public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Stefan Esser <se@freebsd.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/6957: Internal compiler error in failed_reload, at reload1.c:5050 Date: Sat, 29 Jun 2002 13:36:00 -0000 [thread overview] Message-ID: <20020629203601.12687.qmail@sources.redhat.com> (raw) The following reply was made to PR c/6957; it has been noted by GNATS. From: Stefan Esser <se@freebsd.org> To: gerald@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, pfeifer@dbai.tuwien.ac.at, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c/6957: Internal compiler error in failed_reload, at reload1.c:5050 Date: Sat, 29 Jun 2002 22:29:34 +0200 On 2002-06-28 12:47 -0000, gerald@gcc.gnu.org wrote: > Synopsis: Internal compiler error in failed_reload, at reload1.c:5050 > > State-Changed-From-To: open->feedback > State-Changed-By: gerald > State-Changed-When: Fri Jun 28 05:47:50 2002 > State-Changed-Why: > As far as I can see, Bernd Schmidt has addressed this bug: > http://gcc.gnu.org/ml/gcc/2002-06/msg01211.html > http://gcc.gnu.org/ml/gcc/2002-06/msg01709.html > Would you mind verifying whether this fix indeed resolves > your bug? Thanks! > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6957 The bug appears to be fixed! I also verified that the resulting GCC is capable of completing a "make world" on FreeBSD-current, just as an additional regression test ... Regards, STefan
next reply other threads:[~2002-06-29 20:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-29 13:36 Stefan Esser [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-06-29 14:46 gerald 2002-06-28 5:56 gerald 2002-06-07 9:06 se
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=20020629203601.12687.qmail@sources.redhat.com \ --to=se@freebsd.org \ --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).