public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/66822] New: Turn off X86_TUNE_ZERO_EXTEND_WITH_AND for IAMCU Date: Thu, 09 Jul 2015 11:48:00 -0000 [thread overview] Message-ID: <bug-66822-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66822 Bug ID: 66822 Summary: Turn off X86_TUNE_ZERO_EXTEND_WITH_AND for IAMCU Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: hjl.tools at gmail dot com CC: julia.koval at intel dot com Target Milestone: --- Since X86_TUNE_ZERO_EXTEND_WITH_AND generates bigger code, should it be turned off for IAMCU?
next reply other threads:[~2015-07-09 11:48 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-09 11:48 hjl.tools at gmail dot com [this message] 2015-07-09 12:12 ` [Bug target/66822] Turn off X86_TUNE_ZERO_EXTEND_WITH_AND for -miamcu julia.koval at intel dot com 2015-07-09 18:09 ` hjl.tools at gmail dot com 2015-07-09 20:32 ` ubizjak at gmail dot com 2015-07-10 1:42 ` [Bug target/66822] Turn -mtune=iamcu for size hjl.tools at gmail dot com 2015-07-10 1:46 ` hjl.tools at gmail dot com 2015-07-10 1:59 ` hjl.tools at gmail dot com 2015-07-10 9:16 ` 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-66822-4@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).