public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ohhara@postech.edu To: gcc-gnats@gcc.gnu.org Subject: c/3246: gcc -Wconversion doesn't work properly Date: Mon, 18 Jun 2001 23:56:00 -0000 [thread overview] Message-ID: <20010619064929.18134.qmail@sourceware.cygnus.com> (raw) >Number: 3246 >Category: c >Synopsis: gcc -Wconversion doesn't work properly >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Jun 18 23:56:02 PDT 2001 >Closed-Date: >Last-Modified: >Originator: ohhara@postech.edu >Release: gcc version 2.95.2 19991024 (release) >Organization: >Environment: redhat linux 6.2 i386, kernel 2.2.16-3, gcc 2.95.2, glibc-2.1.3-22 >Description: I use many warning options to find my small ( or big ) mistakes. Therefore, I tried to use -Wconversion warning option. However, it doesn't seem to work properly. For example, I tried following code with -Wconversion option. ---------- void f(unsigned char a); void f(unsigned char a) { } int main() { unsigned char a = 1; f(a); return 0; } ---------- And tried to compile this code ---------- [ ohhara@vm ~/tmp ] {180} $ gcc -Wconversion wconv.c wconv.c: In function `main': wconv.c:9: warning: passing arg 1 of `f' with different width due to prototype ---------- Why does it prints warning message? Even if I changed "unsigned char" to "unsigned short", the same warning message would be printed. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-06-18 23:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-18 23:56 ohhara [this message] 2001-06-19 5:16 Joseph S. Myers 2002-11-24 16:06 bangerth
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=20010619064929.18134.qmail@sourceware.cygnus.com \ --to=ohhara@postech.edu \ --cc=gcc-gnats@gcc.gnu.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: linkBe 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).