public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: r.hautz@inn-salzach.de To: gcc-gnats@gcc.gnu.org Subject: java/6729: Compiler error causing break of java.lang.Character.isWhitespace Date: Sun, 19 May 2002 21:26:00 -0000 [thread overview] Message-ID: <200205200358.g4K3wWns001690@isabella.iivs.de> (raw) >Number: 6729 >Category: java >Synopsis: Compiler error causing break of java.lang.Character.isWhitespace >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Sun May 19 21:26:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Roland Hautz >Release: 3.2 20020516 (experimental) >Organization: >Environment: System: Linux isabella 2.4.18-4GB #1 Wed Mar 27 13:57:05 UTC 2002 i586 unknown Architecture: i586 host: i586-pc-linux-gnu build: i586-pc-linux-gnu target: i586-pc-linux-gnu configured with: /home/roland/gcc/configure --enable-threads=posix --enable-languages=c,c++,java >Description: I tracked down the reason, why java.io.StreamTokenizer can't parse numbers any longer. The testcase is narrowed from java.lang.Character.isWhitespace, which is returning true on digits because of this bug. I consider this to be of high priority. >How-To-Repeat: # gcj -g --main=HelloWorld HelloWorld.java # ./a.out this should be false: true public class HelloWorld { static int attr = 0x9; public static void main(String [] args) { boolean res = ( ( 1 << attr ) & 0x1000 ) != 0 ; System.out.println("this should be "+res+": "+isWhite()); } public static boolean isWhite() { return ( ( 1 << attr ) & 0x1000 ) != 0 ; } } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-05-20 4:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-19 21:26 r.hautz [this message] 2002-05-22 20:36 Bryce McKinlay 2002-05-27 11:56 Andrew Haley 2002-05-29 23:26 bryce
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=200205200358.g4K3wWns001690@isabella.iivs.de \ --to=r.hautz@inn-salzach.de \ --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).