public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/1824: gcc accepts computed goto's + -fprofile-arcs, gcov barfs Date: Thu, 05 Dec 2002 14:16:00 -0000 [thread overview] Message-ID: <20021205221602.7308.qmail@sources.redhat.com> (raw) The following reply was made to PR other/1824; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: Brad Lucier <lucier@math.purdue.edu> Cc: gcc-gnats@gcc.gnu.org Subject: Re: other/1824: gcc accepts computed goto's + -fprofile-arcs, gcov barfs Date: Thu, 5 Dec 2002 16:06:27 -0600 (CST) On Thu, 5 Dec 2002, Brad Lucier wrote: > I think this is fixed, but I won't be able to check it until next week. OK, thanks. I will be waiting with closing the report then. It would be nice if you could give it a spin sometimes. Thanks Wolfgang > > > > > Synopsis: gcc accepts computed goto's + -fprofile-arcs, gcov barfs > > > > State-Changed-From-To: open->feedback > > State-Changed-By: bangerth > > State-Changed-When: Thu Dec 5 12:11:14 2002 > > State-Changed-Why: > > Brad, the report does not contain a testcase, so I cannot > > check myself. But do you know whether this has improved in > > the last nearly 2 years? > > > > Thanks > > Wolfgang > > > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=1824 > > > ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-12-05 22:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-05 14:16 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-11 12:28 bangerth 2002-12-05 12:11 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=20021205221602.7308.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --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).