public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104781] [12 regression] SEGV in _Unwind_GetGR during i386 Ada bootstrap
Date: Wed, 09 Mar 2022 14:27:30 +0000 [thread overview]
Message-ID: <bug-104781-4-9tEDxkegSt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104781-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104781
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:caa6c33c5d5223c50657b08e73177e8d54ceee51
commit r12-7565-gcaa6c33c5d5223c50657b08e73177e8d54ceee51
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Mar 9 15:25:30 2022 +0100
x86: Define LIBGCC2_UNWIND_ATTRIBUTE on ia32 [PR104781]
On Mon, Mar 07, 2022 at 07:06:28AM -0800, H.J. Lu wrote:
> Since eh_return doesn't work with stack realignment, disable SSE on
> unwind-c.c and unwind-dw2.c to avoid stack realignment with the 4-byte
> incoming stack to avoid SSE usage which is caused by
The following change does that using LIBGCC2_UNWIND_ATTRIBUTE macro
instead,
for ia32 only by forcing -mgeneral-regs-only on routines that call
__builtin_eh_return in libgcc.
2022-03-09 Jakub Jelinek <jakub@redhat.com>
PR target/104781
* config/i386/i386.h (LIBGCC2_UNWIND_ATTRIBUTE): Define for ia32.
next prev parent reply other threads:[~2022-03-09 14:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 12:31 [Bug target/104781] New: " ro at gcc dot gnu.org
2022-03-04 12:32 ` [Bug target/104781] " ro at gcc dot gnu.org
2022-03-04 13:23 ` ro at gcc dot gnu.org
2022-03-04 14:00 ` hjl.tools at gmail dot com
2022-03-04 15:00 ` ubizjak at gmail dot com
2022-03-04 15:04 ` hjl.tools at gmail dot com
2022-03-04 20:29 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-03-05 2:59 ` hjl.tools at gmail dot com
2022-03-05 13:43 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-03-07 8:22 ` rguenth at gcc dot gnu.org
2022-03-08 17:56 ` cvs-commit at gcc dot gnu.org
2022-03-09 14:27 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-09 14:44 ` jakub at gcc dot gnu.org
2022-03-09 14:45 ` jakub at gcc dot gnu.org
2022-03-10 9:36 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-03-10 9:42 ` jakub at gcc dot gnu.org
2022-03-15 10:13 ` drepper.fsp+rhbz at gmail dot com
2022-03-15 10:17 ` jakub at gcc dot gnu.org
2022-03-22 16:34 ` hjl.tools 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-104781-4-9tEDxkegSt@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).