public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "julia.koval at intel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/66703] [4.9/5/6] gcc.target/i386/readeflags-1.c aborts on -march=i586 or on -miamcu Date: Tue, 07 Jul 2015 09:18:00 -0000 [thread overview] Message-ID: <bug-66703-4-ybT2iBAe1b@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66703-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66703 --- Comment #2 from Yulia Koval <julia.koval at intel dot com> --- Why zero-extend with and is better than zero-extend with movz? Why it's ok to clobber the flags?
next prev parent reply other threads:[~2015-07-07 9:18 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-30 12:01 [Bug target/66703] New: [4.9] gcc.target/i386/readeflags-1.c aborts on -march=i586 julia.koval at intel dot com 2015-07-04 14:24 ` [Bug target/66703] [4.9/5/6] gcc.target/i386/readeflags-1.c aborts on -march=i586 or on -miamcu hjl.tools at gmail dot com 2015-07-07 9:18 ` julia.koval at intel dot com [this message] 2015-07-07 14:48 ` hjl.tools at gmail dot com 2015-07-10 8:49 ` ubizjak at gmail dot com 2015-07-10 12:43 ` hjl.tools at gmail dot com 2015-07-10 15:33 ` uros at gcc dot gnu.org 2015-07-17 16:31 ` uros at gcc dot gnu.org 2015-07-17 18:46 ` uros at gcc dot gnu.org 2015-07-17 18:53 ` 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-66703-4-ybT2iBAe1b@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).