public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom St Denis <tstdenis@ellipticsemi.com>
To: "Humpolicek, Jiri - Acision" <jiri.humpolicek@acision.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc warnings
Date: Wed, 17 Oct 2007 11:49:00 -0000	[thread overview]
Message-ID: <4715F65A.20106@ellipticsemi.com> (raw)
In-Reply-To: <53248A54C3B3EC4EAAD993D10A6DD01203C5DAB7@cz-ex002.groupinfra.com>

Humpolicek, Jiri - Acision wrote:
> Hi,
>             I have, from my point of view, strange problem. I want to tell gcc to report all compilation warnings, especially warnings about assigment from variable of greater type to variable with smaller type. For example, when I write following code and compile it with next command no warning is reported:
>
> c++ -o test test.cpp -Wall -Wextra -Wconversion -pedantic
>
> #include "stdio.h"
>
> int main()
> {
>         long a = 10000;
>         unsigned char b = a;
>
>         printf("%d\n", b);
>
>         return b;
> }
>
>   

The problem is that's not an error or problem as far as the C standard 
[and C++] goes.  So a warning for that while valid, would probably be 
out of line.

My recommendation is to simply not assign across types unless you have 
to.  If you have a function like

void myfunc(unsigned long somevalue)
{
}

Then never store somevalue in anything but an unsigned long unless 
you're sure of what you are doing.  Why would you write

char careless = somevalue;

just for the hell of it? 

Tom


  parent reply	other threads:[~2007-10-17 11:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17  9:08 Humpolicek, Jiri - Acision
2007-10-17 11:48 ` John Love-Jensen
2007-10-17 11:49 ` Tom St Denis [this message]
2007-10-17 14:08   ` Humpolicek, Jiri - Acision
2007-10-17 13:28 ` Tim Prince
2007-10-17 14:28   ` Humpolicek, Jiri - Acision
2007-10-17 15:25     ` Andrew Haley
  -- strict thread matches above, loose matches on Subject: below --
2008-08-12 15:36 kamelopardus
2008-08-12 15:48 ` Andrew Bell
2008-08-12 15:52   ` Joel Dice
2008-08-12 17:19   ` kamelopardus
2000-05-24 14:29 Zia Babar
2000-05-24 23:48 ` Martin v. Loewis

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=4715F65A.20106@ellipticsemi.com \
    --to=tstdenis@ellipticsemi.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jiri.humpolicek@acision.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).