public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/6680: [alphaev5-dec-osf5.0] gcc-3.1 build fails with internal error Date: Wed, 21 May 2003 08:33:00 -0000 [thread overview] Message-ID: <20030521082650.13674.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/6680; it has been noted by GNATS. From: Dara Hazeghi <dhazeghi@yahoo.com> To: sabelka@iue.tuwien.ac.at, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: bootstrap/6680: [alphaev5-dec-osf5.0] gcc-3.1 build fails with internal error Date: Wed, 21 May 2003 01:21:44 -0700 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- trail&database=gcc&pr=6680 Hello, would it be possible for you to check whether the problem in this report still occurs with the most current version of gcc (3.3) or the cvs 3.3 branch? I believe some progress has been made in this area. Thanks, Dara
next reply other threads:[~2003-05-21 8:33 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-21 8:33 Dara Hazeghi [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-21 9:41 ehrhardt 2002-12-06 7:26 Wolfgang Bangerth 2002-12-05 13:46 Wolfgang Bangerth
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=20030521082650.13674.qmail@sources.redhat.com \ --to=dhazeghi@yahoo.com \ --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).