public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/5582: warn about using the extension "int x=x;"
Date: Wed, 08 Jan 2003 14:36:00 -0000	[thread overview]
Message-ID: <20030108143608.31561.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
Cc: pcarlini@unitus.it, <aoliva@redhat.com>, <dewar@gnat.com>,
   <gcc-gnats@gcc.gnu.org>, <coola@ngs.ru>, <gcc-bugs@gcc.gnu.org>,
   <bangerth@dealii.org>
Subject: Re: c/5582: warn about using the extension "int x=x;"
Date: Wed, 8 Jan 2003 08:24:46 -0600 (CST)

 > You get no error/warning, if you try to compile the code inside a
 > function, ie. "void foo() { int x=x; }".
 > But that's not a gcc extension, just a missing warning about the use of
 > an uninitialized variable.
 
 Sure. IIRC the extension is that this reliably calms down warnings about 
 uninitialized variables.
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-01-08 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 14:36 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-08 10:56 Volker Reichelt
2003-01-08  1:12 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=20030108143608.31561.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --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).