public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, neil@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c/9166: [2003-01-03] C front end's type scoping not right
Date: Wed, 08 Jan 2003 01:03:00 -0000	[thread overview]
Message-ID: <20030108010355.14850.qmail@sources.redhat.com> (raw)

Synopsis: [2003-01-03] C front end's type scoping not right

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Tue Jan  7 17:03:54 2003
State-Changed-Why:
    This has been analyzed before. For completeness, here's what
    icc7 says:
    tmp/g> /home/bangerth/bin/gcc-3.4-pre/bin/gcc -std=c99 -c -pedantic x.c
    x.c: In function `foo':
    x.c:5: warning: `struct bar' declared inside parameter list
    x.c:5: warning: its scope is only this definition or declaration, which is probably not what you want
    tmp/g> icc x.c
    x.c(5): warning #274: declaration is not visible outside of function
        extern void f( struct bar {double x, y;} );
                              ^
    
    x.c(8): warning #159: declaration is incompatible with previous "f" (declared at line 5)
      void f (struct bar );
           ^
    
    From the discussion, this should really be a change-request
    than a bug report.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9166


             reply	other threads:[~2003-01-08  1:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08  1:03 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-01  8:37 neil
2003-01-04 13:36 Neil Booth
2003-01-04 11:26 Joseph S. Myers
2003-01-04  0:36 neil

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=20030108010355.14850.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=neil@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).