public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38909] FAIL: gcc.target/i386/sse4_2-popcntl.c (test for excess errors)
Date: Mon, 19 Jan 2009 00:12:00 -0000 [thread overview]
Message-ID: <20090119001154.30215.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38909-276@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from howarth at nitro dot med dot uc dot edu 2009-01-19 00:11 -------
This is a pre-existing problem in gcc 4.3 branch which should be fixable with a
backport of...
Author: uros
Date: Sat Nov 22 14:16:57 2008
New Revision: 142121
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=142121
Log:
PR target/38222
* config/i386/i386.md (SWI248): New mode iterator.
(SWI32): Remove mode iterator.
(popcount<mode>2): Rename from popcounthi2, popcountsi2 and
popcounthi2 insn patterns. Macroize pattern using SWI248 mode
iterator. Generate popcnt mnemonic without mode extensions
for Darwin x86 targets.
(*popcount<mode>2_cmp): Ditto.
(*popcountsi2_cmp_zext): Generate popcnt mnemonic without mode
extensions for Darwin x86 targets.
testsuite/ChangeLog:
PR target/38222
* gcc.target/i386/funcspec-3.c: Scan for popcnt on Darwin targets.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386.md
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.target/i386/funcspec-3.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38909
next prev parent reply other threads:[~2009-01-19 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 23:22 [Bug target/38909] New: " danglin at gcc dot gnu dot org
2009-01-19 0:12 ` howarth at nitro dot med dot uc dot edu [this message]
2009-01-19 0:14 ` [Bug target/38909] " howarth at nitro dot med dot uc dot edu
2009-01-19 1:25 ` dave at hiauly1 dot hia dot nrc dot ca
2009-06-11 8:56 ` [Bug target/38909] [4.3 only] " fxcoudert at gcc dot gnu dot org
2009-06-11 17:36 ` ubizjak at gmail dot com
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=20090119001154.30215.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).