public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "noloader at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/106568] -freorder-blocks-algorithm appears to causes a crash in stable code, no way to disable it
Date: Tue, 09 Aug 2022 04:22:58 +0000	[thread overview]
Message-ID: <bug-106568-4-x47C9fDNFH@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 #20 from Jeffrey Walton <noloader at gmail dot com> ---
Hi Andrew.

I went through the list of options that are enabled at -O2 from [1]. I built
the library with each option separately at "-DNDEBUG -g2 -O2 -fno-xxx".

Here is the list of suspects. I seem to recall having trouble with
-fdevirtualize in the past:

  -fno-devirtualize
  -fno-indirect-inlining
  -fno-devirtualize

Here are the full results:

Failed to execute with -fno-align-functions
Failed to execute with -fno-align-jumps
Failed to execute with -fno-align-labels
Failed to execute with -fno-align-loops
Failed to execute with -fno-caller-saves
Failed to execute with -fno-code-hoisting
Failed to execute with -fno-crossjumping
Failed to execute with -fno-cse-follow-jumps
Failed to execute with -fno-cse-skip-blocks
Failed to execute with -fno-delete-null-pointer-checks
Ok! Ok! Ok! Ok! Ok! -fno-devirtualize
Failed to execute with -fno-devirtualize-speculatively
Failed to execute with -fno-expensive-optimizations
Failed to execute with -fno-finite-loops
Failed to execute with -fno-gcse
Failed to execute with -fno-gcse-lm
Failed to execute with -fno-hoist-adjacent-loads
Failed to execute with -fno-inline-functions
Failed to execute with -fno-inline-small-functions
Ok! Ok! Ok! Ok! Ok! -fno-indirect-inlining
Failed to execute with -fno-ipa-bit-cp
Failed to execute with -fno-ipa-cp
Failed to execute with -fno-ipa-icf
Failed to execute with -fno-ipa-ra
Failed to execute with -fno-ipa-sra
Failed to execute with -fno-ipa-vrp
Failed to execute with -fno-isolate-erroneous-paths-dereference
Failed to execute with -fno-lra-remat
Failed to execute with -fno-optimize-sibling-calls
Failed to execute with -fno-optimize-strlen
Failed to execute with -fno-partial-inlining
Failed to execute with -fno-peephole2
Failed to build with -fno-reorder-blocks-algorithm=stc
Failed to execute with -fno-reorder-blocks-and-partition
Failed to execute with -fno-reorder-functions
Failed to execute with -fno-rerun-cse-after-loop
Failed to execute with -fno-schedule-insns
Failed to execute with -fno-schedule-insns2
Failed to execute with -fno-sched-interblock
Failed to execute with -fno-sched-spec
Failed to execute with -fno-store-merging
Ok! Ok! Ok! Ok! Ok! -fno-strict-aliasing
Failed to execute with -fno-thread-jumps
Failed to execute with -fno-tree-builtin-call-dce
Failed to execute with -fno-tree-loop-vectorize
Failed to execute with -fno-tree-pre
Ok! Ok! Ok! Ok! Ok! -fno-tree-slp-vectorize
Failed to execute with -fno-tree-switch-conversion
Failed to execute with -fno-tree-tail-merge
Failed to execute with -fno-tree-vrp
Failed to build with -fno-vect-cost-model=very-cheap

Attached is the script I used to repeatedly build the library.

  parent reply	other threads:[~2022-08-09  4:22 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
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 [this message]
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-x47C9fDNFH@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).