From: Diego Novillo <dnovillo@google.com>
To: Richard Guenther <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][LTO] Kill forced type merging code
Date: Fri, 16 Oct 2009 21:13:00 -0000 [thread overview]
Message-ID: <b798aad50910161411q724f32ebn739dedca2afd1b81@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0910162255020.4520@zhemvz.fhfr.qr>
On Fri, Oct 16, 2009 at 16:58, Richard Guenther <rguenther@suse.de> wrote:
> 2009-10-16 Richard Guenther <rguenther@suse.de>
>
> * lto-symtab.c (merge_incomplete_and_complete_type): Remove.
> (maybe_merge_incomplete_and_complete_type): Likewise.
> (lto_symtab_merge): Do not call them. Do not warn for
> complete vs. incomplete compatible types.
> (lto_symtab_merge_decls_2): Simplify.
> * gimple.c (gimple_force_type_merge): Remove.
> (gimple_types_compatible_p): Make it static.
> * gimple.h (gimple_force_type_merge): Remove.
> (gimple_types_compatible_p): Likewise.
Whee! OK.
Diego.
prev parent reply other threads:[~2009-10-16 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 21:12 Richard Guenther
2009-10-16 21:13 ` Diego Novillo [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=b798aad50910161411q724f32ebn739dedca2afd1b81@mail.gmail.com \
--to=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).