public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Kinh Nguyen <xkinh@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/10170: Is this a bug of GCC? or it's a C syntax
Date: Thu, 20 Mar 2003 21:26:00 -0000	[thread overview]
Message-ID: <20030320212600.12082.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/10170; it has been noted by GNATS.

From: Kinh Nguyen <xkinh@yahoo.com>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
  nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c/10170: Is this a bug of GCC? or it's a C syntax
Date: Thu, 20 Mar 2003 13:21:37 -0800 (PST)

 I totally agree with you about the C syntax and the
 way GCC handles it.  I just hope the GCC would detect
 and give a warning so life would be easier for C
 programmers.  I made a mistake in typing when I 
 modified a big program. It gave me a lot of head-ache
 to figure out the problem.
 Thanks
 Kinh
 
 --- bangerth@dealii.org wrote:
 > Synopsis: Is this a bug of GCC? or it's a C syntax
 > 
 > State-Changed-From-To: open->closed
 > State-Changed-By: bangerth
 > State-Changed-When: Thu Mar 20 18:44:53 2003
 > State-Changed-Why:
 >     Your code is perfectly legal: you take the
 > address of a
 >     function and in the if-statement, it is
 > implicitly compared
 >     against zero. Since the function's address is
 > non-zero, 
 >     the printf-branch is executed.
 >     
 >     Other compilers will certainly not give you
 > errors on this
 >     code, since it is legal. They may give you
 > warnings, as
 >     icc does here, for example:
 >     g/x> icc x.c
 >     x.c(4): warning #279: controlling expression is
 > constant
 >         if (alwayzero)
 >             ^
 >     
 >     W.
 > 
 >
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10170
 
 
 __________________________________________________
 Do you Yahoo!?
 Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
 http://platinum.yahoo.com


             reply	other threads:[~2003-03-20 21:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 21:26 Kinh Nguyen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-20 18:44 bangerth
2003-03-20 18:26 xkinh

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=20030320212600.12082.qmail@sources.redhat.com \
    --to=xkinh@yahoo.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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: 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).