public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/1259] string constants not handled properly Date: Wed, 01 Jun 2005 21:12:00 -0000 [thread overview] Message-ID: <20050601211226.8925.qmail@sourceware.org> (raw) In-Reply-To: <20001220121823.1259.tromey@gcc.gnu.org> ------- Additional Comments From tromey at gcc dot gnu dot org 2005-06-01 21:12 ------- One example of a failure is the test case in PR 21722. In this PR we generate this bytecode in A.class: 0: ldc #9=<String "foo"> 2: astore_1 3: getstatic #15=<Field b.B.FOO java.lang.String> 6: aload_1 7: invokevirtual #21=<Method java.lang.String.equals (java.lang.Object)boolean> However, as B.FOO is a compile-time constant, we should not have a 'getstatic' here. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1259
next prev parent reply other threads:[~2005-06-01 21:12 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20001220121823.1259.tromey@gcc.gnu.org> 2004-11-07 23:27 ` pinskia at gcc dot gnu dot org 2004-11-07 23:42 ` pinskia at gcc dot gnu dot org 2005-06-01 21:12 ` tromey at gcc dot gnu dot org [this message] [not found] <bug-1259-360@http.gcc.gnu.org/bugzilla/> 2007-01-09 20:43 ` tromey at gcc dot gnu dot org
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=20050601211226.8925.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-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).