public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0'
Date: Tue, 18 Jul 2023 21:42:26 +0000	[thread overview]
Message-ID: <bug-110726-4-kYzjsl8jHl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110726-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Sergei Trofimovich from comment #7)
> Silly question: I would expect -O0 not to perform any simplifications like
> that.  Does `gcc` have a knob to disable `match.pd` templates? Or some of
> them are crucial for correctness?

Some are crucial for correctness usually dealing with c++. you could always use
dbg_cnt to try to narrow down which one is failing.


See 
https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/dbgcnt.def;h=9e2f1d857b49c6c331cc7d1c419eafa0f2403e96;hb=HEAD

For on how to use dbg_cnt

match is the counter here.

Also for generic folding -fdump-tree-original-folding will have the debug info
on what match pattern was applied during "fold" (of generic).

  parent reply	other threads:[~2023-07-18 21:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 19:09 [Bug middle-end/110726] New: " slyfox at gcc dot gnu.org
2023-07-18 19:29 ` [Bug middle-end/110726] " pinskia at gcc dot gnu.org
2023-07-18 19:29 ` pinskia at gcc dot gnu.org
2023-07-18 19:32 ` pinskia at gcc dot gnu.org
2023-07-18 19:36 ` pinskia at gcc dot gnu.org
2023-07-18 19:36 ` pinskia at gcc dot gnu.org
2023-07-18 19:39 ` pinskia at gcc dot gnu.org
2023-07-18 20:04 ` pinskia at gcc dot gnu.org
2023-07-18 20:31 ` pinskia at gcc dot gnu.org
2023-07-18 21:37 ` slyfox at gcc dot gnu.org
2023-07-18 21:42 ` pinskia at gcc dot gnu.org [this message]
2023-07-19  2:02 ` pinskia at gcc dot gnu.org
2023-07-19  6:13 ` slyfox at gcc dot gnu.org
2023-07-19 16:16 ` cvs-commit at gcc dot gnu.org
2023-07-19 16:17 ` 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-110726-4-kYzjsl8jHl@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: link
Be 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).