public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Donn Terry" <donnte@microsoft.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: RE: optimization/6864: Optimizer infinite loop/memory runaway (on gdb sources) Date: Mon, 02 Dec 2002 14:26:00 -0000 [thread overview] Message-ID: <20021202222600.31131.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/6864; it has been noted by GNATS. From: "Donn Terry" <donnte@microsoft.com> To: <bangerth@dealii.org>, "Donn Terry" <donnte@microsoft.com>, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Cc: Subject: RE: optimization/6864: Optimizer infinite loop/memory runaway (on gdb sources) Date: Mon, 2 Dec 2002 14:16:21 -0800 Sorry, but I'm pretty sure it's gone at this point. I don't even remember the details enough to tell you which gdb source file was having the problem. I am pretty sure, however, that it got fixed along the way, as I can now compile gdb successfully. Donn -----Original Message----- From: bangerth@dealii.org [mailto:bangerth@dealii.org]=20 Sent: Monday, December 02, 2002 1:39 PM To: Donn Terry; gcc-bugs@gcc.gnu.org; gcc-prs@gcc.gnu.org; nobody@gcc.gnu.org Subject: Re: optimization/6864: Optimizer infinite loop/memory runaway (on gdb sources) Synopsis: Optimizer infinite loop/memory runaway (on gdb sources) State-Changed-From-To: open->feedback State-Changed-By: bangerth State-Changed-When: Mon Dec 2 13:38:44 2002 State-Changed-Why: It is unfirtunate that nobody has noticed this by now: the attachment to your report is missing. Do you still have it, so that we can attach it to the report? =20 Thanks Wolfgang http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&database=3D= g cc&pr=3D6864
next reply other threads:[~2002-12-02 22:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-02 14:26 Donn Terry [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-02 14:21 bangerth 2002-12-02 13:38 bangerth 2002-05-29 18:53 donnte
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=20021202222600.31131.qmail@sources.redhat.com \ --to=donnte@microsoft.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).