public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: and@rsu.ru, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	geoffk@gcc.gnu.org, nobody@gcc.gnu.org, wanderer@rsu.ru
Subject: Re: c++/10470: [pch] spurious warning about "anonymous variadic macros were introduced in C99"
Date: Thu, 24 Apr 2003 01:33:00 -0000	[thread overview]
Message-ID: <20030424013357.29439.qmail@sources.redhat.com> (raw)

Old Synopsis: anonymous variadic macros were introduced in C99 warning at pch using
New Synopsis: [pch] spurious warning about "anonymous variadic macros were introduced in C99"

Responsible-Changed-From-To: unassigned->geoffk
Responsible-Changed-By: bangerth
Responsible-Changed-When: Thu Apr 24 01:33:56 2003
Responsible-Changed-Why:
    pch
State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Thu Apr 24 01:33:56 2003
State-Changed-Why:
    Geoff, I think you're being overly harsh -- the bug report
    includes everything one needs to reproduce the problem. I
    see the very same reported problem on my linux box. It
    should be simple for you as well to reproduce this.
    
    W.
    
    g/x> cat x.h
    #include<string>
    
    g/x> cat x.cc
    #include"x.h"
    
    int main() {
      return 0;
    }
    
    g/x> rm x.h.gch
    rm: cannot remove `x.h.gch': No such file or directory
    g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -ansi -pedantic -Werror -Winvalid-pch -c x.cc
    g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -ansi -pedantic -Werror -Winvalid-pch -c x.h
    g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -ansi -pedantic -Werror -Winvalid-pch -c x.cc
    x.cc:679:2: anonymous variadic macros were introduced in C99
    
    Note also the bogus line number 679, which certainly doesn't
    exist in this file.

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


             reply	other threads:[~2003-04-24  1:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24  1:33 bangerth [this message]
2003-04-28 12:36 Vladimir Merzliakov

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=20030424013357.29439.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=and@rsu.ru \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=geoffk@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=wanderer@rsu.ru \
    /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).