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/101324] powerpc64le: hashst appears before mflr at -O1 or higher Date: Fri, 03 Dec 2021 20:32:32 +0000 [thread overview] Message-ID: <bug-101324-4-ppWn1sG2ZD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101324-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101324 --- Comment #20 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Peter Bergner <bergner@gcc.gnu.org>: https://gcc.gnu.org/g:cff7879a381d3f5ed6556206896e6a6229800167 commit r12-5781-gcff7879a381d3f5ed6556206896e6a6229800167 Author: Martin Liska <mliska@suse.cz> Date: Fri Dec 3 11:58:25 2021 -0600 rs6000: Fix up flag_shrink_wrap handling in presence of -mrop-protect [PR101324] PR101324 shows a problem in disabling shrink-wrapping when using -mrop-protect when there is a attribute optimize/pragma. The fix envolves moving the handling of flag_shrink_wrap so it gets re-disbled when we change or add options. 2021-12-03 Martin Liska <mliska@suse.cz> gcc/ PR target/101324 * config/rs6000/rs6000.c (rs6000_option_override_internal): Move the disabling of shrink-wrapping when using -mrop-protect from here... (rs6000_override_options_after_change): ...to here. 2021-12-03 Peter Bergner <bergner@linux.ibm.com> gcc/testsuite/ PR target/101324 * gcc.target/powerpc/pr101324.c: New test.
next prev parent reply other threads:[~2021-12-03 20:32 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-05 15:32 [Bug target/101324] New: " tuliom at ascii dot art.br 2021-07-05 22:18 ` [Bug target/101324] " segher at gcc dot gnu.org 2021-07-05 23:54 ` segher at gcc dot gnu.org 2021-07-06 13:28 ` segher at gcc dot gnu.org 2021-07-06 13:46 ` tuliom at ascii dot art.br 2021-07-12 3:41 ` marxin at gcc dot gnu.org 2021-08-12 16:17 ` marxin at gcc dot gnu.org 2021-08-16 11:37 ` marxin at gcc dot gnu.org 2021-10-25 16:54 ` marxin at gcc dot gnu.org 2021-10-25 20:48 ` bergner at gcc dot gnu.org 2021-10-25 20:49 ` bergner at gcc dot gnu.org 2021-10-26 6:02 ` marxin at gcc dot gnu.org 2021-10-26 6:26 ` marxin at gcc dot gnu.org 2021-10-26 11:35 ` bergner at gcc dot gnu.org 2021-10-26 11:42 ` bergner at gcc dot gnu.org 2021-10-26 14:43 ` marxin at gcc dot gnu.org 2021-10-26 15:32 ` bergner at gcc dot gnu.org 2021-10-26 16:55 ` segher at gcc dot gnu.org 2021-10-26 19:08 ` bergner at gcc dot gnu.org 2021-10-27 20:08 ` bergner at gcc dot gnu.org 2021-10-27 20:09 ` bergner at gcc dot gnu.org 2021-10-28 3:19 ` bergner at gcc dot gnu.org 2021-12-03 20:32 ` cvs-commit at gcc dot gnu.org [this message] 2021-12-03 20:43 ` bergner at gcc dot gnu.org 2021-12-03 21:29 ` bergner at gcc dot gnu.org 2021-12-03 22:36 ` bergner at gcc dot gnu.org 2021-12-27 13:50 ` raoni at linux dot ibm.com 2022-02-11 19:28 ` cvs-commit at gcc dot gnu.org 2022-02-11 22:33 ` bergner at gcc dot gnu.org
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-101324-4-ppWn1sG2ZD@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: linkBe 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).