From: "Richard Guenther" <richard.guenther@gmail.com>
To: gcc-patches@gcc.gnu.org, zadeck@naturalbridge.com
Subject: Re: [lto] set alias info, poorly
Date: Fri, 07 Dec 2007 10:47:00 -0000 [thread overview]
Message-ID: <84fc9c000712070247g6ac73f01m94e71acfdac039c1@mail.gmail.com> (raw)
In-Reply-To: <20071206222919.GS14706@codesourcery.com>
On Dec 6, 2007 11:29 PM, Nathan Froyd <froydnj@codesourcery.com> wrote:
> First, the good news about this patch: it fixes a few failing testcases.
>
> The bad news is that it does it with a very heavy hammer. We say that
> every type can alias every other type. Obviously this wreaks havoc with
> all the clever alias analysis that has gone into GCC over the years.
>
> There are better, cleverer, more involved ways that you could fix this.
> But this demonstrably works right now. Ideas on what to do in the
> future welcome.
I believe we have to write out the alias sets and the conflict map and at the
point we combine types of different translation units we have to merge the
alias sets and conflict maps properly.
Or not rely on TBAA for LTO, which is what your patch does (so I guess for
completeness you should disable strict aliasing as well).
Richard.
next prev parent reply other threads:[~2007-12-07 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 22:29 Nathan Froyd
2007-12-07 10:47 ` Richard Guenther [this message]
2007-12-07 10:59 ` Jakub Jelinek
2007-12-10 13:55 ` Kenneth Zadeck
2007-12-10 19:55 ` Toon Moene
2007-12-10 20:02 ` Kenneth Zadeck
2007-12-10 20:09 ` Richard Guenther
2007-12-10 20:49 ` Kenneth Zadeck
2007-12-10 21:00 ` Richard Guenther
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=84fc9c000712070247g6ac73f01m94e71acfdac039c1@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=zadeck@naturalbridge.com \
/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).