public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: java/8866: [3.3/3.4 regression] Bug in switch statement code generation -- missing label Date: Tue, 11 Feb 2003 22:16:00 -0000 [thread overview] Message-ID: <20030211221601.5123.qmail@sources.redhat.com> (raw) The following reply was made to PR java/8866; it has been noted by GNATS. From: Tom Tromey <tromey@redhat.com> To: Steven Bosscher <s.bosscher@student.tudelft.nl> Cc: gcc-gnats@gcc.gnu.org, green@redhat.com Subject: Re: java/8866: [3.3/3.4 regression] Bug in switch statement code generation -- missing label Date: 11 Feb 2003 14:58:12 -0700 Steven> This is almost certainly a duplicate of c/7887, which I have tracked Steven> down to a bug in crossjumping or cfgcleanup. Thanks. I added myself to the CC list for 7887. That way if it is fixed I'll remember to check 8866 as well. Tom
next reply other threads:[~2003-02-11 22:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-11 22:16 Tom Tromey [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-06 0:16 Steven Bosscher 2003-02-13 23:26 Graham Stott 2003-02-13 19:13 tromey 2003-02-11 22:06 Steven Bosscher
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=20030211221601.5123.qmail@sources.redhat.com \ --to=tromey@redhat.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).