public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: fortran/6108: sparc-sun-solaris2.7 gcc-3.1 extra g77 testsuite failures w/-fpic|-fPIC
@ 2002-04-02 9:58 ghazi
0 siblings, 0 replies; 2+ messages in thread
From: ghazi @ 2002-04-02 9:58 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, ghazi, nobody
Synopsis: sparc-sun-solaris2.7 gcc-3.1 extra g77 testsuite failures w/-fpic|-fPIC
State-Changed-From-To: open->closed
State-Changed-By: ghazi
State-Changed-When: Tue Apr 2 09:58:34 2002
State-Changed-Why:
fixed by
http://gcc.gnu.org/ml/gcc-patches/2002-03/msg02051.html
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6108
^ permalink raw reply [flat|nested] 2+ messages in thread
* fortran/6108: sparc-sun-solaris2.7 gcc-3.1 extra g77 testsuite failures w/-fpic|-fPIC
@ 2002-03-30 7:36 ghazi
0 siblings, 0 replies; 2+ messages in thread
From: ghazi @ 2002-03-30 7:36 UTC (permalink / raw)
To: gcc-gnats
>Number: 6108
>Category: fortran
>Synopsis: sparc-sun-solaris2.7 gcc-3.1 extra g77 testsuite failures w/-fpic|-fPIC
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Sat Mar 30 07:36:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Kaveh Ghazi
>Release: gcc version 3.1 20020328 (prerelease)
>Organization:
>Environment:
sparc-sun-solaris2.7 native as/ld
>Description:
These are all excess failures exposed by adding -fpic|-fPIC:
Running target unix/-fPIC
FAIL: g77.dg/bprob/bprob-1.f execution, -g -fprofile-arcs
FAIL: g77.dg/bprob/bprob-1.f execution, -O0 -fprofile-arcs
FAIL: g77.dg/bprob/bprob-1.f execution, -O1 -fprofile-arcs
FAIL: g77.dg/bprob/bprob-1.f execution, -O2 -fprofile-arcs
FAIL: g77.dg/bprob/bprob-1.f execution, -O3 -fprofile-arcs
FAIL: g77.dg/bprob/bprob-1.f execution, -O3 -g -fprofile-arcs
FAIL: g77.dg/bprob/bprob-1.f execution, -Os -fprofile-arcs
I compiled and ran bprob-1 with -O0 -fPIC (actually the exact command line from the g77.log file) and naturally it says:
> f771: warning: -fPIC and profiling conflict: disabling -fPIC
which makes the difference with the non-pic testrun all the more puzzling.
I get a SEGV, running under gdb I see:
Program received signal SIGSEGV, Segmentation fault.
__bb_init_func (blocks=0x13c) at ../../egcc-3.1-CVS20020328/gcc/libgcc2.c:1463
1463 if (blocks->zero_word)
(gdb) bt
#0 __bb_init_func (blocks=0x13c)
at ../../egcc-3.1-CVS20020328/gcc/libgcc2.c:1463
#1 0x137e8 in _GLOBAL__I_MAIN__GCOV ()
at /teal/caip5/ghazi/gcc-testing/branch/egcc-3.1-CVS20020328/gcc/testsuite/g77.dg/bprob/bprob-1.f:330
#2 0x14144 in __do_global_ctors_aux ()
#3 0x1417c in _init ()
(gdb) list
1458 __bb_init_func (struct bb *blocks)
1459 {
1460 /* User is supposed to check whether the first word is non-0,
1461 but just in case.... */
1462
1463 if (blocks->zero_word)
1464 return;
1465
1466 /* Initialize destructor. */
1467 if (!bb_head)
(gdb) p blocks
$1 = (struct bb *) 0x13c
(gdb) p blocks->zero_word
Cannot access memory at address 0x13c.
>How-To-Repeat:
bootstrap on solaris2.7 and run the testsuite with -fPIC or -fpic
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-04-02 17:58 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-04-02 9:58 fortran/6108: sparc-sun-solaris2.7 gcc-3.1 extra g77 testsuite failures w/-fpic|-fPIC ghazi
-- strict thread matches above, loose matches on Subject: below --
2002-03-30 7:36 ghazi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).