public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/10353] [3.4/4.0/4.1/4.2 regression] Java testsuite failures Date: Sun, 29 Jan 2006 17:07:00 -0000 [thread overview] Message-ID: <20060129170723.28962.qmail@sourceware.org> (raw) In-Reply-To: <bug-10353-222@http.gcc.gnu.org/bugzilla/> ------- Comment #25 from ebotcazou at gcc dot gnu dot org 2006-01-29 17:07 ------- Status for 4.1.0pre on Solaris 7, 8, 9 and 10: 32-bit: === libjava tests === Running target unix FAIL: Array_3 execution - gij test FAIL: Array_3 execution - gij test FAIL: FileHandleGcTest execution - source compiled test FAIL: FileHandleGcTest execution - gij test FAIL: FileHandleGcTest execution - bytecode->native test FAIL: FileHandleGcTest -O3 execution - source compiled test FAIL: FileHandleGcTest execution - gij test FAIL: FileHandleGcTest -O3 execution - bytecode->native test === libjava Summary === # of expected passes 3995 # of unexpected failures 8 # of expected failures 10 # of untested testcases 16 64-bit: === libjava tests === Running target unix FAIL: Array_3 execution - gij test FAIL: Array_3 execution - gij test FAIL: FileHandleGcTest execution - source compiled test FAIL: FileHandleGcTest execution - gij test FAIL: FileHandleGcTest execution - bytecode->native test FAIL: FileHandleGcTest -O3 execution - source compiled test FAIL: FileHandleGcTest execution - gij test FAIL: FileHandleGcTest -O3 execution - bytecode->native test FAIL: Throw_2 execution - gij test FAIL: Throw_2 execution - gij test === libjava Summary === # of expected passes 3991 # of unexpected failures 10 # of expected failures 10 # of untested testcases 18 i.e. we are on par with GCC 4.0.x on both 32-bit and 64-bit SPARC/Solaris. There is a significant difference with GCC 4.0.x though: the above results are valid only with GNU binutils (in this case 2.16.1 CVS), not with the Sun tools; in the latter case, there are several additional failures: http://gcc.gnu.org/ml/gcc-testresults/2006-01/msg01501.html http://gcc.gnu.org/ml/gcc-testresults/2006-01/msg01499.html I've investigated a little and the additional failures seem to be related to strings and UTF-8 support. I don't really plan to dig further. I'll add a blurb about that in the platform-specific installation notes. -- ebotcazou at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail|3.3.3 3.4.0 4.0.0 |3.3.3 3.4.0 4.0.0 4.1.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10353
next prev parent reply other threads:[~2006-01-29 17:07 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-10353-222@http.gcc.gnu.org/bugzilla/> 2005-10-16 21:47 ` [Bug libgcj/10353] [3.4/4.0/4.1 " pinskia at gcc dot gnu dot org 2005-10-30 22:03 ` mmitchel at gcc dot gnu dot org 2006-01-29 17:07 ` ebotcazou at gcc dot gnu dot org [this message] 2006-02-28 20:35 ` [Bug libgcj/10353] [3.4/4.0/4.1/4.2 " mmitchel at gcc dot gnu dot org 2006-05-06 11:30 ` [Bug libgcj/10353] [4.0/4.1/4.2 " christian dot joensson at gmail dot com 2006-05-06 11:46 ` ebotcazou at gcc dot gnu dot org 2006-05-25 2:42 ` mmitchel at gcc dot gnu dot org 2007-02-14 9:26 ` [Bug libgcj/10353] [4.0/4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org 2007-09-22 8:46 ` ebotcazou at gcc dot gnu dot org 2008-07-04 16:29 ` [Bug libgcj/10353] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org 2008-12-10 23:18 ` steven at gcc dot gnu dot org 2008-12-10 23:31 ` rguenth at gcc dot gnu dot org 2008-12-11 1:10 ` ghazi at gcc dot gnu dot org 2008-12-11 12:44 ` [Bug libgcj/10353] " ebotcazou at gcc dot gnu dot org
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=20060129170723.28962.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@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: linkBe 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).