public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: douze@enseeiht.fr
To: gcc-gnats@gcc.gnu.org
Subject: target/10077: gcc -msse2 generates movd to move dwords between xmm regs
Date: Fri, 14 Mar 2003 08:16:00 -0000	[thread overview]
Message-ID: <20030314081457.17020.qmail@sources.redhat.com> (raw)


>Number:         10077
>Category:       target
>Synopsis:       gcc -msse2 generates movd to move dwords between xmm regs
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Mar 14 08:16:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     douze@enseeiht.fr
>Release:        gcc 3.2.2 on x86
>Organization:
>Environment:
Linux 2.4.18
>Description:
The bug appears when I compile a function with many variables. GCC then uses xmm registers as 32-bit scalar integer registers.

When it has to move data with an xmm register involved, it generates a movd instruction, which doesn't work (movss might work better). Although there is sse2 assembly in my code, I don't think it comes from there. 

The assembler used is GNU assembler version 2.11.92.0.10 (i486-suse-linux) using BFD version 2.11.92.0.10 20011021 (SuSE)
>How-To-Repeat:
Compile the code with 

gcc -c gcc_bug.i -msse2 -O3
>Fix:
replace movd with movss in the .s file
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="gcc_bug.i"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="gcc_bug.i"

CiAKdHlwZWRlZiBpbnQgbTEyOCAKICAgIF9fYXR0cmlidXRlX18gKChfX21vZGVfXyhfX1Y0U0lf
XyksYWxpZ25lZCgxNikpKTsKCiAKc3RhdGljIF9faW5saW5lIG0xMjggeG1tX21hZGQobTEyOCBh
LG0xMjggYixtMTI4IGMpIHsKICBhc20gdm9sYXRpbGUoCiAgICAgICIgIHBtYWRkd2QgJTIsJTBc
biIKICAgICAgIiAgcGFkZGQgJTAsJTFcbiIKICAgICAgOiAiK3giIChiKSwiK3giIChjKQogICAg
ICA6ICJ4bSIgKGEpKTsKICByZXR1cm4gYzsKfQoKIAogCnN0YXRpYyBfX2lubGluZSBpbnQgeG1t
X2dldF8zMihtMTI4IGEpIHsKICBpbnQgYjsgCiAgYXNtIHZvbGF0aWxlKAogICAgICAiICBtb3Zk
ICUxLCUwIiAKICAgICAgOiAiPXEiIChiKQogICAgICA6ICJ4IiAoYSkpOwogIHJldHVybiBiOwp9
CgoKCgoKCgp2b2lkIGF0cmFfcygKICAgIHNob3J0ICphLGludCBtLGludCBuLGludCBsZGEsCiAg
ICBkb3VibGUgKmF0YSkgewogIGludCBpMSxqMTsKICBpbnQgbmQ9bi8gOCAsbmM9bmQqIDggOwog
IGludCBtZD1tLyA4ICxtYz1tZCogOCA7CgogIGZvcihpMT0wO2kxPG5kO2kxKyspIHsKICAgIHNo
b3J0ICpiaT1hK2xkYSppMSogOCA7CgogICAgZm9yKGoxPWkxKzE7ajE8bmQ7ajErKykgewogICAg
ICBtMTI4IGFjY3VbOCAqIDggXTsKICAgICAgc2hvcnQgKmJqPWErbGRhKmoxKiA4IDsKICAgICAg
aW50IGksaixrOwogICAgICBkb3VibGUgKmF0YV9sPWF0YStpMSogOCArajEqIDggKm47CiAgICAg
CiAgICAgIGZvcihrPTA7azxtZDtrKyspIHsKICAgICAgICBzaG9ydCAqbGk9YmkrayogOCA7CiAg
ICAgICAgc2hvcnQgKmxqPWJqK2sqIDggOwogICAgICAgIGZvcihqPTA7ajwgOCA7aisrKSBmb3Io
aT0wO2k8IDggO2krKykgewoJICBtMTI4IGFjY3UxOwogICAgICAgICAgbTEyOCAqbWk9KHZvaWQq
KShsaStpKmxkYSk7CiAgICAgICAgICBtMTI4ICptaj0odm9pZCopKGxqK2oqbGRhKTsKICAgICAg
ICAgIGFjY3UxPWFjY3VbaStqKiA4IF07CgkgIAkgIAogICAgICAgICAgYWNjdTE9eG1tX21hZGQo
bWlbMF0sbWpbMF0sYWNjdTEpOwoJICAKCSAgYWNjdVtpK2oqIDggXT1hY2N1MTsKICAgICAgICB9
ICAgICAgICAKICAgICAgfQoKCiAgICAgIGZvcihqPTA7ajwgOCA7aisrKSBmb3IoaT0wO2k8IDgg
O2krKykgewogICAgICAgIHNob3J0ICpsaT1iaStpKmxkYTsKICAgICAgICBzaG9ydCAqbGo9Ymor
aipsZGE7CiAgICAgICAgaW50IGFjY3UxOwoJYWNjdTE9eG1tX2dldF8zMihhY2N1W2kraiogOCBd
KTsKCQogICAgICAgIGZvcihrPW1jO2s8bTtrKyspIHsKICAgICAgICAgIGFjY3UxKz1saVtrXSps
altrXTsKCX0KICAgICAgICBhdGFfbFtpK2oqbl09YWNjdTE7CiAgICAgIH0KICAgICAgCiAgICB9
CiAgfQoKfQoKCgoKCg==


             reply	other threads:[~2003-03-14  8:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14  8:16 douze [this message]
2003-03-14  9:36 Andreas Jaeger
2003-03-14 12:05 aj
2003-03-14 15:12 bangerth
2003-04-14 14:13 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=20030314081457.17020.qmail@sources.redhat.com \
    --to=douze@enseeiht.fr \
    --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).