public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/57224] New: Remove __builtin_ia32_cmpngtss and __builtin_ia32_cmpngess Date: Thu, 09 May 2013 09:23:00 -0000 [thread overview] Message-ID: <bug-57224-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57224 Bug #: 57224 Summary: Remove __builtin_ia32_cmpngtss and __builtin_ia32_cmpngess Classification: Unclassified Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: minor Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: glisse@gcc.gnu.org Target: x86_64-linux-gnu Hello, the builtins __builtin_ia32_cmpngtss and __builtin_ia32_cmpngess are unused (_mm_cmpngt_ss uses __builtin_ia32_cmpnltss instead), undocumented, and produce confusing results (they swap operands, so the high elements of the vector are taken from the second operand instead of the first one like all other cmp*ss). I think it would be best to remove them.
next reply other threads:[~2013-05-09 9:23 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-09 9:23 glisse at gcc dot gnu.org [this message] 2013-06-27 20:10 ` [Bug target/57224] " glisse 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-57224-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).