From: Jakub Jelinek <jakub@redhat.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: fix for PR49888 var-tracking compile-time regression
Date: Wed, 16 Jan 2013 16:55:00 -0000 [thread overview]
Message-ID: <20130116165449.GK7269@tucnak.redhat.com> (raw)
In-Reply-To: <or1udl5kf9.fsf@livre.localdomain>
On Wed, Jan 16, 2013 at 11:25:46AM -0200, Alexandre Oliva wrote:
> > Also, what effects (if any) does the patch have on the
> > .debug_info/.debug_loc size and coverage?
>
> It shouldn't have any, since it's just caching results that would have
> been recomputed over and over. However, there's a possibility of being
> âluckyâ and recording an equivalence in the cache whose path would later
> be removed from a dynamic set (say, if an incoming VALUE is reset and
> re-bound within a block; I'm not sure this ever actually happens). In
> this case, these retained equivalences might enable alias analysis to
> figure out that two memory refs do not overlap, and so one can be
> retained in a dynamic equivalence list when we process a MOp that
> modifies the other. Or something ;-) It shouldn't really make any
> difference, just speed things up a bit. Paraphrasing Knuth, âI proved
> it, but I didn't test itâ ;-)
Ok, seems it is almost no change, but if I do between
--enable-languages=all,obj-c++,ada,lto,go --enable-checking=yes,rtl
x86_64-linux and i686-linux (the latter without ,ada) trees (once without
your var-tracking.c patch, once with) readelf -WS comparison of all the
gcc/*.o gcc/*/*.o files from stage3, I get differences beyond
var-tracking.o (which is of course expected):
for i686-linux tree-ssa-pre.o is different, and
for x86_64-linux go/export.o is different.
All other objects have the same readelf -WS output (not comparing .debug_*
section data, as that could be slightly different as I haven't done the
build with exactly the same object directory (different dirname, but same
length thereof)). If I strip those two object files, then they are
identical between the two trees. There are some differences in .debug_loc
in both cases.
Jakub
next prev parent reply other threads:[~2013-01-16 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 10:29 Alexandre Oliva
2013-01-16 10:58 ` Jakub Jelinek
2013-01-16 13:25 ` Alexandre Oliva
2013-01-16 14:15 ` Jakub Jelinek
2013-01-16 16:55 ` Jakub Jelinek [this message]
2013-01-17 20:57 ` Alexandre Oliva
2013-01-18 10:59 ` Jakub Jelinek
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=20130116165449.GK7269@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=aoliva@redhat.com \
--cc=gcc-patches@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).