From: Andreas Jaeger <aj@suse.de>
To: gcc@gcc.gnu.org
Subject: Miscompilation of glibc with CVS mainline
Date: Wed, 01 Jan 2003 13:37:00 -0000 [thread overview]
Message-ID: <u8ptrh0z71.fsf@gromit.moeb> (raw)
GCC CVS mainline miscompiles glibc on i686-linux-gnu. The actual
error I noticed is:
CPP='/opt/gcc/3.3-devel/bin/gcc -E -x c-header' /builds/glibc/test-libc/elf/ld-linux.so.2 --library-path /builds/glibc/test-libc:/builds/glibc/test-libc/math:/builds/glibc/test-libc/elf:/builds/glibc/test-libc/dlfcn:/builds/glibc/test-libc/nss:/builds/glibc/test-libc/nis:/builds/glibc/test-libc/rt:/builds/glibc/test-libc/resolv:/builds/glibc/test-libc/crypt:/builds/glibc/test-libc/linuxthreads /builds/glibc/test-libc/sunrpc/rpcgen -Y ../scripts -c rpcsvc/bootparam_prot.x -o /builds/glibc/test-libc/sunrpc/xbootparam_prot.T
make[2]: *** [/builds/glibc/test-libc/sunrpc/xbootparam_prot.stmp] Segmentation fault
make[2]: Leaving directory `/cvs/libc/sunrpc'
To track down the failure, I used Janis' script and noticed that it
fails since the merge from the 3_4-basic-improvement branch.
Searching that branch I found this patch as beeing the problem:
+2002-10-07 Richard Henderson <rth@redhat.com>
+
+ * cse.c (fixed_base_plus_p): Turn FIXED_BASE_PLUS_P into a
+ function; cleanup PLUS case by using recursion. Update all users.
+ (NONZERO_BASE_PLUS_P): Remove.
+ (find_comparison_args): Use rtx_addr_can_trap_p instead.
+ (fold_rtx): Use nonzero_address_p.
+ * rtl.h (nonzero_address_p): Declare.
+ * rtlanal.c (rtx_varies_p): Handle ADDRESSOF.
+ (rtx_addr_can_trap_p): Likewise.
+ (nonzero_address_p): New.
+ * simplify-rtx.c (NONZERO_BASE_PLUS_P): Remove.
+ (simplify_relational_operation): Use nonzero_address_p.
I haven't been able to figure out which file in glibc is miscompiled
and therefore like to ask for an additional review of that patch
again.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next reply other threads:[~2003-01-01 13:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 13:37 Andreas Jaeger [this message]
2003-01-01 17:43 John David Anglin
2003-01-02 13:18 ` Andreas Jaeger
2003-01-02 13:27 ` Jakub Jelinek
2003-01-02 13:53 ` Andreas Jaeger
2003-01-02 14:41 ` Andreas Jaeger
2003-01-02 21:10 ` Andreas Jaeger
2003-01-02 17:38 ` John David Anglin
2003-01-02 17:48 ` "Martin v. Löwis"
2003-01-02 18:52 ` John David Anglin
2003-01-02 18:58 ` Paul Jarc
2003-01-02 19:10 ` Dale Johannesen
2003-01-02 19:16 ` John David Anglin
2003-01-02 19:26 ` Paul Jarc
2003-01-02 20:25 ` Martin v. Löwis
2003-01-02 22:11 ` Richard Henderson
2003-01-03 1:02 ` John David Anglin
2003-01-03 1:35 ` Richard Henderson
2003-01-02 19:42 ` Ulrich Drepper
2003-01-02 22:16 ` Richard Henderson
2003-01-03 0:14 ` Fergus Henderson
[not found] <no.id>
2003-01-02 17:48 ` John David Anglin
2003-01-02 17:54 ` Jakub Jelinek
2003-01-02 18:58 ` John David Anglin
2003-01-02 17:57 ` Daniel Jacobowitz
2003-01-04 17:52 Robert Dewar
2003-01-04 18:54 Robert Dewar
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=u8ptrh0z71.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=gcc@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).