public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/52908] xop-mul-1:f9 miscompiled on bulldozer (-mxop) Date: Fri, 04 May 2012 12:52:00 -0000 [thread overview] Message-ID: <bug-52908-4-8JZVsnJbJv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52908-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52908 --- Comment #5 from Uros Bizjak <ubizjak at gmail dot com> 2012-05-04 12:51:49 UTC --- (In reply to comment #4) > A Quick make check on i386.exp result is shown below: > > Tests that now fail, but worked before: > > gcc.target/i386/xop-imul32widen-vector.c scan-assembler vpmacsdql This is expected, there is no need to emit vpmacsdql, IMO vpmuldq works as good (if not even better, since we don't have to preload accumulator with zero). The test should be either changed to really emit vpmacsdql, or asm scan should be adjusted. > Tests that now work, but didn't before: > > gcc.target/i386/xop-mul-1.c execution test Yes this one should be fixed with the patch. If the change vmpacsdql -> vpmuldq is OK with you, I can commit the patch, but I'd ask you for full bootstrap/regression test.
next prev parent reply other threads:[~2012-05-04 12:52 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-08 22:48 [Bug target/52908] New: " matz at gcc dot gnu.org 2012-04-09 8:17 ` [Bug target/52908] " ubizjak at gmail dot com 2012-04-09 11:48 ` ubizjak at gmail dot com 2012-04-10 13:49 ` ubizjak at gmail dot com 2012-05-04 10:43 ` venkataramanan.kumar at amd dot com 2012-05-04 12:52 ` ubizjak at gmail dot com [this message] 2012-05-09 3:44 ` venkataramanan.kumar at amd dot com 2012-05-09 20:46 ` uros at gcc dot gnu.org 2012-05-09 20:57 ` ubizjak at gmail dot com 2012-05-10 6:22 ` ubizjak at gmail dot com 2012-06-18 15:11 ` vekumar at gcc dot gnu.org 2012-07-02 12:42 ` rguenth at gcc dot gnu.org 2024-03-17 2:33 ` sjames at gcc dot gnu.org
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=bug-52908-4-8JZVsnJbJv@http.gcc.gnu.org/bugzilla/ \ --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: 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).