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/65871] bzhi builtin/intrinsic wrongly assumes bzhi instruction doesn't set the ZF flag Date: Tue, 28 Apr 2015 13:06:00 -0000 [thread overview] Message-ID: <bug-65871-4-5Q8FLB8Iwb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65871-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65871 Uroš Bizjak <ubizjak at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-04-28 Ever confirmed|0 |1 --- Comment #3 from Uroš Bizjak <ubizjak at gmail dot com> --- (In reply to James Almer from comment #1) > The same apparently happens with bextr, blsi, blsr, and most (if not all) of > AMD's tbm instructions. They set the ZF flag but gcc still generates a test > instruction. Please see the patch, attached in Comment #2. While I can see the use (and benefit) to model the patterns that also set CC register internally for BEXTR and BZHI instructions, I don't think other listed instructions have clear usage scenarios to warrant additional patterns. Can you perhaps show the benefit to have more insns modelled this way? >From gcc-bugs-return-484843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Apr 28 13:06:27 2015 Return-Path: <gcc-bugs-return-484843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 116160 invoked by alias); 28 Apr 2015 13:06:27 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 116109 invoked by uid 48); 28 Apr 2015 13:06:23 -0000 From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/61645] forward_list::splice_after shall not throw exceptions Date: Tue, 28 Apr 2015 13:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 6.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: <bug-61645-4-xtcBw3qDc9@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-61645-4@http.gcc.gnu.org/bugzilla/> References: <bug-61645-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-04/txt/msg02395.txt.bz2 Content-length: 422 https://gcc.gnu.org/bugzilla/show_bug.cgi?ida645 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> --- done
next prev parent reply other threads:[~2015-04-28 13:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-65871-4@http.gcc.gnu.org/bugzilla/> 2015-04-28 12:58 ` ubizjak at gmail dot com 2015-04-28 13:06 ` ubizjak at gmail dot com [this message] 2015-04-28 16:29 ` jamrial at gmail dot com 2015-04-29 18:53 ` uros at gcc dot gnu.org 2015-04-29 20:59 ` uros at gcc dot gnu.org 2015-05-04 3:03 ` jamrial at gmail dot com 2015-05-05 4:36 ` uros at gcc dot gnu.org 2015-06-18 23:20 ` jamrial at gmail dot com 2015-06-21 9:57 ` ubizjak at gmail dot com 2015-06-22 13:55 ` uros 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-65871-4-5Q8FLB8Iwb@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).