This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/36797] ICE on SFINAE and __is_empty
- From: "sebor at roguewave dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Jul 2008 15:24:38 -0000
- Subject: [Bug c++/36797] ICE on SFINAE and __is_empty
- References: <bug-36797-1186@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #6 from sebor at roguewave dot com 2008-07-14 15:24 -------
(In reply to comment #4)
> ... Is it a reasonable
> restriction on users to say "thou shalt not use __is_empty in an expression
> that gets mangled"? For example, can the user just use std::is_empty instead?
As a data point, consider that the user may be an author of a third party
implementation of the C++ standard library (such as Apache/Rogue Wave or
STLport), and they may not be able to use std::is_empty for reasons unique
to their project (e.g., policy or otherwise).
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).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36797