public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "debian-gcc at lists dot debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/17180] New: nearly all g77 tests fail on sparc-linux
Date: Wed, 25 Aug 2004 06:55:00 -0000	[thread overview]
Message-ID: <20040825065523.17180.debian-gcc@lists.debian.org> (raw)

seen in various test results, as well as my own builds, i.e.:

failed 20040731: http://gcc.gnu.org/ml/gcc-testresults/2004-08/msg00047.html
failed 20040731: http://gcc.gnu.org/ml/gcc-testresults/2004-08/msg00251.html
failed 20040721: http://gcc.gnu.org/ml/gcc-testresults/2004-07/msg00994.html

ok 20040709: http://gcc.gnu.org/ml/gcc-testresults/2004-07/msg01317.html
ok 3.4.1 release: http://gcc.gnu.org/ml/gcc-testresults/2004-07/msg00786.html
ok 20040710: http://gcc.gnu.org/ml/gcc-testresults/2004-07/msg00632.html

currently no access to a sparc-linux box.

    Matthias

-- 
           Summary: nearly all g77 tests fail on sparc-linux
           Product: gcc
           Version: 3.4.2
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: debian-gcc at lists dot debian dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: sparc*-linux
  GCC host triplet: sparc*-linux
GCC target triplet: sparc*-linux


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17180


             reply	other threads:[~2004-08-25  6:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25  6:55 debian-gcc at lists dot debian dot org [this message]
2004-08-25  7:16 ` [Bug target/17180] [3.4 Regression] " pinskia at gcc dot gnu dot org
2004-08-29 19:09 ` mmitchel at gcc dot gnu dot org
2004-08-30 10:31 ` ebotcazou at gcc dot gnu dot org
2004-08-31  4:23 ` ebotcazou at gcc dot gnu dot org
2004-08-31  4:24 ` [Bug target/17180] [3.4 Regression] nearly all g77 tests fail ebotcazou at gcc dot gnu dot org
2004-08-31  5:00 ` ebotcazou at gcc dot gnu dot org
2004-08-31  5:11 ` mark at codesourcery dot com
2004-08-31  5:32 ` ebotcazou at gcc dot gnu dot org
2004-08-31  5:47 ` ebotcazou at gcc dot gnu dot org
2004-08-31  5:53 ` pinskia at gcc dot gnu dot org
2004-08-31  6:37 ` ebotcazou at gcc dot gnu dot org
2004-08-31  9:31 ` bdavis at gcc dot gnu dot org
2004-08-31 10:35 ` ebotcazou at gcc dot gnu dot org
2004-08-31 10:39 ` bdavis9659 at comcast dot net
2004-08-31 17:28 ` ebotcazou at gcc dot gnu dot org
2004-09-01  1:15 ` bdavis at gcc dot gnu dot org
2004-09-01  5:10 ` ebotcazou at gcc dot gnu dot org
2004-09-01  6:03 ` mmitchel at gcc dot gnu dot org
2004-09-01  7:23 ` [Bug fortran/17180] " cvs-commit at gcc dot gnu dot org
2004-09-01  7:25 ` ebotcazou at gcc dot gnu dot org
2004-09-01 10:20 ` ebotcazou at gcc dot gnu dot org
2004-09-02  6:08 ` ebotcazou at gcc dot gnu dot org
2004-09-02  7:48 ` mark at codesourcery dot com
2004-09-02 16:04 ` cvs-commit at gcc dot gnu dot org
2004-09-02 16:06 ` 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=20040825065523.17180.debian-gcc@lists.debian.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).