public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/18322] New: __func__ diagnostic in bad location
Date: Sat, 06 Nov 2004 21:29:00 -0000	[thread overview]
Message-ID: <20041106212923.18322.jsm28@gcc.gnu.org> (raw)

The diagnostic for use of __func__ outside a function, as tested in
gcc.dg/func-outside-*.c, wrongly has line number 0 instead of the
line number of the bad use of __func__.

func-outside-1.c:0: warning: '__func__' is not defined outside of function scope

This is a regression from 3.2.x.

When fixed, the " { target *-*-* } 0" should be removed from those
testcases so they test the diagnostic in its proper location.

-- 
           Summary: __func__ diagnostic in bad location
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jsm28 at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18322


             reply	other threads:[~2004-11-06 21:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-06 21:29 jsm28 at gcc dot gnu dot org [this message]
2004-11-06 21:32 ` [Bug c/18322] [3.3/3.4/4.0 Regression] " pinskia at gcc dot gnu dot org
2004-11-09 21:22 ` cvs-commit at gcc dot gnu dot org
2004-11-10 19:47 ` [Bug c/18322] [3.3/3.4 " cvs-commit at gcc dot gnu dot org
2004-11-11 15:06 ` [Bug c/18322] [3.3 " pinskia at gcc dot gnu dot org
2005-04-30 16:31 ` gdr 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=20041106212923.18322.jsm28@gcc.gnu.org \
    --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: 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).