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/57264] cld not emitted when string instructions used, and '-mcld' on command line Date: Mon, 13 May 2013 15:41:00 -0000 [thread overview] Message-ID: <bug-57264-4-mTuWAcPIg8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57264-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57264 Uros Bizjak <ubizjak at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |x86 Status|UNCONFIRMED |NEW Version|unknown |4.7.3 Last reconfirmed| |2013-05-13 Component|c |target CC| |ubizjak at gmail dot com Ever confirmed|0 |1 Target Milestone|--- |4.7.4 --- Comment #1 from Uros Bizjak <ubizjak at gmail dot com> --- The stosl insn is created by the combine pass, not via expander, so flag that triggers the cld insertion is not set. I propose to backport r195381 to disable unwanted insn combination. Can you please test the backport?
next prev parent reply other threads:[~2013-05-13 15:41 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-13 13:32 [Bug c/57264] New: " thutt at vmware dot com 2013-05-13 15:41 ` ubizjak at gmail dot com [this message] 2013-05-13 15:56 ` [Bug target/57264] " ubizjak at gmail dot com 2013-05-13 17:26 ` ubizjak at gmail dot com 2013-05-13 17:28 ` ubizjak at gmail dot com 2013-05-13 17:56 ` thutt at vmware dot com 2013-05-13 18:54 ` ubizjak at gmail dot com 2013-05-14 13:41 ` thutt at vmware dot com 2013-05-14 14:01 ` ubizjak at gmail dot com 2013-05-14 17:07 ` thutt at vmware dot com 2013-05-14 18:00 ` 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-57264-4-mTuWAcPIg8@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).