public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/54796] [4.8 Regression] Non-addressable stack parameter debug quality regression
Date: Mon, 08 Oct 2012 14:38:00 -0000	[thread overview]
Message-ID: <bug-54796-4-8mzgxwdjap@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54796-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54796

--- Comment #4 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2012-10-08 14:37:53 UTC ---
I'm a bit uncomfortable with this approach.  On the one hand, it's quite
simple, which is nice, but if all we get from it is the base term, we'll still
have trouble given multiple sp-based non-overlapping memory regions, won't we? 
The patch in revision 188871 and others in that batch were meant to let alias
analysis within vta figure out the relationship between argp, fp and sp and
disambiguate accesses.  I wonder why it didn't work in this case, with or
without the still-pending patch to canonicalize stack pointer tracking.  I'd
rather go with the latter (even if with additional changes) because it would
enable alias analysis, through more precise sp+offset tracking, to distinguish
not only between argp and sp-based variables, but also between automatic
varying-sized objects.  Assuming my understanding of your patch is correct in
that it adds information on whether some object is at an sp-relative offset but
without making the offset available to alias analysis.  Is that so?


  parent reply	other threads:[~2012-10-08 14:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 15:30 [Bug debug/54796] New: " jakub at gcc dot gnu.org
2012-10-03 16:40 ` [Bug debug/54796] " jakub at gcc dot gnu.org
2012-10-03 17:36 ` jakub at gcc dot gnu.org
2012-10-04 14:09 ` jakub at gcc dot gnu.org
2012-10-08 14:38 ` aoliva at gcc dot gnu.org [this message]
2012-10-16 11:21 ` jakub at gcc dot gnu.org
2012-10-23 15:14 ` jakub 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-54796-4-8mzgxwdjap@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: link
Be 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).