public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: danglin@gcc.gnu.org To: Stefan.Becker@nokia.com, danglin@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, marduk@mandatory.net, nobody@gcc.gnu.org Subject: Re: target/6867: GCC 3.1 bootstrap fails for HPPA with -march=2.0 Date: Thu, 21 Nov 2002 13:46:00 -0000 [thread overview] Message-ID: <20021115221553.27447.qmail@sources.redhat.com> (raw) Synopsis: GCC 3.1 bootstrap fails for HPPA with -march=2.0 Responsible-Changed-From-To: unassigned->danglin Responsible-Changed-By: danglin Responsible-Changed-When: Fri Nov 15 14:15:53 2002 Responsible-Changed-Why: Assigned responsibility. State-Changed-From-To: open->closed State-Changed-By: danglin State-Changed-When: Fri Nov 15 14:15:53 2002 State-Changed-Why: Fixed in 3.3 (experimental). http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6867
next reply other threads:[~2002-11-15 22:15 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-21 13:46 danglin [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-30 4:49 Stefan.Becker
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=20021115221553.27447.qmail@sources.redhat.com \ --to=danglin@gcc.gnu.org \ --cc=Stefan.Becker@nokia.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=marduk@mandatory.net \ --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: 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).