From: Richard Guenther <richard.guenther@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][last/n] LTO type merging cleanup
Date: Mon, 23 May 2011 16:19:00 -0000 [thread overview]
Message-ID: <BANLkTineN4WupDkUMTrfUG0DuYag6KtU9w@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimffbjNRAEc7vOjGxVjb7b0ZCjyzw@mail.gmail.com>
On Mon, May 23, 2011 at 5:34 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Mon, May 23, 2011 at 8:18 AM, Richard Guenther <rguenther@suse.de> wrote:
>>
>> This is the last (planned) bit for the regular type merging machinery
>> (there is still some issues with TYPE_CANONICAL that I will try to
>> address next). It avoids merging types which have different names
>> as that leads to interesting debuginfo issues.
>>
>> LTO-bootstrapped and tested on x86_64-unknown-linux-gnu, SPEC 2k6
>> non--g built (w/o any but the TYPE_CANONICAL issues), SPEC 2k6 -g
>> build running.
>>
>> Richard.
>>
>> 2011-05-23 Richard Guenther <rguenther@suse.de>
>>
>> * gimple.c (gimple_types_compatible_p_1): Always compare type names.
>> (iterative_hash_gimple_type): Always hash type names.
>>
>
> Will it fix
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49078
That's very unlikely as it is a TYPE_CANONICAL issue.
Richard.
prev parent reply other threads:[~2011-05-23 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 15:54 Richard Guenther
2011-05-23 16:16 ` H.J. Lu
2011-05-23 16:19 ` Richard Guenther [this message]
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=BANLkTineN4WupDkUMTrfUG0DuYag6KtU9w@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.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).