From: Matthias Klose <doko@ubuntu.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Martin Thuresson <martin@mtme.org>,
binutils <binutils@sourceware.org>,
Tristan Gingold <gingold@adacore.com>,
GCC Java <java@gcc.gnu.org>
Subject: [regressions in GCC/libjava testsuite] Re: Patch to make bfd compile with -Wc++-compat
Date: Wed, 30 Sep 2009 23:01:00 -0000 [thread overview]
Message-ID: <4AC3E34D.3080708@ubuntu.com> (raw)
In-Reply-To: <4AA820CB.3030403@redhat.com>
On 09.09.2009 23:40, Nick Clifton wrote:
> Hi Martin,
>
>> Reran make check, make check-gas and make check-ld on x86_64-linux and
>> arm-eabi
>> and found no regression.
>
> Approved and applied (mainline and branch).
I identified this patch or the one applied to the binutils subdirectory to cause
regressions in the GCC/libjava testsuite on the 4.3/4.4 branches and trunk, at
least on {x86,x86_64,powerpc}-linux:
FAIL: StackTrace2 execution - source compiled test
FAIL: StackTrace2 -findirect-dispatch execution - source compiled test
FAIL: StackTrace2 -O3 execution - source compiled test
FAIL: StackTrace2 -O3 -findirect-dispatch execution - source compiled test
FAIL: Throw_3 execution - source compiled test
FAIL: Throw_3 -findirect-dispatch execution - source compiled test
FAIL: Throw_3 -O3 execution - source compiled test
FAIL: Throw_3 -O3 -findirect-dispatch execution - source compiled test
FAIL: stacktrace execution - source compiled test
FAIL: stacktrace -findirect-dispatch execution - source compiled test
FAIL: stacktrace -O3 execution - source compiled test
FAIL: stacktrace -O3 -findirect-dispatch execution - source compiled test
The tests fail as:
set_ld_library_path_env_vars:
ld_library_path=.:/scratch/packages/gcc/4.3/u/java/gcj-4.3-4.3.4/build/i486-linux-gnu/./libjava/.libs:/scratch/packages/gcc/4.3/u/java/gcj-4.3-4.3.4/build/gcc
invoke:
/scratch/packages/gcc/4.3/u/java/gcj-4.3-4.3.4/build/i486-linux-gnu/libjava/testsuite/StackTrace2.exe
Setting LD_LIBRARY_PATH to
.:/scratch/packages/gcc/4.3/u/java/gcj-4.3-4.3.4/build/i486-linux-gnu/./libjava/.libs:/scratch/packages/gcc/4.3/u/java/gcj-4.3-4.3.4/build/gcc:.:/scratch/packages/gcc/4.3/u/java/gcj-4.3-4.3.4/build/i486-linux-gnu/./libjava/.libs:/scratch/packages/gcc/4.3/u/java/gcj-4.3-4.3.4/build/gcc
Exception in thread "main" java.lang.NullPointerException
*** Got java.lang.NullPointerException while trying to print stack trace.
No difference, if binutils is built with 4.3.4 or 4.4.1.
Matthias
next parent reply other threads:[~2009-09-30 23:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <624836f10909071812q358c0ff8p34ce468ccadb50@mail.gmail.com>
[not found] ` <m3pra1w0t9.fsf@google.com>
[not found] ` <624836f10909082138h1e14eb14j76d08ba0e4d76d0a@mail.gmail.com>
[not found] ` <624836f10909082308p349131c5l103efc029e9e26e0@mail.gmail.com>
[not found] ` <4AA820CB.3030403@redhat.com>
2009-09-30 23:01 ` Matthias Klose [this message]
2009-09-30 23:23 ` Matthias Klose
2009-09-30 23:48 ` Alan Modra
2009-10-01 0:04 ` Alan Modra
2009-10-01 0:20 ` Martin Thuresson
2009-10-01 0:34 ` Dave Korn
2009-10-01 0:46 ` Martin Thuresson
2009-10-01 0:56 ` Ian Lance Taylor
2009-10-01 1:14 ` Matt Rice
2009-10-01 5:37 ` Alan Modra
2009-10-01 11:35 ` Matthias Klose
2009-10-01 1:36 ` Martin Thuresson
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=4AC3E34D.3080708@ubuntu.com \
--to=doko@ubuntu.com \
--cc=binutils@sourceware.org \
--cc=gingold@adacore.com \
--cc=java@gcc.gnu.org \
--cc=martin@mtme.org \
--cc=nickc@redhat.com \
/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).