public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cgd at broadcom dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/12922] MIPS gcc.c-torture/compile/20001226-1.c times out... Date: Thu, 06 Nov 2003 07:21:00 -0000 [thread overview] Message-ID: <20031106072156.6449.qmail@sources.redhat.com> (raw) In-Reply-To: <20031105234446.12922.daney@gcc.gnu.org> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12922 ------- Additional Comments From cgd at broadcom dot com 2003-11-06 07:21 ------- Subject: Re: MIPS gcc.c-torture/compile/20001226-1.c times out... (for the record, this is in no way new. I've remembered this since i started testing gcc against mips-sim.)
next prev parent reply other threads:[~2003-11-06 7:21 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-11-05 23:44 [Bug c/12922] New: " daney at gcc dot gnu dot org 2003-11-05 23:47 ` [Bug c/12922] " echristo at redhat dot com 2003-11-06 7:21 ` cgd at broadcom dot com [this message] 2003-11-06 7:44 ` ebotcazou at gcc dot gnu dot org 2003-11-06 9:46 ` echristo at redhat dot com 2003-11-26 16:23 ` pinskia at gcc dot gnu dot org 2004-02-18 0:51 ` [Bug middle-end/12922] " daney 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=20031106072156.6449.qmail@sources.redhat.com \ --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: 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).