public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/66813] gcc.target/i386/asm-flag-5.c failed with -march=pentium Date: Fri, 10 Jul 2015 11:57:00 -0000 [thread overview] Message-ID: <bug-66813-4-TcCRvL97dR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66813-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66813 --- Comment #2 from uros at gcc dot gnu.org --- Author: uros Date: Fri Jul 10 11:56:48 2015 New Revision: 225662 URL: https://gcc.gnu.org/viewcvs?rev=225662&root=gcc&view=rev Log: PR target/66813 * config/i386/i386.c (ix86_md_asm_adjust): Emit movstrictqi sequence for TARGET_ZERO_EXTEND_WITH_AND targets. testsuite/ChangeLog: PR target/66813 * gcc.target/i386/pr66813.c: New test. Added: trunk/gcc/testsuite/gcc.target/i386/pr66813.c Modified: trunk/gcc/ChangeLog trunk/gcc/config/i386/i386.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2015-07-10 11:57 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-08 17:28 [Bug target/66813] New: " hjl.tools at gmail dot com 2015-07-09 13:11 ` [Bug target/66813] " hjl.tools at gmail dot com 2015-07-10 11:57 ` uros at gcc dot gnu.org [this message] 2015-07-10 12:20 ` 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=bug-66813-4-TcCRvL97dR@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).