[Bug c/55830] inline and __attribute__((always_inline)) treated differently for unused-function warning

2012-12-30 Thread sch...@linux-m68k.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55830 --- Comment #4 from Andreas Schwab 2012-12-30 22:12:28 UTC --- static alone already makes a function eligible for inlining.

[Bug c/55830] inline and __attribute__((always_inline)) treated differently for unused-function warning

2012-12-30 Thread brooks at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55830 --- Comment #3 from Brooks Moses 2012-12-30 21:50:08 UTC --- Andrew: Oh, interesting. So perhaps this is really a failure to warn (or error?) for a case where "__attribute__((always_inline))" isn't used with "inline", and a case of missin

[Bug c/55830] inline and __attribute__((always_inline)) treated differently for unused-function warning

2012-12-30 Thread brooks at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55830 --- Comment #2 from Brooks Moses 2012-12-30 21:46:02 UTC --- Created attachment 29064 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29064 Minimal test case The attached test case illustrates the problem. When compiled with -Wall

[Bug c/55830] inline and __attribute__((always_inline)) treated differently for unused-function warning

2012-12-30 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55830 --- Comment #1 from Andrew Pinski 2012-12-30 21:42:28 UTC --- IIRC always_inline really needs inline also.

[Bug c/55830] New: inline and __attribute__((always_inline)) treated differently for unused-function warning

2012-12-30 Thread brooks at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55830 Bug #: 55830 Summary: inline and __attribute__((always_inline)) treated differently for unused-function warning Classification: Unclassified Product: gcc Version: 4.7.1

[Bug sanitizer/55561] TSAN: Fortran/OMP yields false positives

2012-12-30 Thread Joost.VandeVondele at mat dot ethz.ch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55561 --- Comment #27 from Joost VandeVondele 2012-12-30 19:57:24 UTC --- (In reply to comment #24) > For testing you can comment out first 2 lines of gomp_ptrlock_get(). That > should fix the race in libgomp. It's not a good fix form performanc

[Bug sanitizer/55561] TSAN: Fortran/OMP yields false positives

2012-12-30 Thread dvyukov at google dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55561 --- Comment #26 from Dmitry Vyukov 2012-12-30 17:07:01 UTC --- (In reply to comment #25) > (In reply to comment #24) > > For testing you can comment out first 2 lines of gomp_ptrlock_get(). That > > should fix the race in libgomp. It's no

[Bug rtl-optimization/55829] New: [4.8 Regression] ICE: in curr_insn_transform, at lra-constraints.c:3069 with -msse3

2012-12-30 Thread zsojka at seznam dot cz
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55829 Bug #: 55829 Summary: [4.8 Regression] ICE: in curr_insn_transform, at lra-constraints.c:3069 with -msse3 Classification: Unclassified Product: gcc Version: 4.8.0

[Bug sanitizer/55561] TSAN: Fortran/OMP yields false positives

2012-12-30 Thread Joost.VandeVondele at mat dot ethz.ch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55561 --- Comment #25 from Joost VandeVondele 2012-12-30 14:52:51 UTC --- (In reply to comment #24) > For testing you can comment out first 2 lines of gomp_ptrlock_get(). That > should fix the race in libgomp. It's not a good fix form performanc

[Bug middle-end/55797] [4.8 Regression] ICE: verify_cgraph_node failed: edge has no corresponding call_stmt

2012-12-30 Thread mpolacek at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55797 Marek Polacek changed: What|Removed |Added CC||hubicka at gcc dot gnu.org ---

[Bug middle-end/55797] [4.8 Regression] ICE: verify_cgraph_node failed: edge has no corresponding call_stmt

2012-12-30 Thread mpolacek at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55797 Marek Polacek changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug sanitizer/55561] TSAN: Fortran/OMP yields false positives

2012-12-30 Thread dvyukov at google dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55561 --- Comment #24 from Dmitry Vyukov 2012-12-30 10:11:27 UTC --- For testing you can comment out first 2 lines of gomp_ptrlock_get(). That should fix the race in libgomp. It's not a good fix form performance pov, but should be OK for testing

[Bug sanitizer/55561] TSAN: Fortran/OMP yields false positives

2012-12-30 Thread dvyukov at google dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55561 --- Comment #23 from Dmitry Vyukov 2012-12-30 09:57:44 UTC --- (In reply to comment #22) > I did do some more testing, and the combination '-fsanitize=thread -fopenmp' > was really very useful. Apart from the libgomp-related warning discus

[Bug sanitizer/55561] TSAN: Fortran/OMP yields false positives

2012-12-30 Thread Joost.VandeVondele at mat dot ethz.ch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55561 --- Comment #22 from Joost VandeVondele 2012-12-30 09:03:15 UTC --- (In reply to comment #18) > > The obvious solution to this seems to be that also the OMP runtime (libgomp) > > must be compiled with '-fsanitize=thread. If I do that, it a