public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Reichelt <reichelt@igpm.rwth-aachen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/6964: Internal compiler error using -O2 but ok using -O0 Date: Tue, 02 Jul 2002 11:16:00 -0000 [thread overview] Message-ID: <20020702181607.2271.qmail@sources.redhat.com> (raw) The following reply was made to PR c/6964; it has been noted by GNATS. From: Reichelt <reichelt@igpm.rwth-aachen.de> To: gcc-gnats@gcc.gnu.org, jari@thep.lu.se, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c/6964: Internal compiler error using -O2 but ok using -O0 Date: Tue, 2 Jul 2002 20:47:12 +0200 Hi, the bug seems to be fixed since both testcases (the original one and the reduced one) now compile fine with gcc 3.1.1 20020701 and gcc 3.2 20020702 (checked on i686-pc-linux-gnu). Hence, the PR can probably be closed. Greetings, Volker Reichelt http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6964
next reply other threads:[~2002-07-02 18:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-02 11:16 Reichelt [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-23 6:12 reichelt 2002-06-12 7:46 Reichelt 2002-06-07 14:26 jari
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=20020702181607.2271.qmail@sources.redhat.com \ --to=reichelt@igpm.rwth-aachen.de \ --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).