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: [ping] [4.5/m32c] libstdc++ build crashes emitting debug_info

From: DJ Delorie <dj at redhat dot com>
To: Richard Guenther <richard dot guenther at gmail dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: Fri, 16 Apr 2010 17:42:20 -0400
Subject: Re: [ping] [4.5/m32c] libstdc++ build crashes emitting debug_info
References: <201004100214.o3A2ETpC031421@greed.delorie.com> <201004162112.o3GLCu0J028648@greed.delorie.com> <s2k84fc9c001004161439i2f00bef4x88639cb90fdf9c2b@mail.gmail.com>

> The sizetype operand should always be sign-extended even if it is
> unsigned.

Really?  How do you do foo[-1] then?

Remember - this is a problem *because* sizetype is smaller than a
pointer, so it matters which way you extend.  You can't rely on
type-wrapping to make large unsigned constants work as negatives.

Follow-Ups:
- Re: [ping] [4.5/m32c] libstdc++ build crashes emitting debug_info
  - From: Richard Guenther

References:
- [4.5/m32c] libstdc++ build crashes emitting debug_info
  - From: DJ Delorie
- [ping] [4.5/m32c] libstdc++ build crashes emitting debug_info
  - From: DJ Delorie
- Re: [ping] [4.5/m32c] libstdc++ build crashes emitting debug_info
  - From: Richard Guenther

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