public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lucier at math dot purdue dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/37878] [4.4 regression] PPC64 ldu command generated with invalid offset
Date: Thu, 23 Oct 2008 19:22:00 -0000 [thread overview]
Message-ID: <20081023192050.4910.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37878-271@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from lucier at math dot purdue dot edu 2008-10-23 19:20 -------
I bootstrapped and regtested the suggested patch. There was one fewer FAIL in
the gcc tests:
FAIL: gcc.c-torture/execute/nestfunc-6.c execution, -O0
and one more failure in the libgomp tests:
FAIL: libgomp.fortran/crayptr2.f90 -O3 -fomit-frame-pointer -funroll-loops
execution test
However, it's not clear to me from the output of gdb implies that this may is
a problem with the compiled code (the command lines are taken from the log
file):
[descartes:powerpc64-apple-darwin9.5.0/libgomp/testsuite] lucier%
/Users/lucier/programs/gcc/objdirs/mainline/gcc/xgcc
-B/Users/lucier/programs/gcc/objdirs/mainline/gcc/
/Users/lucier/programs/gcc/mainline/libgomp/testsuite/libgomp.fortran/crayptr2.f90
-B/Users/lucier/programs/gcc/objdirs/mainline/powerpc64-apple-darwin9.5.0/./libgomp/
-I/Users/lucier/programs/gcc/objdirs/mainline/powerpc64-apple-darwin9.5.0/./libgomp
-I/Users/lucier/programs/gcc/mainline/libgomp/testsuite/.. -shared-libgcc
-fmessage-length=0 -fopenmp -O3 -fomit-frame-pointer -funroll-loops -fopenmp
-fcray-pointer -static-libgcc
-L/Users/lucier/programs/gcc/objdirs/mainline/powerpc64-apple-darwin9.5.0/./libgomp/.libs
-lgomp
-L/Users/lucier/programs/gcc/objdirs/mainline/powerpc64-apple-darwin9.5.0/./libgomp/../libgfortran/.libs
-lgfortranbegin -lgfortran -lm -mcpu=970 -m64 -o ./crayptr2.exe
[descartes:powerpc64-apple-darwin9.5.0/libgomp/testsuite] lucier% env
LD_LIBRARY_PATH=.:/Users/lucier/programs/gcc/objdirs/mainline/powerpc64-apple-darwin9.5.0/./libgomp/.libs:/Users/lucier/programs/gcc/objdirs/mainline/gcc:/Users/lucier/programs/gcc/objdirs/mainline/powerpc64-apple-darwin9.5.0/./libgomp/../libgfortran/.libs:.:/Users/lucier/programs/gcc/objdirs/mainline/powerpc64-apple-darwin9.5.0/./libgomp/.libs:/Users/lucier/programs/gcc/objdirs/mainline/gcc:/Users/lucier/programs/gcc/objdirs/mainline/powerpc64-apple-darwin9.5.0/./libgomp/../libgfortran/.libs
gdb ./crayptr2.exe
GNU gdb 6.3.50-20050815 (Apple version gdb-962) (Sat Jul 26 08:17:57 UTC 2008)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "powerpc-apple-darwin"...Reading symbols for shared
libraries .... done
(gdb) run
Starting program:
/Users/lucier/programs/gcc/objdirs/mainline/powerpc64-apple-darwin9.5.0/libgomp/testsuite/crayptr2.exe
warning: posix_spawn failed, trying execvp, error: 86
Reading symbols for shared libraries +++.. done
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000
0x0000000100001678 in MAIN__.omp_fn.0 ()
(gdb) where
#0 0x0000000100001678 in MAIN__.omp_fn.0 ()
#1 0x000000010000187c in MAIN__ ()
#2 0x00000001000018e4 in main (argc=1, argv=<value temporarily unavailable,
due to optimizations>) at ../../../../mainline/libgfortran/fmain.c:21
It is completely reproducible, however.
Brad
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37878
next prev parent reply other threads:[~2008-10-23 19:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 0:32 [Bug target/37878] New: " lucier at math dot purdue dot edu
2008-10-21 0:33 ` [Bug target/37878] " lucier at math dot purdue dot edu
2008-10-21 0:34 ` lucier at math dot purdue dot edu
2008-10-21 8:37 ` schwab at suse dot de
2008-10-21 8:40 ` [Bug target/37878] [4.4 regression] " schwab at suse dot de
2008-10-21 9:56 ` jakub at gcc dot gnu dot org
2008-10-21 14:54 ` dje at gcc dot gnu dot org
2008-10-21 15:12 ` jakub at gcc dot gnu dot org
2008-10-21 15:16 ` dje at gcc dot gnu dot org
2008-10-22 3:33 ` mmitchel at gcc dot gnu dot org
2008-10-22 11:35 ` jakub at gcc dot gnu dot org
2008-10-23 19:22 ` lucier at math dot purdue dot edu [this message]
2008-10-23 21:26 ` lucier at math dot purdue dot edu
2008-10-28 22:37 ` dje at gcc dot gnu dot org
2008-10-28 23:15 ` dje at gcc dot gnu dot org
2008-10-29 8:33 ` jakub at gcc dot gnu dot org
2008-10-29 23:33 ` dje at gcc dot gnu dot org
2008-10-30 0:02 ` lucier at math dot purdue dot edu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081023192050.4910.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).