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/105960] [12/13 Regression] Crash in 32-bit mode
Date: Tue, 21 Jun 2022 17:45:32 +0000 [thread overview]
Message-ID: <bug-105960-4-shGs3x2Frr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105960-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105960
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:
https://gcc.gnu.org/g:2474c8e09a93027cde39ecb6a53742142c8496ed
commit r12-8501-g2474c8e09a93027cde39ecb6a53742142c8496ed
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Tue Jun 14 08:20:16 2022 -0700
i386: Disallow sibcall for calling ifunc functions with PIC register
Disallow siball when calling ifunc functions with PIC register so that
PIC register can be restored.
gcc/
PR target/105960
* config/i386/i386.cc (ix86_function_ok_for_sibcall): Return
false if PIC register is used when calling ifunc functions.
gcc/testsuite/
PR target/105960
* gcc.target/i386/pr105960.c: New test.
(cherry picked from commit fe9765c0b97e6b4ce2cd226631d329fc05ba2aa5)
next prev parent reply other threads:[~2022-06-21 17:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 19:54 [Bug c/105960] New: " terra at gnome dot org
2022-06-13 20:00 ` [Bug target/105960] " pinskia at gcc dot gnu.org
2022-06-13 20:00 ` pinskia at gcc dot gnu.org
2022-06-13 20:06 ` terra at gnome dot org
2022-06-13 20:08 ` terra at gnome dot org
2022-06-14 8:30 ` rguenth at gcc dot gnu.org
2022-06-14 8:31 ` [Bug target/105960] [12/13 Regression] " rguenth at gcc dot gnu.org
2022-06-14 14:18 ` hjl.tools at gmail dot com
2022-06-14 15:02 ` hjl.tools at gmail dot com
2022-06-14 17:22 ` wwcsmail at gmail dot com
2022-06-20 15:26 ` cvs-commit at gcc dot gnu.org
2022-06-21 17:45 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-15 9:00 ` marxin at gcc dot gnu.org
2022-07-15 18:07 ` 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-105960-4-shGs3x2Frr@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).