public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/101995] [9/10/11/12 Regression] regression built-in memset missed-optimization arm -Os since r9-3594 Date: Thu, 09 Dec 2021 08:18:35 +0000 [thread overview] Message-ID: <bug-101995-4-5z6iTgBcRs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101995-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101995 --- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> --- >I don't see any problem with aarch64 fwiw. I have to try it on aarch64 but it failed there at one point. (In reply to Segher Boessenkool from comment #8) > Also, what is fragile here? This is *removing* fragility and premature > choices! (In reply to Segher Boessenkool from comment #9) > (In reply to Segher Boessenkool from comment #7) > > What is this REG_RETURNED thing? > > Ah, something added in ira-lives.c, and you call *that* code fragile? > I agree :-) You got to what I thought was fragile in the end. And yes the whole REG_RETURNED mechanism seems very fragile (not the change r9-3594 ). I could not figure out how it was being known to be set on which function call even.
next prev parent reply other threads:[~2021-12-09 8:18 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-20 9:35 [Bug c/101995] New: regression built-in memset missed-optimization arm -Os dumoulin.thibaut at gmail dot com 2021-08-20 12:21 ` [Bug middle-end/101995] " rguenth at gcc dot gnu.org 2021-08-20 21:45 ` [Bug rtl-optimization/101995] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org 2021-08-21 2:53 ` pinskia at gcc dot gnu.org 2021-08-21 3:17 ` pinskia at gcc dot gnu.org 2021-08-21 3:26 ` pinskia at gcc dot gnu.org 2021-08-23 9:10 ` rguenth at gcc dot gnu.org 2021-12-08 14:10 ` [Bug rtl-optimization/101995] [9/10/11/12 Regression] regression built-in memset missed-optimization arm -Os since r9-3594 marxin at gcc dot gnu.org 2021-12-08 20:42 ` segher at gcc dot gnu.org 2021-12-08 20:44 ` segher at gcc dot gnu.org 2021-12-08 20:50 ` segher at gcc dot gnu.org 2021-12-09 8:18 ` pinskia at gcc dot gnu.org [this message] 2021-12-09 21:08 ` segher at gcc dot gnu.org 2022-01-20 10:46 ` rguenth at gcc dot gnu.org 2022-05-27 9:46 ` [Bug rtl-optimization/101995] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:46 ` jakub at gcc dot gnu.org 2023-07-07 10:40 ` [Bug rtl-optimization/101995] [11/12/13/14 " rguenth 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-101995-4-5z6iTgBcRs@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).