--- Comment #7 from pinskia at gcc dot gnu dot org 2009-01-14 23:14 ---
And it is. I had the same issue also and backporting the patch for PR 26399
fixes it for me.
*** This bug has been marked as a duplicate of 26399 ***
--
pinskia at gcc dot gnu dot org changed:
What
--- Comment #6 from pinskia at gcc dot gnu dot org 2009-01-14 21:04 ---
I think this is a dup of bug 26399 which was fixed for 4.2.0
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25351
--- Comment #5 from lothar at tradescape dot biz 2006-03-24 18:45 ---
We also get ICEs on valid code with gcc 4.1.0 on both i686 and x86_64 both on
Linux if we compile our source with -fprofile-arcs -ftest-coverage.
When I tried to produce a precompiled (-E) file I could NOT reproduce th
--- Comment #4 from cyberax at elewise dot com 2005-12-11 16:29 ---
Created an attachment (id=10452)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10452&action=view)
Test case
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25351
--- Comment #3 from cyberax at elewise dot com 2005-12-11 16:23 ---
Yes, preprocessed file attached. But this bug is somewhat hard to reproduce,
I've spent about 3 hours trying to create a minimal test-case without much
success - sometimes compilation is finished successfully, but the r
--- Comment #2 from pinskia at gcc dot gnu dot org 2005-12-11 15:52 ---
Do you have a normal testcase that is C++ which produces this symbol?
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
---
