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: ICE in gen_reg_rtx, at emit-rtl.c:662
Date: Sat, 26 Oct 2002 02:46:00 -0000 [thread overview]
Message-ID: <20021026094601.11610.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: gcc-gnats@gcc.gnu.org
Cc: tneumann@pi3.informatik.uni-mannheim.de
Subject: Re: optimization/8300: ICE in gen_reg_rtx, at emit-rtl.c:662
Date: Sat, 26 Oct 2002 11:40:12 +0200
--AhhlLboLdkugWU4S
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Oct 21, 2002 at 01:04:31PM -0000, Robert Schiele wrote:
>=20
> >Number: 8300
> >Category: optimization
> >Synopsis: ICE in gen_reg_rtx, at emit-rtl.c:662
> >Confidential: no
> >Severity: serious
> >Priority: medium
> >Responsible: unassigned
> >State: open
> >Class: ice-on-legal-code
^^^^^^^^^^^^^^^^^
I submitted this with class ice-on-legal-code. Now someone changed
this silently to ice-on-illegal-code in the database.
> void a() {
> double b;
> int c =3D *((int*)&b) && (*(&c + 1) =3D 0);
> }
If you are the one that changed this, could you please explain, why
you consider this illegal! Yes, it is braindead and stupid, but I
can't find a reason why this should be illegal. But hey, it is just a
sample to show a bug in gcc, it does not need to make sense, does it?
Anyway, why are such things silently changed without notification of
the interrested parties? I think this is somewhat annoying.
Robert
--=20
Robert Schiele Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
--AhhlLboLdkugWU4S
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iQEVAwUBPbpi/MQAnns5HcHpAQFQjgf/ZMqbLphimq9UUnfN4RsfO5qkm0iTjy9u
WfXqm9iLR9j+LFIYj+OOFaFKbHEdyoWbUu+RRGZbZ6twtHkUFFSxu9+8T7xaY+UZ
GOocC9Hb7AFVMVDjxKu5NJIDEK3bhG2b/0oj45MKTNnb+TI2szXM2DPIgS3uYOaE
8aGE/fY1wTnbAVMPHtINV+EGwioHUSX7hpahsFR/uwMJbFrdGcrYAU5f0v7NNvTr
CQddOafVU392B/qGHp2tJJPR2N9cspO0dw3SCTBbspwAPc910WkYiSj3mV6fwKbC
1ZgxCp59JJxrxwN2gKlFJBmMMXgPEEVgcSK7lb+rsSUQDGe1Ordt1Q==
=pPFN
-----END PGP SIGNATURE-----
--AhhlLboLdkugWU4S--
next reply other threads:[~2002-10-26 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-26 2:46 Robert Schiele [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-03 9:56 Christian Ehrhardt
2002-10-21 6:06 rschiele
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=20021026094601.11610.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).