public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/101736] Option -fno-reorder-functions breaks exceptions Date: Tue, 03 Aug 2021 07:48:10 +0000 [thread overview] Message-ID: <bug-101736-4-94zqTIBodI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101736-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101736 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hubicka at gcc dot gnu.org --- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> --- We do if (opts->x_flag_reorder_blocks_and_partition) SET_OPTION_IF_UNSET (opts, opts_set, flag_reorder_functions, 1); I guess that needs to be adjusted to disable -freorder-blocks-and-partition when -freorder-functions is explicitely unset. section * default_function_section (tree decl, enum node_frequency freq, bool startup, bool exit) { ... if (!flag_reorder_functions || !targetm_common.have_named_sections) return NULL; might be the actual issue though (the only user of the flag I can find)
prev parent reply other threads:[~2021-08-03 7:48 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-02 21:20 [Bug c++/101736] New: Option -fno-reorder-functions breaks exceptions in gcc 8.2.1 rsundahl at icloud dot com 2021-08-02 21:21 ` [Bug c++/101736] " rsundahl at icloud dot com 2021-08-02 21:57 ` pinskia at gcc dot gnu.org 2021-08-02 22:19 ` [Bug rtl-optimization/101736] " pinskia at gcc dot gnu.org 2021-08-02 22:42 ` pinskia at gcc dot gnu.org 2021-08-03 3:33 ` [Bug rtl-optimization/101736] Option -fno-reorder-functions breaks exceptions rsundahl at icloud dot com 2021-08-03 7:48 ` rguenth at gcc dot gnu.org [this message]
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-101736-4-94zqTIBodI@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: linkBe 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).