public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/36797] ICE on SFINAE and __is_empty
Date: Mon, 14 Jul 2008 15:28:00 -0000	[thread overview]
Message-ID: <20080714152813.26486.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36797-1186@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from mark at codesourcery dot com  2008-07-14 15:28 -------
Subject: Re:  ICE on SFINAE and __is_empty

sebor at roguewave dot com wrote:

> My preference would be for gcc to avoid imposing restrictions on the use
> of these helpers to facilitate portability to other compilers such as EDG
> eccp (the latest 3.10.1 compiles the test case correctly).

How does it mangle it?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36797


  parent reply	other threads:[~2008-07-14 15:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10 21:27 [Bug c++/36797] New: " sebor at roguewave dot com
2008-07-11 11:09 ` [Bug c++/36797] " paolo dot carlini at oracle dot com
2008-07-11 11:12 ` paolo dot carlini at oracle dot com
2008-07-11 13:55 ` paolo dot carlini at oracle dot com
2008-07-13 17:42 ` mmitchel at gcc dot gnu dot org
2008-07-14  9:16 ` paolo dot carlini at oracle dot com
2008-07-14 15:25 ` sebor at roguewave dot com
2008-07-14 15:28 ` mark at codesourcery dot com [this message]
2008-07-14 15:42 ` sebor at roguewave dot com
2008-07-14 16:53 ` mark at codesourcery dot com
2008-07-14 18:44 ` sebor at roguewave dot com
2009-08-03  0:01 ` paolo dot carlini at oracle dot com
2009-08-19 18:50 ` jason at gcc dot gnu dot org
2010-04-21 22:50 ` [Bug c++/36797] ICE mangling __is_empty jason at gcc dot gnu dot org

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=20080714152813.26486.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --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).