public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: pme@gcc.gnu.org To: djg@cl.cam.ac.uk, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, pb@cl.cam.ac.uk Subject: Re: c++/5568: compiles for ever as a c++ file but ok as a .c file Date: Fri, 19 Apr 2002 13:43:00 -0000 [thread overview] Message-ID: <20020419204301.670.qmail@sources.redhat.com> (raw) Synopsis: compiles for ever as a c++ file but ok as a .c file State-Changed-From-To: open->closed State-Changed-By: pme State-Changed-When: Fri Apr 19 13:42:59 2002 State-Changed-Why: Using 3.1 prerelease sources, it compiles in about a quarter-second for me: 219% time g++ 5568_gcctest.cpp real 0m0.265s user 0m0.200s sys 0m0.060s 220% http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5568
next reply other threads:[~2002-04-19 20:43 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-19 13:43 pme [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-02-01 3:16 djg
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=20020419204301.670.qmail@sources.redhat.com \ --to=pme@gcc.gnu.org \ --cc=djg@cl.cam.ac.uk \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=pb@cl.cam.ac.uk \ /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).