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: Host/Target confusion in Dwarf output

From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
To: ebotcazou at libertysurf dot fr
Cc: eager at eagercon dot com, gcc at gcc dot gnu dot org, iant at google dot com
Date: Thu, 12 Jul 2007 17:23:38 EDT
Subject: Re: Host/Target confusion in Dwarf output
References: <4696557A.7060700@eagercon.com> <200707122258.40957.ebotcazou@libertysurf.fr> <10707122108.AA26741@vlsi1.ultra.nyu.edu> <200707122313.05728.ebotcazou@libertysurf.fr>

> > They don't REQUIRE it, but just miss a lot of optimization if that isn't
> > the case (since things that would otherwise be CONST_INT will now be
> > CONST_DOUBLE and folding will be harder).
> 
> #  need_64bit_hwint	Set to yes if HOST_WIDE_INT must be 64 bits wide
> #			for this target.  This is true iff this target
> #			supports "long" or "wchar_t" wider than 32 bits.

Sorry: I guess my information is dated.  What changed so that it's now
required?

Follow-Ups:
- Re: Host/Target confusion in Dwarf output
  - From: Eric Botcazou

References:
- Host/Target confusion in Dwarf output
  - From: Michael Eager
- Re: Host/Target confusion in Dwarf output
  - From: Eric Botcazou
- Re: Host/Target confusion in Dwarf output
  - From: Richard Kenner
- Re: Host/Target confusion in Dwarf output
  - From: Eric Botcazou

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