public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103465] [12 regression] -freorder-blocks-and-partition broken on 64-bit Windows Date: Thu, 06 Jan 2022 17:17:32 +0000 [thread overview] Message-ID: <bug-103465-4-vSaKb1bSFn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103465-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103465 --- Comment #25 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > That's something I'm complete fine with ;) Time for a promotion of UI_SEH :-) diff --git a/gcc/coretypes.h b/gcc/coretypes.h index 5d0fc1d915d..f6206154e1a 100644 --- a/gcc/coretypes.h +++ b/gcc/coretypes.h @@ -228,15 +228,17 @@ enum stack_protector { SPCT_FLAG_EXPLICIT = 4 }; -/* Types of unwind/exception handling info that can be generated. */ +/* Types of unwind/exception handling info that can be generated. + Note that a UI_TARGET (or larger) setting is considered to be + incompatible with -freorder-blocks-and-partition. */ enum unwind_info_type { UI_NONE, UI_SJLJ, UI_DWARF2, - UI_TARGET, UI_SEH + UI_TARGET, }; /* Callgraph node profile representation. */ should do the job. Tomas, can you give it a try?
next prev parent reply other threads:[~2022-01-06 17:17 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-29 10:00 [Bug rtl-optimization/103465] New: Invalid note with -fno-reorder-blocks-and-partition tomas.kalibera at gmail dot com 2021-11-29 10:12 ` [Bug rtl-optimization/103465] " marxin at gcc dot gnu.org 2021-11-29 10:17 ` tomas.kalibera at gmail dot com 2021-11-29 10:18 ` marxin at gcc dot gnu.org 2021-11-29 13:23 ` marxin at gcc dot gnu.org 2021-11-29 15:25 ` tomas.kalibera at gmail dot com 2021-12-09 13:39 ` marxin at gcc dot gnu.org 2021-12-09 13:40 ` marxin at gcc dot gnu.org 2021-12-09 14:37 ` tomas.kalibera at gmail dot com 2021-12-09 14:41 ` tomas.kalibera at gmail dot com 2021-12-09 14:44 ` tomas.kalibera at gmail dot com 2021-12-09 15:24 ` tomas.kalibera at gmail dot com 2021-12-09 15:28 ` marxin at gcc dot gnu.org 2021-12-09 15:44 ` marxin at gcc dot gnu.org 2021-12-09 15:53 ` tomas.kalibera at gmail dot com 2021-12-09 15:55 ` tomas.kalibera at gmail dot com 2021-12-09 19:29 ` marxin at gcc dot gnu.org 2021-12-28 10:05 ` [Bug driver/103465] " cvs-commit at gcc dot gnu.org 2021-12-28 10:06 ` marxin at gcc dot gnu.org 2022-01-06 7:32 ` [Bug driver/103465] [12 regression] -freorder-blocks-and-partition broken on 64-bit Windows ebotcazou at gcc dot gnu.org 2022-01-06 9:51 ` marxin at gcc dot gnu.org 2022-01-06 11:42 ` ebotcazou at gcc dot gnu.org 2022-01-06 12:47 ` marxin at gcc dot gnu.org 2022-01-06 13:45 ` ebotcazou at gcc dot gnu.org 2022-01-06 13:50 ` marxin at gcc dot gnu.org 2022-01-06 14:07 ` tomas.kalibera at gmail dot com 2022-01-06 17:17 ` ebotcazou at gcc dot gnu.org [this message] 2022-01-06 22:18 ` [Bug target/103465] " tomas.kalibera at gmail dot com 2022-01-07 9:50 ` tomas.kalibera at gmail dot com 2022-01-07 17:33 ` tomas.kalibera at gmail dot com 2022-01-10 11:44 ` cvs-commit at gcc dot gnu.org 2022-01-10 16:06 ` cvs-commit at gcc dot gnu.org 2022-01-10 16:06 ` cvs-commit at gcc dot gnu.org 2022-01-10 16:07 ` cvs-commit at gcc dot gnu.org 2022-01-10 16:09 ` ebotcazou 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-103465-4-vSaKb1bSFn@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).