public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: nirkko@dkf6.unibe.ch To: gcc-gnats@gcc.gnu.org Subject: libgcj/7578: gcc-3.1.1 libjava regression: tons of new FAILS on check Date: Mon, 12 Aug 2002 12:56:00 -0000 [thread overview] Message-ID: <20020812145612.27843.qmail@sources.redhat.com> (raw) >Number: 7578 >Category: libgcj >Synopsis: gcc-3.1.1 libjava regression: tons of new FAILS on check >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Aug 12 08:06:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: nirkko@dkf6.unibe.ch >Release: gcc-3.1.1 >Organization: >Environment: Sun SPARC Solaris 2.6 (and Linux, and others...) >Description: after gcc bootstrap: whereas in gcc-3.1, gmake -k check results for libjava were in the 'usual' range, now in gcc-3.1.1 there are tons of unexpected FAILS, which seems a regression to me. Looking at your "successful builds" webpage, this seems so also on other platforms (for example, Linux-i86). Do tests FAIL because of assembler warnings, and newer assemblers (gas-2.13) issue more of them? or was there a major change in the testsuite or in libjava code? >How-To-Repeat: take gcc-3.1 and gcc-3.1.1 'gmake bootstrap' and 'gmake -k check' each of them. compare results. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-08-12 15:06 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020812145612.27843.qmail@sources.redhat.com \ --to=nirkko@dkf6.unibe.ch \ --cc=gcc-gnats@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).