public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com> To: geoffk@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/10470: anonymous variadic macros were introduced in C99 warning at pch using Date: Thu, 24 Apr 2003 02:36:00 -0000 [thread overview] Message-ID: <20030424023600.5846.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/10470; it has been noted by GNATS. From: Phil Edwards <phil@jaj.com> To: wanderer@rsu.ru Cc: gcc-gnats@gcc.gnu.org, and@rsu.ru Subject: Re: c++/10470: anonymous variadic macros were introduced in C99 warning at pch using Date: Wed, 23 Apr 2003 22:26:49 -0400 On Wed, Apr 23, 2003 at 09:45:39PM -0000, wanderer@rsu.ru wrote: > >Description: > simple test.c test.h files compile without using pch > and generate strange warning if use test.h.gch > > All case with options: g++ -ansi -pedantic -Werror -Winvalid-pch > > -test.h----8<----------- > #include<string> > -test.h---->8----------- > > -test.cc---8<----------- > #include"test.h" > > int main() { > return 0; > } > -test.cc--->8----------- > > Warning generated at line in concept_check.h:52 : > > #define __glibcpp_function_requires(...) That code isn't going to change anytime soon; see the comment preceeding it. That header is marked with system_header. It shouldn't be generating these warnings, even in PCH mode... -- If ye love wealth greater than liberty, the tranquility of servitude greater than the animating contest for freedom, go home and leave us in peace. We seek not your counsel, nor your arms. Crouch down and lick the hand that feeds you; and may posterity forget that ye were our countrymen. - Samuel Adams
next reply other threads:[~2003-04-24 2:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-24 2:36 Phil Edwards [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-23 21:46 wanderer
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=20030424023600.5846.qmail@sources.redhat.com \ --to=phil@jaj.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=geoffk@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: linkBe 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).