public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: David.Kastrup@t-online.de To: gcc-gnats@gcc.gnu.org Subject: target/5381: __builtin_ia32_pmulhuw seems unknown to compiler Date: Mon, 14 Jan 2002 12:46:00 -0000 [thread overview] Message-ID: <20020114204434.5393.qmail@sources.redhat.com> (raw) >Number: 5381 >Category: target >Synopsis: __builtin_ia32_pmulhuw seems unknown to compiler >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Jan 14 12:46:02 PST 2002 >Closed-Date: >Last-Modified: >Originator: Myself >Release: gcc version 3.1 20020106 (Red Hat Linux Rawhide 3.1-0.17) >Organization: >Environment: Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.1/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --host=i386-redhat-linux --with-system-zlib Thread model: posix >Description: Strangely, while using -mmmx, __builtin_ia32_pmulhuw is unknown to the compiler, while, for example, __builtin_ia32_pmulhw seems known. Anyhow, as you can see from the generated code, the compiler fails to emit an emmx instruction at the end of the routine, leading to possible floating point errors after return. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="test.c" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="test.c"
next reply other threads:[~2002-01-14 20:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-14 12:46 David.Kastrup [this message] 2002-01-14 18:36 Richard Henderson 2002-01-14 18:43 rodrigc
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=20020114204434.5393.qmail@sources.redhat.com \ --to=david.kastrup@t-online.de \ --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: 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).