--- Comment #6 from dtemirbulatov at gmail dot com 2007-05-02 16:25 ---
workaround for the bug:
--- gcc/varasm.c-orig 2007-05-02 19:15:04.0 +0400
+++ gcc/varasm.c2007-05-02 19:16:17.0 +0400
@@ -5519,6 +5519,8 @@ decl_readonly_section (tree decl, int re
case
--- Comment #5 from dtemirbulatov at gmail dot com 2007-05-02 16:14 ---
I can reproduce this bug any architecture with -fpic option
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31490
--- Comment #4 from dtemirbulatov at gmail dot com 2007-04-06 03:18 ---
looks like regression is caused by PR26090 fix
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31490
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-04-06 01:59 ---
> This error was not happening with gcc 4.2 snapshot from January.
My reduced testcase shows it happens even in 4.0.2. I don't have any thing
older than that right off hand.
--
http://gcc.gnu.org/bugzilla/show
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-04-06 01:57 ---
Reduced testcase:
int cpu_ (void *attr) {}
const unsigned long _1 __attribute__((section("__"))) = (unsigned long)&cpu_ ;
const unsigned long _group __attribute__((section("__"))) = 0;
--
http://gcc.gnu.org/bug
--- Comment #1 from raj dot khem at gmail dot com 2007-04-06 01:28 ---
Created an attachment (id=1)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=1&action=view)
testcase
testcase to reproduce the problem.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31490
