public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/8878: miscompilation with -O and SSE
Date: Thu, 03 Apr 2003 19:36:00 -0000	[thread overview]
Message-ID: <20030403193600.18960.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/8878; it has been noted by GNATS.

From: Janis Johnson <janis187@us.ibm.com>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
   gcc-prs@gcc.gnu.org, kronoz@tiscali.it, aldyh@redhat.com
Cc:  
Subject: Re: optimization/8878: miscompilation with -O and SSE
Date: Thu, 03 Apr 2003 11:36:47 -0800

 This was fixed on mainline by the following patch, whose
 date is actually 2003-04-01:
 
 2003-02-31  Aldy Hernandez  <aldyh@redhat.com>
 
         * testsuite/gcc.c-torture/execute/simd-3.c: New.
 
         * expr.c (expand_expr): Handle VECTOR_CST.
           (const_vector_from_tree): New.
 
         * varasm.c (output_constant): Handle VECTOR_CST.
 
         * c-typeck.c (digest_init): Build a vector constant from a
           VECTOR_TYPE.
 
         [lots of changes to files in config/rs6000]
 
 My hunt used the testcase that Volker sent me yesterday
 and checked that the generated .s file did not include
 'mulps'.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8878
 
 
 


             reply	other threads:[~2003-04-03 19:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-03 19:36 Janis Johnson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-02 16:34 reichelt
2003-04-02 20:16 Volker Reichelt
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=20030403193600.18960.qmail@sources.redhat.com \
    --to=janis187@us.ibm.com \
    --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).