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/94556] FAIL: nptl/tst-thread-exit-clobber
Date: Mon, 20 Apr 2020 13:05:13 +0000 [thread overview]
Message-ID: <bug-94556-4-kAjR0IryfA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94556-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94556
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:
https://gcc.gnu.org/g:47ea8616d4f5fee875e0849e393575e00def5894
commit r9-8517-g47ea8616d4f5fee875e0849e393575e00def5894
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Mon Apr 20 05:51:29 2020 -0700
x86: Restore the frame pointer in word_mode
We must restore the frame pointer in word_mode for eh_return epilogues
since the upper 32 bits of RBP register can have any values.
Tested on Linux/x32 and Linux/x86-64.
Backport from master
PR target/94556
* config/i386/i386.c (ix86_expand_epilogue): Restore the frame
pointer in word_mode for eh_return epilogues.
(cherry picked from commit efc1f3577f38bb213b313661c025ac965baee953)
next prev parent reply other threads:[~2020-04-20 13:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 20:42 [Bug target/94556] New: [10 Regression] " hjl.tools at gmail dot com
2020-04-10 21:39 ` [Bug target/94556] " hjl.tools at gmail dot com
2020-04-10 21:46 ` hjl.tools at gmail dot com
2020-04-10 22:38 ` hjl.tools at gmail dot com
2020-04-10 22:39 ` hjl.tools at gmail dot com
2020-04-12 14:30 ` hjl.tools at gmail dot com
2020-04-12 17:19 ` hjl.tools at gmail dot com
2020-04-13 11:26 ` cvs-commit at gcc dot gnu.org
2020-04-13 19:38 ` [Bug target/94556] " law at redhat dot com
2020-04-14 6:47 ` rguenth at gcc dot gnu.org
2020-04-20 13:05 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-20 13:05 ` cvs-commit at gcc dot gnu.org
2020-04-20 13: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-94556-4-kAjR0IryfA@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).