public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/6724: "make check" on glibc-2.2.5 fails using gcc-3.1
Date: Sun, 19 May 2002 23:16:00 -0000 [thread overview]
Message-ID: <20020520061601.2934.qmail@sources.redhat.com> (raw)
The following reply was made to PR c/6724; it has been noted by GNATS.
From: Andreas Jaeger <aj@suse.de>
To: alex14641@yahoo.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c/6724: "make check" on glibc-2.2.5 fails using gcc-3.1
Date: Mon, 20 May 2002 08:08:11 +0200
alex14641@yahoo.com writes:
>>Number: 6724
>>Category: c
>>Synopsis: "make check" on glibc-2.2.5 fails using gcc-3.1
>>Description:
> While running 'make check' on glibc-2.2.5 using gcc-3.1, I get the following error.
>
> /usr/gcc-3.1/bin/gcc -nostdlib -nostartfiles -o /update/glibc-build/math/test-if
> loat -Wl,-dynamic-linker=/lib/ld-linux.so.2 -Wl,-z,combreloc /update/glibc-bu
> ild/csu/crt1.o /update/glibc-build/csu/crti.o `/usr/gcc-3.1/bin/gcc --print-file
> -name=crtbegin.o` /update/glibc-build/math/test-ifloat.o /update/glibc-build/mat
> h/libm.so.6 -Wl,-rpath-link=/update/glibc-build:/update/glibc-build/math:/updat
> e/glibc-build/elf:/update/glibc-build/dlfcn:/update/glibc-build/nss:/update/glib
> c-build/nis:/update/glibc-build/rt:/update/glibc-build/resolv:/update/glibc-buil
> d/crypt:/update/glibc-build/linuxthreads /update/glibc-build/libc.so.6 /update/g
> libc-build/libc_nonshared.a -lgcc `/usr/gcc-3.1/bin/gcc --print-file-name=crtend
> .o` /update/glibc-build/csu/crtn.o
> GCONV_PATH=/update/glibc-build/iconvdata LC_ALL=C /update/glibc-build/elf/ld-l
> inux.so.2 --library-path /update/glibc-build:/update/glibc-build/math:/update/gl
> ibc-build/elf:/update/glibc-build/dlfcn:/update/glibc-build/nss:/update/glibc-bu
> ild/nis:/update/glibc-build/rt:/update/glibc-build/resolv:/update/glibc-build/cr
> ypt:/update/glibc-build/linuxthreads /update/glibc-build/math/test-ifloat > /up
> date/glibc-build/math/test-ifloat.out
> make[2]: *** [/update/glibc-build/math/test-ifloat.out] Error 1
> make[2]: Leaving directory `/update/glibc-2.2.5/math'
> make[1]: *** [math/tests] Error 2
> make[1]: Leaving directory `/update/glibc-2.2.5'
> make: *** [check] Error 2
>
> There is a similar bug already in glibc's bug list; Andreas Jaeger seems to think this is a gcc/kernel bug.
In that case I was too short, might be that my comment was to a
different test case. An error in test-ifloat is a problem with a
non-stable algorithm in glibc or an error in GCC, but I suspect the
first. It is definitly no kernel issue. Since we test for exact
errors, we allow deltas and some of them are too small. Just ignore
the issue for now.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next reply other threads:[~2002-05-20 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-19 23:16 Andreas Jaeger [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-02 9:03 bangerth
2002-05-20 11:36 Alex Davis
2002-05-19 14:36 alex14641
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=20020520061601.2934.qmail@sources.redhat.com \
--to=aj@suse.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).