public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@medozas.de>
To: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
Cc: Richard Guenther <richard.guenther@gmail.com>, gcc@gnu.org
Subject: Re: GCC feature req: warn when bitops exceed type size (was:   conntrack untracked match is broken)
Date: Mon, 29 Jun 2009 19:02:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.00.0906292026060.5445@fbirervta.pbzchgretzou.qr> (raw)
In-Reply-To: <6c33472e0906290709q6d4db132u60df53018125499b@mail.gmail.com>


On Monday 2009-06-29 16:09, Manuel López-Ibáñez wrote:
>2009/6/29 Richard Guenther wrote:
>> On Mon, Jun 29, 2009 at 3:10 PM, Jan Engelhardt wrote:
>>> Hi gcc list,
>>>
>>>
>>> I am forwarding below's bugreport here(*), to implicitly make aware
>>> of a feature that I deem important to have in a future gcc.
>>>
>>
>> -Wconversion should say
>>
>> t.c:4: warning: conversion to ‘unsigned char’ from ‘int’ may alter its value

I added -Wconversion to the Linux kernel's global cflags (KBUILD_CFLAGS) 
just to see what would happen. As I expected, I get swamped with 
warnings, like "conversion to int from unsigned int". All legitimate in 
themselves, I would have preferred an option (or even no option at all, 
given that the "large integer implicitly truncated to unsigned type" 
warning is shown without any -W flags) that only flags up truncation 
problems with literals.

  reply	other threads:[~2009-06-29 18:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 13:59 Jan Engelhardt
2009-06-29 14:06 ` Richard Guenther
2009-06-29 16:25   ` Manuel López-Ibáñez
2009-06-29 19:02     ` Jan Engelhardt [this message]
2009-06-30  2:08       ` Manuel López-Ibáñez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LSU.2.00.0906292026060.5445@fbirervta.pbzchgretzou.qr \
    --to=jengelh@medozas.de \
    --cc=gcc@gnu.org \
    --cc=lopezibanez@gmail.com \
    --cc=richard.guenther@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).