From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24286 invoked by alias); 1 Jun 2002 18:36:00 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 24272 invoked by uid 71); 1 Jun 2002 18:36:00 -0000 Date: Sat, 01 Jun 2002 11:36:00 -0000 Message-ID: <20020601183600.24271.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "Zephaniah E. Hull" Subject: Re: c/6893: gcc generates invalid code for x86 subarches. Reply-To: "Zephaniah E. Hull" X-SW-Source: 2002-06/txt/msg00012.txt.bz2 List-Id: The following reply was made to PR c/6893; it has been noted by GNATS. From: "Zephaniah E\. Hull" To: Glen Nakamura 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 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--