public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/46219] Generate indirect jump instruction on x86-64 Date: Fri, 29 Oct 2010 16:46:00 -0000 [thread overview] Message-ID: <20101029164600.E1GPbWN1K2dozGLUsEdh5V_JnreDLMRsFtLfvi4ihGE@z> (raw) In-Reply-To: <bug-46219-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46219 Richard Henderson <rth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rth at gcc dot gnu.org --- Comment #3 from Richard Henderson <rth at gcc dot gnu.org> 2010-10-29 16:45:47 UTC --- That would be because we have no good way to say: global memory is fine, but the on-stack memory that we just deallocated is not. In addition for this case, we have to ensure that the registers used to do the indexing are still valid after call-saved registers have been restored, and avoid any call-clobbered registers that might be needed to execute the epilogue. In general I don't think this is solvable, but for this specific case we could add a peephole.
next prev parent reply other threads:[~2010-10-29 16:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-28 22:52 [Bug rtl-optimization/46219] New: " adam at consulting dot net.nz 2010-10-28 22:58 ` [Bug target/46219] " pinskia at gcc dot gnu.org 2010-10-29 8:17 ` ubizjak at gmail dot com 2010-10-29 16:46 ` rth at gcc dot gnu.org [this message] 2014-06-05 17:04 ` ktietz at gcc dot gnu.org 2014-06-05 17:05 ` ktietz at gcc dot gnu.org 2014-09-05 0:29 ` adam at consulting dot net.nz 2021-11-28 5:48 ` pinskia 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=20101029164600.E1GPbWN1K2dozGLUsEdh5V_JnreDLMRsFtLfvi4ihGE@z \ --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).