From: Joern Rennecke <amylaar@cygnus.co.uk>
To: kaz@cafe.net (Kaz Kylheku)
Cc: amylaar@cygnus.co.uk, tege@pdc.kth.se, wilson@cygnus.com,
law@cygnus.com, egcs@cygnus.com
Subject: Re: x86 failure on loop reversal
Date: Mon, 06 Apr 1998 15:25:00 -0000 [thread overview]
Message-ID: <199804061746.SAA17658@phal.cygnus.co.uk> (raw)
In-Reply-To: <01BD6145.E6CDB300.kaz@cafe.net>
> To create a constant expression which evaluates to the most negative long
> value (assuming, again, 32 bit, two's complement), you must write:
>
> -0x7FFFFFFF - 1
Point taken; it should be -0x7fffffff - 1 in the testcase.
However, gcc doesn't really care; the problem is actually in check_dbra_loop.
next prev parent reply other threads:[~1998-04-06 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-06 17:35 Kaz Kylheku
1998-04-06 15:25 ` Joern Rennecke [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-04-03 21:52 Joern Rennecke
1998-04-08 2:13 ` Jim Wilson
1998-04-08 2:13 ` Jeffrey A Law
1998-04-08 2:13 ` Joern Rennecke
1998-04-08 2:13 ` Jeffrey A Law
1998-04-08 13:11 ` Jim Wilson
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=199804061746.SAA17658@phal.cygnus.co.uk \
--to=amylaar@cygnus.co.uk \
--cc=egcs@cygnus.com \
--cc=kaz@cafe.net \
--cc=law@cygnus.com \
--cc=tege@pdc.kth.se \
--cc=wilson@cygnus.com \
/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).