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 05:16:00 -0000	[thread overview]
Message-ID: <20030317051601.8656.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: 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 06:08:21 +0100

 --/04w6evG8XlLl3ft
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Sun, Mar 16, 2003 at 11:26:37PM -0000, rth@gcc.gnu.org wrote:
 > Synopsis: [3.2/3.3/3.4 regression] [sparc] ICE in gen_reg_rtx, at emit-rt=
 l.c:662
 >=20
 > State-Changed-From-To: analyzed->open
 > State-Changed-By: rth
 > State-Changed-When: Sun Mar 16 23:26:37 2003
 > State-Changed-Why:
 >     The code is illegal because *(&c+1) is not an object.
 
 Well, I can show that this is not the problem:
 
 Rewriting the code as
 
 void a() {
     double b;
     int c;
     c =3D *((int*)&b) && (*(&c + 1) =3D 0);
 }
 
 shows the same problem and as c is explicitly defined here _before_,
 *(&c + 1) is also well defined.
 
 And then we have two bugs here:
 
 1. My rewritten example is legal code with no doubt and produces an
    ICE whit optimization.
 
 2. The original sample is accepted is accepted without optimization,
    although you say, it is illegal.
 
 Robert
 
 --=20
 Robert Schiele			Tel.: +49-621-181-2517
 Dipl.-Wirtsch.informatiker	mailto:rschiele@uni-mannheim.de
 
 --/04w6evG8XlLl3ft
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.7 (GNU/Linux)
 
 iQEVAwUBPnVYRcQAnns5HcHpAQE18AgAiDhqYRS/sUWexdcCwHXNE5QZKiVm7KjS
 u5LcL0t87k0kBf6X+EUpIre4T/rWPopJXOpiquH3jkl/9ikeI18aWQ9gwRWkcAx6
 CVtCYfzCgmmBUwvkfUL7ckFu0UTL3wzixc7Fsu34qAgcyKfOGrruuyE/JHdfcsD4
 5YU2S6mQKJvTt3aeXD5rn5Zpn3/QIGvCdZAiJm4GI51h4bX7Mgw9iXGnUYXzgGzp
 bZbFjMpcVSlZWSn24ToMheNMpMRmgkYCGEQ1nH7XXms1Fwd+O6gk1isFI61JuyZq
 YPJ43pZfyuUth2YUhOcVnmhlimoCgWmyz5RJ2klpPAB2MgUDJJP/SA==
 =lc5E
 -----END PGP SIGNATURE-----
 
 --/04w6evG8XlLl3ft--
 


             reply	other threads:[~2003-03-17  5:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-17  5:16 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:26 Robert Schiele
2003-03-17  9:16 Richard Henderson
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=20030317051601.8656.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).