public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Jim Wilson <wilson@specifixinc.com>
To: david <d.obermann@callassoftware.com>
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: gcc 3.3.3 bug( #9737 ?): "ambiguous class template instantiation"
Date: Mon, 17 May 2004 13:44:00 -0000 [thread overview]
Message-ID: <40A802A1.5050802@specifixinc.com> (raw)
In-Reply-To: <c7vl7l$ag4$1@sea.gmane.org>
david wrote:
> This seems to be the same bug as:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9737
> This is already a year old. Is there a workaround for this?
We don't track bugs reported via mail to gcc-bugs. You are better off
if you file bug reports into our bugzilla bug database. See
http://gcc.gnu.org/bugs.html
for more info on reporting bugs.
If you want to ask about status of a current bug report, then add a
comment to that bug report asking the question. This is more likely to
get a response than sending mail to gcc-bugs.
I am not a C++ expert, but from a quick look at bug 9737, it appears
that the ISO C++ language committee has decided that a C++ compiler is
not required to make this testcase work, however, it is allowed as an
extension to the C++ language. See Defect Report 150. Gcc does not
implement this extension yet. Since we rely on volunteers for most of
our work, there is no way to say when this extension will be implemented
in gcc.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
prev parent reply other threads:[~2004-05-17 0:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 23:00 gcc 3.3.3 bug(?): " david
2004-05-13 15:26 ` gcc 3.3.3 bug( #9737 ?): " david
2004-05-17 13:44 ` Jim Wilson [this message]
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=40A802A1.5050802@specifixinc.com \
--to=wilson@specifixinc.com \
--cc=d.obermann@callassoftware.com \
--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).