public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: green@redhat.com To: gcc-gnats@gcc.gnu.org Subject: java/8219: gcj order of argument evaluation problem Date: Sun, 13 Oct 2002 23:36:00 -0000 [thread overview] Message-ID: <200210140627.g9E6RMM03375@louie.sfbay.redhat.com> (raw) >Number: 8219 >Category: java >Synopsis: gcj order of argument evaluation problem >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Sun Oct 13 23:36:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: >Release: 3.3 20021005 (experimental) >Organization: >Environment: System: Linux louie 2.4.7-10smp #1 SMP Thu Sep 6 17:09:31 EDT 2001 i686 unknown Architecture: i686 host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: /home/green/FSF/GCC/HEAD/gcc/configure --prefix=/louie/green/latest/i --enable-languages=c,c++,java : (reconfigured) >Description: Here's a bug in how gcj evaluates method arguments.... public class bug { private static int first (int x, int y) { return x; } public static void main (String[] args) { int l = args.length; /* This should print: 0 0 1 */ System.out.println (l); System.out.println (first (l, ++l)); System.out.println (l); } } This is correct output... [green@build green]$ gcj -o bug --main=bug bug.java -O0 [green@build green]$ ./bug 0 0 1 This is bad output... [green@build green]$ gcj -o bug --main=bug bug.java -O2 [green@build green]$ ./bug 0 1 1 Is looks as though the rtl we're generating is bad from the start - so it's unlikely to be a problem with any on the rtl-based optimizations. >How-To-Repeat: See above. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-10-14 6:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-13 23:36 green [this message] 2002-12-01 15:26 tromey
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=200210140627.g9E6RMM03375@louie.sfbay.redhat.com \ --to=green@redhat.com \ --cc=gcc-gnats@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).