public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/53652] *andn* isn't used for vectorization Date: Thu, 14 Jun 2012 03:46:00 -0000 [thread overview] Message-ID: <bug-53652-4-gwJWJv1yvC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53652-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53652 Hans-Peter Nilsson <hp at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hp at gcc dot gnu.org --- Comment #1 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2012-06-14 03:45:59 UTC --- I'd humbly suggest adding a "not"-recognizer anon insn-and-split pattern with a clear comment "combine needs this as a stepping stone to combine into the andnot". BTW, this PR seems target-specific; I don't see it for my vector back-end (using 4.7.1:ish, has "and" and "not" and "andnot" V4SI).
next prev parent reply other threads:[~2012-06-14 3:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-13 6:49 [Bug rtl-optimization/53652] New: " jakub at gcc dot gnu.org 2012-06-14 3:46 ` hp at gcc dot gnu.org [this message] 2012-06-14 10:24 ` [Bug rtl-optimization/53652] " jakub at gcc dot gnu.org 2021-12-27 5:47 ` pinskia at gcc dot gnu.org 2021-12-27 5:48 ` pinskia at gcc dot gnu.org 2022-01-11 2:13 ` [Bug rtl-optimization/53652] *andn* does not always get used with simd and loading from memory cvs-commit at gcc dot gnu.org 2022-01-11 2:19 ` crazylht at gmail dot com 2022-01-11 2:25 ` pinskia 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-53652-4-gwJWJv1yvC@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).