public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/36409] Additional instructions in prologue and epilogue. Date: Mon, 20 Dec 2021 11:18:06 +0000 [thread overview] Message-ID: <bug-36409-4-VeQ8X3h3I6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-36409-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36409 Richard Earnshaw <rearnsha at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2009-04-21 14:42:20 |2021-12-20 --- Comment #3 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- Still a problem even today. The 'optimized' gimple code is: __attribute__((noinline)) void foo (struct Foo f) { int * _1; <bb 2> [local count: 1073741824]: _1 = f.p; *_1 = 0; return; } which then gets expanded to copy the incoming argument to the stack
next parent reply other threads:[~2021-12-20 11:18 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-36409-4@http.gcc.gnu.org/bugzilla/> 2021-12-20 11:18 ` rearnsha at gcc dot gnu.org [this message] 2008-06-01 10:47 [Bug rtl-optimization/36409] New: " ramana at icerasemi dot com 2009-02-04 23:39 ` [Bug target/36409] " ramana dot r at gmail dot com 2009-04-21 14:42 ` ramana at gcc dot gnu dot 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-36409-4-VeQ8X3h3I6@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).