This is the mail archive of the gcc-patches@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: [PATCH][LTO] [1/3] Fix bootstrap with -flto

From: Diego Novillo <dnovillo at google dot com>
To: Richard Guenther <rguenther at suse dot de>
Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>
Date: Wed, 19 Aug 2009 09:41:15 -0400
Subject: Re: [PATCH][LTO] [1/3] Fix bootstrap with -flto
References: <alpine.LNX.2.00.0908191043280.16347@zhemvz.fhfr.qr> <b798aad50908190515y15018bd7ja2167aff28c07925@mail.gmail.com> <alpine.LNX.2.00.0908191417390.16347@zhemvz.fhfr.qr> <alpine.LNX.2.00.0908191511330.16347@zhemvz.fhfr.qr> <b798aad50908190636s174a87d7ybb9a0ad1819cc2f7@mail.gmail.com> <alpine.LNX.2.00.0908191538110.16347@zhemvz.fhfr.qr>

On Wed, Aug 19, 2009 at 09:39, Richard Guenther<rguenther@suse.de> wrote:

> That's what the patch implements. ÂIt is irrelevant what
> flag_signed_char is for lto1, it will be just the signedness of
> for example va_arg_list_node which is char *. ÂSo I could as well
> hard-code it to always be unsigned or signed here.

In which case, I would rather hard code it.  Otherwise, it seems as if
flag_signed_char would affect lto1.

Diego.

Follow-Ups:
- Re: [PATCH][LTO] [1/3] Fix bootstrap with -flto
  - From: Richard Guenther

References:
- [PATCH][LTO] [1/3] Fix bootstrap with -flto
  - From: Richard Guenther
- Re: [PATCH][LTO] [1/3] Fix bootstrap with -flto
  - From: Diego Novillo
- Re: [PATCH][LTO] [1/3] Fix bootstrap with -flto
  - From: Richard Guenther
- Re: [PATCH][LTO] [1/3] Fix bootstrap with -flto
  - From: Richard Guenther
- Re: [PATCH][LTO] [1/3] Fix bootstrap with -flto
  - From: Diego Novillo
- Re: [PATCH][LTO] [1/3] Fix bootstrap with -flto
  - From: Richard Guenther

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