public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joern Rennecke <amylaar@onetel.net.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/7799: [3.2/3.3 regression] Loop bug with optimization flag -Os in gcc
Date: Thu, 19 Dec 2002 22:16:00 -0000	[thread overview]
Message-ID: <20021220061602.18608.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/7799; it has been noted by GNATS.

From: Joern Rennecke <amylaar@onetel.net.uk>
To: segher@koffie.nl (Segher Boessenkool)
Cc: ehrhardt@mathematik.uni-ulm.de (Christian Ehrhardt),
        nejataydin@superonline.com, gcc-gnats@gcc.gnu.org, gcc@gcc.gnu.org,
        gcc-bugs@gcc.gnu.org
Subject: Re: optimization/7799: [3.2/3.3 regression] Loop bug with optimization flag -Os in gcc
Date: Fri, 20 Dec 2002 06:17:18 +0000 (GMT)

 > 6.2.5.19:
 >         ... An array type describes a contiguously allocated nonempty set of
 >         objects with a particular member object type, called the element
 >         type. ...
 >
 > So an array can not wrap around address 0.
 
 It can't wrap around there, but if pointers are signed, it might straddle 0
 nonetheless.  This requires, of course, for an aligned start address
 that the address 0 is not the same as NULL, which AFAICR is something gcc
 doesn't currently support.
 
 OTOH, if the start address is not aligned to a multiple of the types size,
 you can have the array straddle address 0 without it ever being a valid
 address.  Well, that is if character pointers have a different
 representation ;-)


             reply	other threads:[~2002-12-20  6:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19 22:16 Joern Rennecke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-20 16:36 Robert Dewar
2002-12-20  1:26 Christian Ehrhardt
2002-12-19 19:26 Segher Boessenkool
2002-12-13 10:06 Eric Botcazou
2002-12-13  6:56 Christian Ehrhardt
2002-12-13  5:56 Eric Botcazou
2002-12-13  5:46 Christian Ehrhardt
2002-12-06 12:52 bangerth

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=20021220061602.18608.qmail@sources.redhat.com \
    --to=amylaar@onetel.net.uk \
    --cc=gcc-prs@gcc.gnu.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: 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).