public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tomas.kalibera at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103274] [10/11/12 regression] remaining -freorder-blocks-and-partition/ glitch with Windows SEH Date: Wed, 01 Dec 2021 22:59:38 +0000 [thread overview] Message-ID: <bug-103274-4-jQvOr6cqGf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103274-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103274 --- Comment #12 from Tomas Kalibera <tomas.kalibera at gmail dot com> --- I've tested with GCC 10.3 with R. R can be built and passes its tests (without the patch, it crashes). Also, I've checked the generated assembly with an awk script looking for a call instruction immediately followed by .seh_endproc. I didn't find any (while there were many without the patch, based on one the attached example was created). Thanks for the fix.
prev parent reply other threads:[~2021-12-01 22:59 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-16 13:12 [Bug target/103274] New: Remaining " tomas.kalibera at gmail dot com 2021-11-16 14:55 ` [Bug target/103274] " ebotcazou at gcc dot gnu.org 2021-11-16 15:27 ` tomas.kalibera at gmail dot com 2021-11-16 16:02 ` martin at martin dot st 2021-11-16 16:07 ` martin at martin dot st 2021-11-16 17:11 ` [Bug target/103274] [10/11/12 regression] remaining " ebotcazou at gcc dot gnu.org 2021-11-16 17:34 ` ebotcazou at gcc dot gnu.org 2021-11-30 9:19 ` cvs-commit at gcc dot gnu.org 2021-11-30 9:21 ` cvs-commit at gcc dot gnu.org 2021-11-30 9:23 ` cvs-commit at gcc dot gnu.org 2021-11-30 9:24 ` ebotcazou at gcc dot gnu.org 2021-12-01 7:46 ` martin at martin dot st 2021-12-01 22:59 ` tomas.kalibera at gmail dot com [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-103274-4-jQvOr6cqGf@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).