public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Volker Reichelt <reichelt@igpm.rwth-aachen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/8878: miscompilation with -O and SSE Date: Wed, 02 Apr 2003 20:16:00 -0000 [thread overview] Message-ID: <20030402201601.20332.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/8878; it has been noted by GNATS. From: Volker Reichelt <reichelt@igpm.rwth-aachen.de> To: janis187@us.ibm.com Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, kronoz@tiscali.it Subject: Re: optimization/8878: miscompilation with -O and SSE Date: Wed, 02 Apr 2003 21:17:49 +0200 (CEST) Hi Janis, PR 8878 got fixed on mainline in the last couple of days (somewhere between 2003-03-29 and 2003-04-02). Since the bug is in the category "wrong-code" it would be nice if the patch could be backported to 3.3 (and maybe even 3.2) to prevent silent miscompilations. Could you please identify the patch that fixed the problem? Maybe the following testcase is more convenient for the hunt, since you can check the return value instead of the output: ------------------------snip here---------------------------- typedef int v4sf __attribute__((mode(V4SF))); int main(void) { v4sf v = {1.0, 2.0, 3.0, 4.0}; union { v4sf v; float f[4]; } u; u.v = __builtin_ia32_mulps(v,v); return u.f[0]; } ------------------------snip here---------------------------- Just compile with "gcc -march=i686 -msse -O". Thanks, Volker http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8878
next reply other threads:[~2003-04-02 20:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-02 20:16 Volker Reichelt [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-02 16:34 reichelt 2003-04-03 19:36 Janis Johnson 2003-04-02 20:16 Janis Johnson 2002-12-11 6:08 reichelt 2002-12-09 9:56 Luca Kronos Tettamanti
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=20030402201601.20332.qmail@sources.redhat.com \ --to=reichelt@igpm.rwth-aachen.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).