public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: John Love-Jensen <eljay@adobe.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
	"Kevin P. Fleming" <kpfleming@starnetworks.us>
Cc: MSX to GCC <gcc-help@gcc.gnu.org>
Subject: Re: -Wconversion producing incorrect warning
Date: Fri, 04 Nov 2005 12:20:00 -0000	[thread overview]
Message-ID: <BF90AE25.46AA%eljay@adobe.com> (raw)
In-Reply-To: <88b9f6ad3ed768b532e3485abc8a24bd@kernel.crashing.org>

Hi Segher,

> The problem here is, that -Wconversion does _not_ warn about type conversions
in your code!

From: http://gcc.gnu.org/onlinedocs/gcc-4.0.2/gcc/Warning-Options.html

-------------------------------------------------------------------
-Wconversion

Warn if a prototype causes a type conversion that is different from what
would happen to the same argument in the absence of a prototype. This
includes conversions of fixed point to floating and vice versa, and
conversions changing the width or signedness of a fixed point argument
except when the same as the default promotion.

Also, warn if a negative integer constant expression is implicitly converted
to an unsigned type. For example, warn about the assignment x = -1 if x is
unsigned. But do not warn about explicit casts like (unsigned) -1.
-------------------------------------------------------------------

What kind of type conversions in your code are you referring to?

--Eljay

  reply	other threads:[~2005-11-04 12:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 17:30 Kevin P. Fleming
2005-10-31 17:42 ` John Love-Jensen
2005-10-31 18:40   ` Kevin P. Fleming
2005-10-31 18:53     ` John Love-Jensen
2005-10-31 19:35       ` Kevin P. Fleming
2005-11-04 11:54 ` Segher Boessenkool
2005-11-04 12:20   ` John Love-Jensen [this message]
2005-11-04 12:38     ` Segher Boessenkool

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=BF90AE25.46AA%eljay@adobe.com \
    --to=eljay@adobe.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=kpfleming@starnetworks.us \
    --cc=segher@kernel.crashing.org \
    /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).