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 16:26:00 -0000 [thread overview] Message-ID: <20030317162601.16156.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: Andreas Schwab <schwab@suse.de> Cc: Richard Henderson <rth@redhat.com>, gcc-bugs@gcc.gnu.org, tneumann@pi3.informatik.uni-mannheim.de, gcc-gnats@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 17:21:09 +0100 --zYM0uCDKw75PZbzx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 17, 2003 at 04:34:38PM +0100, Andreas Schwab wrote: > Ignoring the missing initialisation of b this is undefined under the > aliasing rules. Ok, behaviour is undefined. As this is only a sample to produce an ICE, this is no problem for me. But do you think this code is illegal in the sense that the compiler cannot generate valid code out of it? In that case I would be happy about a pointer to the specs that tell me that this is not allowed. Does any spec _force_ me to initialize b? When I do so, the error is vanished. Again, I don't care about undefined behaviour here. This is also the reason, why I omitted the initialization. My point, as far as I understand this situation, is that the compiler should generate a binary out of it. The resulting code is completely braindead --- I know that --- and may even SIGBUS or whatever he likes to do at _runtime_, but I don't see, why this should be seen as illegal at _compile_ time. Robert --=20 Robert Schiele Tel.: +49-621-181-2517 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de --zYM0uCDKw75PZbzx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iQEVAwUBPnX19cQAnns5HcHpAQE0eQf+OwHgQFADbOzdB+JUVaoaEijwNmsBWOQJ anM6xWORACaUSerUBJCb+Ox3jCnU1Yq8r9+a4uvZtZGkkMMVocazUsjzia929FJE Y1tO43j1/eEnP5H90w2zIN1XoA14WdG+4PtohkFd1xJ0BorbpcYBQrTMG1rdkZ7n xkYwaKtIGLxXYrjuG1MVafR44OyryOqbBkhLGwkqpBmVMUeoYAAmXLCY574dwR3d Y6Gblg4ztu7958XNdUqPMhlFL/6Ik6jih1foG80OcEX3gM/VuAdGVOBrT11i4oIw jhPAWXqBjjRYCiRpp0FuznB5jIoxKdvm5etjMo0sHmpTMQGaI2jRhg== =tUq4 -----END PGP SIGNATURE----- --zYM0uCDKw75PZbzx--
next reply other threads:[~2003-03-17 16:26 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-17 16: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 15:56 Robert Schiele 2003-03-17 15:36 Andreas Schwab 2003-03-17 15:26 Falk Hueffner 2003-03-17 15:26 Robert Schiele 2003-03-17 14:36 Daniel Jacobowitz 2003-03-17 9:26 Robert Schiele 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=20030317162601.16156.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: linkBe 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).