[Bug ipa/67368] Inlining failed due to no_sanitize_address and always_inline conflict

2021-08-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67368 Andrew Pinski changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW

[Bug ipa/67368] Inlining failed due to no_sanitize_address and always_inline conflict

2017-10-04 Thread loic.yhuel at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67368 Loïc Yhuel changed: What|Removed |Added CC||loic.yhuel at gmail dot com --- Comment #4

[Bug ipa/67368] Inlining failed due to no_sanitize_address and always_inline conflict

2015-09-08 Thread ryabinin.a.a at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67368 Andrey Ryabinin changed: What|Removed |Added CC||ryabinin.a.a at gmail dot com --- Comm

[Bug ipa/67368] Inlining failed due to no_sanitize_address and always_inline conflict

2015-08-27 Thread y.gribov at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67368 --- Comment #2 from Yury Gribov --- (In reply to Richard Biener from comment #1) > so it fails on purpose (not sure why though). And it ignores always-inline. > I wonder if we should, for always-inline functions, inline anyway and output > a war

[Bug ipa/67368] Inlining failed due to no_sanitize_address and always_inline conflict

2015-08-27 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67368 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|