public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: gert.vervoort@philips.com
To: gcc-gnats@gcc.gnu.org
Subject: optimization/6783: mmx intrinsics problem with -O2 and -O3 opt.
Date: Thu, 23 May 2002 04:36:00 -0000	[thread overview]
Message-ID: <20020523112850.1109.qmail@sources.redhat.com> (raw)


>Number:         6783
>Category:       optimization
>Synopsis:       mmx intrinsics problem with -O2 and -O3 opt.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Thu May 23 04:36:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     gert.vervoort@philips.com
>Release:        gcc-3.1
>Organization:
>Environment:
vervoort@linux22 [68] > uname -a
Linux linux22 2.4.18 #2 SMP Fri Apr 19 16:21:16 CEST 2002 i686 unknown
vervoort@linux22 [69] >  /cadappl/gcc/3.1/bin/gcc -v                           
Reading specs from /cadappl/gcc/3.1/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs
Configured with: /home/hooft/Level/Work/gcc/gcc-3.1/gcc-3.1/configure --prefix=/cadappl/gcc/3.1 --enable-shared --enable-languages=c,c++,f77
Thread model: single
gcc version 3.1
>Description:
gcc 3.1 generates wrong code when using mmx intrinsics
with '-O2' and '-O3'. '-O' works oke.
>How-To-Repeat:
vervoort@linux22 [80] >  /cadappl/gcc/3.1/bin/gcc -O -mmmx intrinsic_mmx_add.c 
vervoort@linux22 [81] > ./a.out 
11 22 33 44 55 66 77 88 
vervoort@linux22 [82] >  /cadappl/gcc/3.1/bin/gcc -O2 -mmmx intrinsic_mmx_add. 
vervoort@linux22 [83] > ./a.out                                                
68 253 2 64 255 255 42 144 
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/x-unknown-content-type-c_auto_file; name="intrinsic_mmx_add.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="intrinsic_mmx_add.c"

I2luY2x1ZGUgPG1taW50cmluLmg+CgptYWluKCkKewogICAgdW5zaWduZWQgY2hhciBhWzhdID0g
ezEsMiwzLDQsNSw2LDcsOH07CiAgICB1bnNpZ25lZCBjaGFyIGJbOF0gPSB7MTAsMjAsMzAsNDAs
NTAsNjAsNzAsODB9OwogICAgdW5zaWduZWQgY2hhciBjWzhdID0gezAsMCwwLDAsMCwwLDAsMH07
CiAgICBfX202NCBtMCxtMSxtMjsKICAgIGludCBpOwogICAgCiAgICBtMCA9ICooX19tNjQgKilh
OwogICAgbTEgPSAqKF9fbTY0ICopYjsKICAgIG0yID0gX21tX2FkZHNfcHU4KG0wLG0xKTsKICAg
ICooX19tNjQgKiljID0gbTI7CgogICAgX21tX2VtcHR5KCk7CgogICAgZm9yKGk9MDtpPDg7aSsr
KQogICAgICAgIHByaW50ZigiJWQgIiwgY1tpXSk7CiAgICBwcmludGYoIlxuIik7CgoKfQo=


             reply	other threads:[~2002-05-23 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-23  4:36 gert.vervoort [this message]
2002-10-03 11:06 hubicka

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=20020523112850.1109.qmail@sources.redhat.com \
    --to=gert.vervoort@philips.com \
    --cc=gcc-gnats@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).