public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug tree-optimization/95922] New: Failure to optimize `((b ^ a) & c) ^ a` to `(a & ~c) | (b & c)` the right way on architectures with andnot
@ 2020-06-26 23:17 gabravier at gmail dot com
  2020-06-29  9:42 ` [Bug middle-end/95922] " rguenth at gcc dot gnu.org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: gabravier at gmail dot com @ 2020-06-26 23:17 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95922

            Bug ID: 95922
           Summary: Failure to optimize `((b ^ a) & c) ^ a` to `(a & ~c) |
                    (b & c)` the right way on architectures with andnot
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gabravier at gmail dot com
  Target Milestone: ---

int f(int a, int b, int c)
{
    return ((b ^ a) & c) ^ a;
}

This can be optimized to `return (a & ~c) | (b & c);` on processors that have
andnot instructions (at least according to LLVM, which does this transformation
on x86 with -mbmi).

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2021-12-27  5:53 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-26 23:17 [Bug tree-optimization/95922] New: Failure to optimize `((b ^ a) & c) ^ a` to `(a & ~c) | (b & c)` the right way on architectures with andnot gabravier at gmail dot com
2020-06-29  9:42 ` [Bug middle-end/95922] " rguenth at gcc dot gnu.org
2020-11-20 11:06 ` jakub at gcc dot gnu.org
2020-11-20 15:04 ` gabravier at gmail dot com
2021-04-26  1:51 ` pinskia at gcc dot gnu.org
2021-12-27  5:53 ` pinskia at gcc dot gnu.org

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).