public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Robert Schiele <rschiele@uni-mannheim.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/8300: [3.2/3.3/3.4 regression] [sparc] ICE in gen_reg_rtx, at emit-rtl.c:662
Date: Mon, 17 Mar 2003 09:26:00 -0000	[thread overview]
Message-ID: <20030317092600.12871.qmail@sources.redhat.com> (raw)

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

From: Robert Schiele <rschiele@uni-mannheim.de>
To: Richard Henderson <rth@redhat.com>, rth@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
   gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
   tneumann@pi3.informatik.uni-mannheim.de, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: optimization/8300: [3.2/3.3/3.4 regression] [sparc] ICE in gen_reg_rtx, at emit-rtl.c:662
Date: Mon, 17 Mar 2003 10:25:04 +0100

 --AqsLC8rIMeq19msA
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Mon, Mar 17, 2003 at 01:05:55AM -0800, Richard Henderson wrote:
 > On Mon, Mar 17, 2003 at 06:08:21AM +0100, Robert Schiele wrote:
 > > *(&c + 1) is also well defined.
 >=20
 > How's that?
 
 It's pointer arithmetic:
 
 Assume you have the following memory layout...
 
 |   |
 +---+
 |   | <=3D=3D ... then the contents of that address is *(&c + 1)
 +---+
 | c |
 +---+
 |   |
 
 It is:
 
 c: The contents of the variable c on the stack.
 
 &c: The address where c is located on the stack.
 
 &c + 1: That address plus 4 byte. (sizeof(int) =3D=3D 4 on sparc)
 
 *(&c + 1): The contents of the above address.
 
 > > 1. My rewritten example is legal code with no doubt and produces an
 > >    ICE whit optimization.
 >=20
 > Nyet.
 
 Well, I still don't see why this is illegal. Can you give me the
 paragraph of the C standard that prohibits this sort of pointer
 arithmetic?
 
 Robert
 
 --=20
 Robert Schiele			Tel.: +49-621-181-2517
 Dipl.-Wirtsch.informatiker	mailto:rschiele@uni-mannheim.de
 
 --AqsLC8rIMeq19msA
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.7 (GNU/Linux)
 
 iQEVAwUBPnWUcMQAnns5HcHpAQGdKggAlK9ZV4OgrAY+7UCvuoO7BbUg6PgbHhXQ
 02LxCX3fN5FXsyvj5nVfD8ZbwK42rh6w95hb0XloKZwQMM7+izJala5SEOgghyUN
 l3Wlr7f30yJOudPHFanqBtyfOuQJP9gWBfFIssIDtdAOx+ZpBxb8XGbpex5EAPWG
 T5/DBchE6zrM46R7XCBdRurZ2PFTh6E9k7dJwfjOh+h5O0R6Npvv3NLHuvdfHfJk
 vCfyZgRM8K96KmOzmetAytCsU01aD/6UsGOPhntnlqpOfysC87aPAJ9Zam6wCmMr
 pq8hzQa7hdaVVUjnZbltLMQ/XY1/mHft6S1C95eekY5EPtFVEzCO1w==
 =0Vp8
 -----END PGP SIGNATURE-----
 
 --AqsLC8rIMeq19msA--
 


             reply	other threads:[~2003-03-17  9:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-17  9:26 Robert Schiele [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-24  4:23 rth
2003-03-18 20:29 ebotcazou
2003-03-17 17:16 Robert Schiele
2003-03-17 17:06 Falk Hueffner
2003-03-17 16:56 Joseph S. Myers
2003-03-17 16:26 Robert Schiele
2003-03-17 15:56 Robert Schiele
2003-03-17 15:36 Andreas Schwab
2003-03-17 15:26 Robert Schiele
2003-03-17 15:26 Falk Hueffner
2003-03-17 14:36 Daniel Jacobowitz
2003-03-17  9:16 Richard Henderson
2003-03-17  5:16 Robert Schiele
2003-03-16 23:27 rth
2003-03-16 23:26 rth

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=20030317092600.12871.qmail@sources.redhat.com \
    --to=rschiele@uni-mannheim.de \
    --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).