This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: lto gimple types and debug info

From: Chris Lattner <clattner at apple dot com>
To: Kenneth Zadeck <zadeck at naturalbridge dot com>
Cc: GCC Development <gcc at gcc dot gnu dot org>, Diego Novillo <dnovillo at google dot com>, "Hubicha, Jan" <jh at suse dot cz>, Richard Guenther <richard dot guenther at gmail dot com>, "Taylor, Ian Lance" <iant at google dot com>, Ollie Wild <aaw at google dot com>, "Maddox, Bill" <maddox at google dot com>, jason at redhat dot com, Rafael Espindola <espindola at google dot com>
Date: Thu, 24 Jul 2008 10:03:52 -0700
Subject: Re: lto gimple types and debug info
References: <4888AD1F.7080007@naturalbridge.com>

On Jul 24, 2008, at 9:26 AM, Kenneth Zadeck wrote:

3) Generate the debugging for the types late.  The problem here is
 that we want the gimple type system to be stripped of the front end
 specific information, so any front end specific info that is only
 necessary for the debugging, will both bulk up the gimple type
 system and make it less language independent.

I thought the whole idea of the LTO project was to keep as much language specific type information as late as possible. If you start stripping out useful information about types, it becomes harder to do high level optimizations like devirtualization and other source- specific transformations. This is one of the major advantages of LTO, no?

-Chris

Follow-Ups:
- Re: lto gimple types and debug info
  - From: Kenneth Zadeck

References:
- lto gimple types and debug info
  - From: Kenneth Zadeck

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]