public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Zephaniah E. Hull" <warp@babylon.d2dc.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/6893: gcc generates invalid code for x86 subarches. Date: Sat, 01 Jun 2002 11:36:00 -0000 [thread overview] Message-ID: <20020601183600.24271.qmail@sources.redhat.com> (raw) The following reply was made to PR c/6893; it has been noted by GNATS. From: "Zephaniah E\. Hull" <warp@babylon.d2dc.net> To: Glen Nakamura <glen@imodulo.com> Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: c/6893: gcc generates invalid code for x86 subarches. Date: Sat, 1 Jun 2002 14:30:28 -0400 --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 01, 2002 at 05:48:44AM -1000, Glen Nakamura wrote: > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&database= =3Dgcc&pr=3D6893 >=20 > Aloha, >=20 > Looks like the testcase you provided has an aliasing problem: > icolor =3D (int *) tmp; >=20 > Strict aliasing does not allow casting from (float *) to (int *)... > You will need to fix your code or compile w/ -fno-strict-aliasing. > See the GCC documentation on -fstrict-aliasing for more information. Ah, thank you. Caught by changes in what is activated by -O2. Now if I can isolate what is getting killed by -fregmove I'll have this actually working properly with gcc 3.1. >=20 > Please check if your problem persists with the attached testcase. Seems to be gone. >=20 > - Glen Nakamura Zephaniah E. Hull. --=20 1024D/E65A7801 Zephaniah E. Hull <warp@babylon.d2dc.net> 92ED 94E4 B1E6 3624 226D 5727 4453 008B E65A 7801 CCs of replies from mailing lists are requested. Well, of course. That's what Unix sysadmins do. We make things work. Even if they're things which are outside our job description or supposed area of expertise. As to the other proposal of breaking them for 6 months first, I will offer a quote from an MCSE I once met: "You're a Unix sysadmin? You're the bad guys. You keep things working." Pretty obvious who gets paid when things break, and who gets paid when they don't. -- Dan Birchall in the Scary Devil Monastery. --/04w6evG8XlLl3ft Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE8+RLDRFMAi+ZaeAERArtVAKDQ1NymIFmXH0l1qylBVTCF5YbwhACfQBcc nBrvH6UBcKsmBXqOOd8ZJz4= =rXBJ -----END PGP SIGNATURE----- --/04w6evG8XlLl3ft--
next reply other threads:[~2002-06-01 18:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-01 11:36 Zephaniah E. Hull [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-06-01 23:55 rth 2002-06-01 8:56 Glen Nakamura 2002-06-01 6:16 warp
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=20020601183600.24271.qmail@sources.redhat.com \ --to=warp@babylon.d2dc.net \ --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).