public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mishabear at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/25151] New: GCC issues warnings to a syntactically correct expression. Date: Tue, 29 Nov 2005 06:14:00 -0000 [thread overview] Message-ID: <bug-25151-11784@http.gcc.gnu.org/bugzilla/> (raw) Put the following code in a file tt.c and compile tt.c with command "gcc -Wall tt.c", then the compiler will complain. int main() { void *pv; pv = (pv=0); return 0; } The compiler complains: tt.c: In function `main': tt.c:5: warning: operation on `pv' may be undefined The result of "gcc --version" is: gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-52) Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. The result of "cat /etc/issue" is: Red Hat Enterprise Linux AS release 3 (Taroon Update 5) Kernel \r on an \m The result of "uname -a" is: Linux AS3-A64 2.4.21-32.EL #1 SMP Fri Apr 15 21:02:58 EDT 2005 x86_64 x86_64 x86_64 GNU/Linux In fact the type of pv has no matter with the warning. The warning will still show up if the type of pv is changed to int, short or double. -- Summary: GCC issues warnings to a syntactically correct expression. Product: gcc Version: 3.2.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mishabear at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25151
next reply other threads:[~2005-11-29 6:14 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-11-29 6:14 mishabear at gmail dot com [this message] 2005-11-29 6:28 ` [Bug c/25151] " pinskia at gcc dot gnu dot org 2005-11-29 7:44 ` mishabear at gmail dot com 2006-09-18 1:38 ` pinskia at gcc dot gnu dot org
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=bug-25151-11784@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).