From: Alexandre Oliva <aoliva@redhat.com>
To: dewar@gnat.com (Robert Dewar)
Cc: kenner@vlsi1.ultra.nyu.edu, gcc@gcc.gnu.org
Subject: Re: Bug in loop optimize (invalid postinc to preinc transformation)
Date: Thu, 28 Dec 2000 12:21:00 -0000 [thread overview]
Message-ID: <orsnn89u6j.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20001228134026.EC58D34D93@nile.gnat.com>
On Dec 28, 2000, dewar@gnat.com (Robert Dewar) wrote:
> then this is defined only if the resulting pointer remains within the
> same object, or in the csae of arrays it can go just past the end. Overflow
> per se does not arise with pointers because of this stricter rule.
Only if the compiler guarantees that no array will ever be placed
across the wrapping boundary.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2000-12-28 12:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-28 5:40 Robert Dewar
2000-12-28 12:21 ` Alexandre Oliva [this message]
2000-12-28 14:32 ` Geoff Keating
2000-12-28 15:22 ` Tim Hollebeek
2000-12-28 22:20 ` Dave Korn
2000-12-29 0:52 ` Richard Henderson
2000-12-29 1:51 ` Tim Hollebeek
-- strict thread matches above, loose matches on Subject: below --
2000-12-31 8:30 dewar
2001-01-03 0:52 ` Jamie Lokier
2000-12-29 18:43 dewar
2000-12-30 15:18 ` Toon Moene
2000-12-28 20:33 dewar
2000-12-28 1:14 Richard Kenner
2000-12-27 22:40 Robert Dewar
2000-12-29 18:36 ` Jamie Lokier
2000-12-27 3:04 Bug in loop optimize (TREE stage) David Korn
2000-12-27 15:42 ` Bug in loop optimize (invalid postinc to preinc transformation) Peter Osterlund
2000-12-27 19:55 ` Alexandre Oliva
2000-12-27 21:09 ` Torbjorn Granlund
2000-12-27 21:20 ` Alexandre Oliva
2000-12-27 22:24 ` Jamie Lokier
2000-12-31 8:25 ` Andreas Schwab
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=orsnn89u6j.fsf@guarana.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=dewar@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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).