public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/105586] [11/12 Regression] -fcompare-debug failure (length) with -O2 -fno-if-conversion -mtune=power4 -fno-guess-branch-probability
Date: Tue, 08 Nov 2022 14:23:42 +0000	[thread overview]
Message-ID: <bug-105586-4-vZ9CLr65H8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105586-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Ah.  It's a nasty bug, so "safe side" is to *do* fix it, in my reading.  But
you
can also say "not doing anything" (so, staying susceptible to the bug) is
safer.
It happens rather infrequently after all.

Just follow up, ask for clarification?

  parent reply	other threads:[~2022-11-08 14:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12 19:08 [Bug debug/105586] New: [11/12/13 " zsojka at seznam dot cz
2022-05-13  7:55 ` [Bug debug/105586] " rguenth at gcc dot gnu.org
2022-05-13  9:31 ` jakub at gcc dot gnu.org
2022-05-13 16:49 ` segher at gcc dot gnu.org
2022-05-16  2:47 ` linkw at gcc dot gnu.org
2022-05-19 12:41 ` jskumari at gcc dot gnu.org
2022-09-07 15:35 ` [Bug rtl-optimization/105586] " cvs-commit at gcc dot gnu.org
2022-10-19 10:08 ` [Bug rtl-optimization/105586] [11/12 " rguenth at gcc dot gnu.org
2022-10-27 16:02 ` bergner at gcc dot gnu.org
2022-10-27 17:58 ` segher at gcc dot gnu.org
2022-10-27 18:01 ` segher at gcc dot gnu.org
2022-11-08 12:56 ` jskumari at gcc dot gnu.org
2022-11-08 14:23 ` segher at gcc dot gnu.org [this message]
2022-11-09  6:36 ` jskumari at gcc dot gnu.org
2022-11-09 16:51 ` jskumari at gcc dot gnu.org
2023-05-05 21:42 ` 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-105586-4-vZ9CLr65H8@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).