This is the mail archive of the gcc-help@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: char y = 469;

From: Ian Lance Taylor <iant at google dot com>
To: "Diego Novillo" <dnovillo at google dot com>
Cc: stf_polska <stf_polska at o2 dot pl>, gcc-help at gcc dot gnu dot org
Date: 27 Aug 2007 12:25:14 -0700
Subject: Re: char y = 469;
References: <46D0C782.3020402@o2.pl> <b798aad50708270443q21e54a00gaad4a64153295215@mail.gmail.com> <46D2C2E6.8000907@o2.pl> <b798aad50708270613n6a263cfbj953294b129046a63@mail.gmail.com> <m3ps184yz7.fsf@dhcp-172-18-118-196.corp.google.com> <b798aad50708271147m41066b79m95905ca65eb1f557@mail.gmail.com>

"Diego Novillo" <dnovillo@google.com> writes:

> On 27 Aug 2007 11:24:44 -0700, Ian Lance Taylor <iant@google.com> wrote:
> 
> > This warning is (or, rather, will be) new with gcc 4.3.0, when gcc
> > 4.3.0 is released.
> 
> You mean the functionality, right?  IIRC, -Wconversion used to work in
> function arguments (if x and y were function arguments in this test,
> for instance).

Yes, the functionality--that is, this specific warning, among others.
As you say, -Wconversion in general is not new.

This was due to a Google Summer of Code project last year:
    http://gcc.gnu.org/wiki/Wcoercion

Ian

References:
- char y = 469;
  - From: stf_polska
- Re: char y = 469;
  - From: Diego Novillo
- Re: char y = 469;
  - From: stf_polska
- Re: char y = 469;
  - From: Diego Novillo
- Re: char y = 469;
  - From: Ian Lance Taylor
- Re: char y = 469;
  - From: Diego Novillo

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