public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: Sonal.Santan@xilinx.com, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: c++/8905: Function attributes for C++ constructors confuses g++ frontend
Date: Wed, 11 Dec 2002 15:31:00 -0000 [thread overview]
Message-ID: <20021211233104.30047.qmail@sources.redhat.com> (raw)
Synopsis: Function attributes for C++ constructors confuses g++ frontend
State-Changed-From-To: open->closed
State-Changed-By: bangerth
State-Changed-When: Wed Dec 11 15:31:03 2002
State-Changed-Why:
This is a duplicate of PR 6992. The new parser which
will hopefully be in gcc3.4 will handle this correctly,
but it will probably not be fixed in gcc3.3 or 3.2.2.
W.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8905
next reply other threads:[~2002-12-11 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 15:31 bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-11 15:16 Sonal.Santan
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=20021211233104.30047.qmail@sources.redhat.com \
--to=bangerth@dealii.org \
--cc=Sonal.Santan@xilinx.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@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).