From: Jim Wilson <wilson@cygnus.com>
To: law@cygnus.com
Cc: Kamil Iskra <kamil@dwd.interkom.pl>, egcs@cygnus.com
Subject: Re: Loop optimizer misses simple optimisation?
Date: Sun, 03 May 1998 15:32:00 -0000 [thread overview]
Message-ID: <199805032232.PAA08246@rtl.cygnus.com> (raw)
In-Reply-To: <19466.894225692@hurl.cygnus.com>
However, a div or mod operation can not generally be moved out of
a loop unless you know it won't trap (divide by zero).
If an instruction might trap, then it will be moved out of a loop if we
can prove that it will be executed at least once.
Jim
next prev parent reply other threads:[~1998-05-03 15:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-28 7:23 Kamil Iskra
1998-04-28 19:14 ` Richard Henderson
1998-04-29 14:48 ` PÃ¥l-Kristian Engstad
1998-04-29 16:08 ` Richard Henderson
1998-04-28 19:49 ` Michael Meissner
1998-04-29 15:21 ` Jim Wilson
1998-05-02 6:13 ` Kamil Iskra
1998-05-03 14:15 ` Jeffrey A Law
1998-05-03 15:32 ` Jim Wilson [this message]
1998-05-03 20:10 ` Jeffrey A Law
1998-05-06 7:42 ` Was: " John Vickers
1998-05-06 9:19 ` Jeffrey A Law
1998-05-06 11:36 ` Joern Rennecke
1998-05-07 5:15 ` John Vickers
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=199805032232.PAA08246@rtl.cygnus.com \
--to=wilson@cygnus.com \
--cc=egcs@cygnus.com \
--cc=kamil@dwd.interkom.pl \
--cc=law@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).