public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: tromey@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, java-prs@gcc.gnu.org, mark@klomp.org, nobody@gcc.gnu.org, tromey@gcc.gnu.org Subject: Re: java/6388: Integer.MIN_VALUE == 0x80000000 optimized to false on powerpc Date: Wed, 12 Jun 2002 10:06:00 -0000 [thread overview] Message-ID: <20020612170605.25748.qmail@sources.redhat.com> (raw) Synopsis: Integer.MIN_VALUE == 0x80000000 optimized to false on powerpc Responsible-Changed-From-To: unassigned->tromey Responsible-Changed-By: tromey Responsible-Changed-When: Wed Jun 12 10:06:04 2002 Responsible-Changed-Why: I'm handling this. State-Changed-From-To: open->analyzed State-Changed-By: tromey State-Changed-When: Wed Jun 12 10:06:04 2002 State-Changed-Why: The lexer assumes that HOST_WIDE_INT is 32 bits, leading to problems on PPC Linux, where it is 64 bits. I wrote a first hacky patch, but it needs a rewrite. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6388
next reply other threads:[~2002-06-12 17:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-12 10:06 tromey [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-05 16:02 tromey 2002-04-21 2:06 mark
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=20020612170605.25748.qmail@sources.redhat.com \ --to=tromey@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=java-prs@gcc.gnu.org \ --cc=mark@klomp.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: 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).