http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54177
--- Comment #2 from Uros Bizjak 2012-08-05 06:46:03
UTC ---
Following patch fixes the failure:
--cut here--
Index: var-tracking.c
===
--- var-tracking.c (revision 190140)
+++ v
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54177
Uros Bizjak changed:
What|Removed |Added
CC||aoliva at gcc dot gnu.org
Target Mileston
at all.
[1]
Compiler version: 4.8.0 20120804 (experimental) [trunk revision 190144] (GCC)
Platform: alphaev68-unknown-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54176
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-valid-code
Target|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54176
--- Comment #2 from Tommy Thorn 2012-08-05
03:26:16 UTC ---
Forget the attached example, lm32-elf-gcc breaks as soon as any static or
extern variable is used in a function. Fx:
int x;
int foo() { return x; }
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54176
--- Comment #1 from Tommy Thorn 2012-08-05
03:14:30 UTC ---
Looks like the front end is looping (recursively):
gdb --args /home/opt/lm32/bin/../lib/gcc/lm32-elf/4.7.1/cc1 -quiet -v -iprefix
/home/opt/lm32/bin/../lib64/gcc/lm32-elf/4.7.1/ sieve.c
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54176
Bug #: 54176
Summary: lm32-elf-gcc: internal compiler error: Segmentation
fault (program cc1)
Classification: Unclassified
Product: gcc
Version: 4.7.1
Status: UNCONFI
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54165
Paolo Carlini changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #4 from Paolo Carlin
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54033
--- Comment #4 from hjl at gcc dot gnu.org 2012-08-04
18:27:04 UTC ---
Author: hjl
Date: Sat Aug 4 18:26:56 2012
New Revision: 190144
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=190144
Log:
Fix PR 54033, problems with -I, with test ca
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54166
H.J. Lu changed:
What|Removed |Added
CC||hjl.tools at gmail dot com
--- Comment #4 from
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54175
H.J. Lu changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54175
Bug #: 54175
Summary: [4.8 Regression] 459.GemsFDTD in SPEC CPU 2006 failed
to build
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54174
Bug #: 54174
Summary: Missed optimization: Unnecessary vmovaps generated for
__builtin_ia32_vextractf128_ps256(v, 0)
Classification: Unclassified
Product: gcc
Version: 4.7.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54172
Richard Guenther changed:
What|Removed |Added
Target Milestone|--- |4.7.2
Summary|[4.7 Regressi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54173
--- Comment #3 from Paolo Carlini 2012-08-04
16:49:36 UTC ---
Well, whatever it is, if the problem is so old, I think we have a WONTFIX at
this point, because std::string will be completely different in C++11.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54173
--- Comment #2 from Pawel Sikora 2012-08-04 16:13:03
UTC ---
(In reply to comment #1)
> For sure, nothing changed in this area for years and years, thus must be a
> compiler issue. Please try to figure when it started...
i have similar effects f
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54173
Paolo Carlini changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54173
Bug #: 54173
Summary: -D_GLIBCXX_DEBUG breaks
string::_Rep::_S_empty_rep_storage weak binding.
Classification: Unclassified
Product: gcc
Version: 4.7.2
Status: UNCONF
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54161
Paolo Carlini changed:
What|Removed |Added
Status|NEW |ASSIGNED
AssignedTo|unassigned at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52983
Alexandre Oliva changed:
What|Removed |Added
Component|rtl-optimization|debug
--- Comment #16 from Alexandre Ol
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54165
Paolo Carlini changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54172
Bug #: 54172
Summary: [4.7 Regression] __cxa_guard_acquire thread-safety
issue
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54170
--- Comment #4 from Paolo Carlini 2012-08-04
11:37:12 UTC ---
If submitter can try current 4_7-branch or mainline, it would be easy for him
to double check.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54170
--- Comment #3 from Paolo Carlini 2012-08-04
11:35:34 UTC ---
Indeed, I suspected that immediately. But without a self contained testcase not
requiring inspection of the assembly personally I'm not 100% sure (and I'm in
the middle of 2-3 other th
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54170
--- Comment #2 from Jonathan Wakely 2012-08-04
10:47:49 UTC ---
Dup of PR 52988?
25 matches
Mail list logo