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/8204: gcj -O2 to native reorders certain instructions improperly.
Date: Tue, 25 Mar 2003 22:46:00 -0000 [thread overview]
Message-ID: <20030325224600.7980.qmail@sources.redhat.com> (raw)
The following reply was made to PR java/8204; it has been noted by GNATS.
From: Tom Tromey <tromey@redhat.com>
To: bangerth@dealii.org
Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, java-prs@gcc.gnu.org,
nobody@gcc.gnu.org, rsdio@metastatic.org, gcc-gnats@gcc.gnu.org
Subject: Re: java/8204: gcj -O2 to native reorders certain instructions improperly.
Date: 25 Mar 2003 15:36:42 -0700
>>>>> ">" == bangerth <bangerth@dealii.org> writes:
>> (f(s.charAt(i++)) << 4) | (f(s.charAt(i++))))
>> I don't know enough about Java, but in C/C++ this will invoke
>> undefined behavior, since the standard doesn't prescribe
>> which of the two function calls happen first, and with
>> which value of i. Is this different in Java, i.e. does
>> the Java standard give guarantees as to the order in which
>> the sub-statements are executed?
Yes, Java specifies left-to-right evaluation in this situation.
Chances are that this bug is fixed, but I haven't tried it.
Tom
next reply other threads:[~2003-03-25 22:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 22:46 Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-24 15:23 bangerth
2003-03-23 0:06 Casey Marshall
2003-03-22 18:09 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=20030325224600.7980.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: link
Be 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).