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/103274] Remaining -freorder-blocks-and-partition/ glitch with Windows SEH
Date: Tue, 16 Nov 2021 14:55:14 +0000 [thread overview]
Message-ID: <bug-103274-4-oOFuQW0wvt@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
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2021-11-16
Status|UNCONFIRMED |WAITING
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> -freorder-blocks-and-partition sometimes causes a function to end right in a
> (non-returning) call, but SEH needs at least one more instruction on x86_64.
> Seen in GCC 10.3, 11.2 and git master. Maybe [1] did not cover all the cases?
SEH means "Structured Exception Handling" but there is no exception handling in
this chunk of program since it's written in C and compiled without
-fexceptions, so I'm not quite sure what you're expecting here.
next prev parent reply other threads:[~2021-11-16 14:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 13:12 [Bug target/103274] New: " tomas.kalibera at gmail dot com
2021-11-16 14:55 ` ebotcazou at gcc dot gnu.org [this message]
2021-11-16 15:27 ` [Bug target/103274] " 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
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-oOFuQW0wvt@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).