public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bryce@gcc.gnu.org To: apbianco@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: java/1414 Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview] Message-ID: <20010303043600.18891.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR java/1414; it has been noted by GNATS. From: bryce@gcc.gnu.org To: apbianco@gcc.gnu.org, gcc-gnats@gcc.gnu.org, mdejong@cygnus.com Cc: Subject: Re: java/1414 Date: 3 Mar 2001 04:27:51 -0000 Old Synopsis: duplicate switch label problems New Synopsis: Failure to detect duplicate switch labels when generating bytecode State-Changed-From-To: closed->open State-Changed-By: bryce State-Changed-When: Fri Mar 2 20:27:51 2001 State-Changed-Why: Oops. Mo reports that this problem does still occur when generating bytecode. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1414&database=gcc
next reply other threads:[~2001-04-01 0:00 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-04-01 0:00 bryce [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-04-01 0:00 java/1414 Mo DeJong 2001-04-01 0:00 java/1414 bryce 2001-04-01 0:00 java/1414 Bryce McKinlay
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=20010303043600.18891.qmail@sourceware.cygnus.com \ --to=bryce@gcc.gnu.org \ --cc=apbianco@gcc.gnu.org \ --cc=gcc-prs@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).