public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Eric ´Nick´ Nicolich" <pokermind@bigzoo.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: middle-end/10456: gcc 3.2 internal compiler error when building powerpc gas Date: Wed, 23 Apr 2003 17:46:00 -0000 [thread overview] Message-ID: <20030423174601.26175.qmail@sources.redhat.com> (raw) The following reply was made to PR middle-end/10456; it has been noted by GNATS. From: =?ISO-8859-1?Q?Eric_=B4Nick=B4_Nicolich?= <pokermind@bigzoo.net> To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org, pokermind@bigzoo.net Cc: Subject: Re: middle-end/10456: gcc 3.2 internal compiler error when building powerpc gas Date: Wed, 23 Apr 2003 10:45:47 -0700 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10456 This problem is a duplicate of 7705 and 7720. I apologize for the redundancy, and for not having the foresight to look at the "closed" problem reports. Eric
next reply other threads:[~2003-04-23 17:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-23 17:46 Eric ´Nick´ Nicolich [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-23 17:55 bangerth 2003-04-22 21:56 Eric ´Nick´ Nicolich 2003-04-22 20:26 pokermind
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=20030423174601.26175.qmail@sources.redhat.com \ --to=pokermind@bigzoo.net \ --cc=gcc-prs@gcc.gnu.org \ --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).