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/101023] [11/12 Regression] wrong code with -mstackrealign
Date: Thu, 15 Jul 2021 12:43:05 +0000 [thread overview]
Message-ID: <bug-101023-4-dW1jjDpQN1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101023-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101023
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:
https://gcc.gnu.org/g:ba3b30cf70990f4aadb393b64b76ff490bb0bd0f
commit r11-8755-gba3b30cf70990f4aadb393b64b76ff490bb0bd0f
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Fri Jun 11 07:31:29 2021 -0700
x86: Replace ix86_red_zone_size with ix86_red_zone_used
Add red_zone_used to machine_function to track if red zone is used.
When expanding function prologue, set red_zone_used to true if red
zone is used.
gcc/
PR target/101023
* config/i386/i386.c (ix86_expand_prologue): Set red_zone_used
to true if red zone is used.
(ix86_output_indirect_jmp): Replace ix86_red_zone_size with
ix86_red_zone_used.
* config/i386/i386.h (machine_function): Add red_zone_used.
(ix86_red_zone_size): Removed.
(ix86_red_zone_used): New.
* config/i386/i386.md (peephole2 patterns): Replace
ix86_red_zone_size with ix86_red_zone_used.
gcc/testsuite/
PR target/101023
* g++.target/i386/pr101023a.C: New test.
* g++.target/i386/pr101023b.C: Likewise.
(cherry picked from commit 3f04e3782536ad2f9cfbb8cfe6630e9f9dd8af4c)
next prev parent reply other threads:[~2021-07-15 12:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 21:13 [Bug target/101023] New: " zsojka at seznam dot cz
2021-06-11 8:03 ` [Bug target/101023] " rguenth at gcc dot gnu.org
2021-06-11 8:19 ` ubizjak at gmail dot com
2021-06-11 12:25 ` hjl.tools at gmail dot com
2021-06-11 12:56 ` jakub at gcc dot gnu.org
2021-06-11 12:56 ` jakub at gcc dot gnu.org
2021-06-11 13:09 ` zsojka at seznam dot cz
2021-06-11 14:37 ` hjl.tools at gmail dot com
2021-06-11 20:49 ` hjl.tools at gmail dot com
2021-06-13 12:16 ` cvs-commit at gcc dot gnu.org
2021-06-13 13:16 ` hjl.tools at gmail dot com
2021-07-15 12:43 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-15 12:43 ` 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-101023-4-dW1jjDpQN1@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).