public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/42782] [4.5 Regression] VTA missed location: parameter via stack Date: Mon, 18 Jan 2010 10:58:00 -0000 [thread overview] Message-ID: <20100118105750.21758.qmail@sourceware.org> (raw) In-Reply-To: <bug-42782-12292@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from jakub at gcc dot gnu dot org 2010-01-18 10:57 ------- The problem is that dataflow_set_preserve_mem_locs and/or dataflow_set_remove_mem_locs removes all MEMs (with the exception of those referring to decl with 0 MEM_OFFSET in the first function) upon encountering a CALL. For parameters (ARG_POINTER_REGNUM based, or even HARD_FRAME_POINTER_REGNUM based ones I believe) we don't need to remove them, as long as the decl isn't addressable and thus the call shouldn't have modified them. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42782
next prev parent reply other threads:[~2010-01-18 10:58 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-17 21:33 [Bug debug/42782] New: " jan dot kratochvil at redhat dot com 2010-01-17 23:23 ` [Bug debug/42782] " jan dot kratochvil at redhat dot com 2010-01-18 10:14 ` [Bug debug/42782] [4.5 Regression] " jakub at gcc dot gnu dot org 2010-01-18 10:58 ` jakub at gcc dot gnu dot org [this message] 2010-01-19 8:44 ` aoliva at gcc dot gnu dot org 2010-01-20 22:57 ` jakub at gcc dot gnu dot org 2010-01-22 17:03 ` jakub 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=20100118105750.21758.qmail@sourceware.org \ --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).