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/106568] -freorder-blocks-algorithm appears to causes a crash in stable code, no way to disable it
Date: Mon, 08 Aug 2022 21:34:38 +0000	[thread overview]
Message-ID: <bug-106568-4-EGvKgL9owj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106568-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note I really doubt reorder-blocks would cause any issues unless there is some
other undefined code in there. An example might be even aliasing violations
(where the is no undefined sanitizer yet).

  parent reply	other threads:[~2022-08-08 21:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 21:20 [Bug c++/106568] New: " noloader at gmail dot com
2022-08-08 21:30 ` [Bug middle-end/106568] " ktkachov at gcc dot gnu.org
2022-08-08 21:34 ` pinskia at gcc dot gnu.org [this message]
2022-08-08 21:36 ` [Bug rtl-optimization/106568] " pinskia at gcc dot gnu.org
2022-08-08 21:40 ` pinskia at gcc dot gnu.org
2022-08-08 21:52 ` noloader at gmail dot com
2022-08-08 22:00 ` pinskia at gcc dot gnu.org
2022-08-08 22:18 ` noloader at gmail dot com
2022-08-08 22:25 ` pinskia at gcc dot gnu.org
2022-08-08 23:05 ` noloader at gmail dot com
2022-08-08 23:20 ` noloader at gmail dot com
2022-08-08 23:22 ` pinskia at gcc dot gnu.org
2022-08-08 23:23 ` pinskia at gcc dot gnu.org
2022-08-09  0:56 ` noloader at gmail dot com
2022-08-09  1:09 ` noloader at gmail dot com
2022-08-09  1:35 ` noloader at gmail dot com
2022-08-09  1:45 ` pinskia at gcc dot gnu.org
2022-08-09  1:46 ` pinskia at gcc dot gnu.org
2022-08-09  2:05 ` noloader at gmail dot com
2022-08-09  4:22 ` noloader at gmail dot com
2022-08-09  4:22 ` noloader at gmail dot com
2022-08-09  7:57 ` rguenth at gcc dot gnu.org
2024-02-06 20:20 ` redi at gcc dot gnu.org
2024-02-06 20:28 ` pinskia at gcc dot gnu.org
2024-02-06 21:50 ` pinskia at gcc dot gnu.org
2024-02-06 22:21 ` [Bug ipa/106568] " 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-106568-4-EGvKgL9owj@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).