From: Andrew Pinski <pinskia@gmail.com>
To: Mark Tall <mtall.qld@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: c++ template conformance: gcc vs MS
Date: Thu, 28 May 2009 10:07:00 -0000 [thread overview]
Message-ID: <de8d50360905272216g4e9a9c74w9ab4a2c58044efa3@mail.gmail.com> (raw)
In-Reply-To: <454c00060905272156s29c090f4s23aa8e5a13dff712@mail.gmail.com>
On Wed, May 27, 2009 at 9:56 PM, Mark Tall <mtall.qld@gmail.com> wrote:
> [Sorry, I pasted the wrong compiler output (but for the same bug).
> Below is the corrected e-mail. ]
>
> I've come across a possible issue with GCC's adherence to the C++
> standard for handling template code (gcc version 4.3.2 20081105 from
> Fedora 10).
>
> The following code compiles fine under GCC (using -pedantic and
> -std=c++98), but fails under Microsoft's C++ 2008 SP1.
>
> Microsoft explains this on
> http://msdn.microsoft.com/en-us/library/cx7k7hcf(VS.80).aspx
>
> Is GCC or Microsoft at fault ?
GCC see http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24314 .
Thanks,
Andrew Pinski
next prev parent reply other threads:[~2009-05-28 5:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 6:12 Mark Tall
2009-05-28 9:35 ` Mark Tall
2009-05-28 10:07 ` Andrew Pinski [this message]
2009-05-28 15:45 ` Mark Tall
2009-05-28 16:42 ` Daniel Berlin
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=de8d50360905272216g4e9a9c74w9ab4a2c58044efa3@mail.gmail.com \
--to=pinskia@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=mtall.qld@gmail.com \
/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).