[Bug middle-end/49139] always_inline attribute inconsistencies on failure
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49139 chrbr at gcc dot gnu.org changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Comment #14 from chrbr at gcc dot gnu.org 2011-07-11 13:02:22 UTC --- as discussed -emits a warning when __attribute__((always_inline)) is used without inline keyword -emits an error in an always_inline function couldn't be inlined. -consistently behaves, with or without -Winline
[Bug middle-end/49139] always_inline attribute inconsistencies on failure
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49139 --- Comment #10 from chrbr at gcc dot gnu.org 2011-06-21 06:42:08 UTC --- Author: chrbr Date: Tue Jun 21 06:42:05 2011 New Revision: 175239 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=175239 Log: PR middle-end/49139 fix always_inline diagnostics Added: trunk/gcc/testsuite/gcc.dg/fail_always_inline.c Modified: trunk/gcc/cgraphunit.c trunk/gcc/ipa-inline-transform.c trunk/gcc/testsuite/g++.dg/ipa/devirt-7.C trunk/gcc/testsuite/gcc.dg/20051201-1.c trunk/gcc/testsuite/gcc.dg/always_inline.c trunk/gcc/testsuite/gcc.dg/always_inline2.c trunk/gcc/testsuite/gcc.dg/always_inline3.c trunk/gcc/testsuite/gcc.dg/debug/pr41264-1.c trunk/gcc/testsuite/gcc.dg/inline-22.c trunk/gcc/testsuite/gcc.dg/lto/20090218-1_0.c trunk/gcc/testsuite/gcc.dg/lto/20090218-1_1.c trunk/gcc/testsuite/gcc.dg/torture/pta-structcopy-1.c trunk/gcc/testsuite/gcc.dg/uninit-pred-5_a.c trunk/gcc/testsuite/gcc.dg/uninit-pred-5_b.c trunk/gcc/tree-inline.c
[Bug middle-end/49139] always_inline attribute inconsistencies on failure
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49139 --- Comment #11 from chrbr at gcc dot gnu.org 2011-06-21 06:43:28 UTC --- Author: chrbr Date: Tue Jun 21 06:43:26 2011 New Revision: 175240 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=175240 Log: PR middle-end/49139 fix always_inline diagnostics Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog
[Bug middle-end/49139] always_inline attribute inconsistencies on failure
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49139 --- Comment #12 from chrbr at gcc dot gnu.org 2011-06-21 06:45:09 UTC --- Author: chrbr Date: Tue Jun 21 06:45:05 2011 New Revision: 175241 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=175241 Log: PR middle-end/49139 PR other/43564 make sure the inline function is inlined Modified: trunk/gcc/ChangeLog trunk/gcc/ipa-inline.c
[Bug middle-end/49139] always_inline attribute inconsistencies on failure
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49139 --- Comment #13 from chrbr at gcc dot gnu.org 2011-06-21 06:48:50 UTC --- Author: chrbr Date: Tue Jun 21 06:48:45 2011 New Revision: 175242 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=175242 Log: PR middle-end/49139 fix always_inline diagnostics Added: trunk/gcc/testsuite/gcc.dg/fail_always_inline2.c Modified: trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.dg/inline_1.c trunk/gcc/testsuite/gcc.dg/inline_2.c trunk/gcc/testsuite/gcc.dg/inline_3.c trunk/gcc/testsuite/gcc.dg/inline_4.c trunk/gcc/testsuite/gcc.dg/tree-ssa/pr40087.c
[Bug middle-end/49139] always_inline attribute inconsistencies on failure
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49139 --- Comment #7 from chrbr at gcc dot gnu.org 2011-05-27 14:37:42 UTC --- Created attachment 24373 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=24373 testcase 1
[Bug middle-end/49139] always_inline attribute inconsistencies on failure
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49139 --- Comment #8 from chrbr at gcc dot gnu.org 2011-05-27 14:38:13 UTC --- Created attachment 24374 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=24374 testcase 2
[Bug middle-end/49139] always_inline attribute inconsistencies on failure
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49139 --- Comment #9 from Manuel López-Ibáñez manu at gcc dot gnu.org 2011-05-27 15:08:17 UTC --- You patch looks fine to me but I cannot approve it. You'll need to submit it to gcc-patches for review and approval. You'll need also a Changelog. If you don't have svn access, you should mention in your emails that you need someone to commit the patch for you. See also http://gcc.gnu.org/contribute.html#patches