public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/92271] for consistency, __is_same_as should be named __is_same
       [not found] <bug-92271-4@http.gcc.gnu.org/bugzilla/>
@ 2020-09-30 17:42 ` cvs-commit at gcc dot gnu.org
  0 siblings, 0 replies; only message in thread
From: cvs-commit at gcc dot gnu.org @ 2020-09-30 17:42 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92271

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:73ae6eb572515ad627b575a7fbdfdd47a4368e1c

commit r11-3569-g73ae6eb572515ad627b575a7fbdfdd47a4368e1c
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Wed Sep 30 18:24:48 2020 +0100

    libstdc++: Use __is_same instead of __is_same_as

    PR 92271 added __is_same as another spelling of __is_same_as. Since
    Clang also spells it __is_same, let's just use that consistently.

    It appears that Intel icc sets __GNUC__ to 10, but only supports
    __is_same_as. If we only use __is_same for __GNUC__ >= 11 then we won't
    break icc again (it looks like we broke previous versions of icc when we
    started using __is_same_as).

    libstdc++-v3/ChangeLog:

            * include/bits/c++config (_GLIBCXX_HAVE_BUILTIN_IS_SAME):
            Define for GCC 11 or when !__is_identifier(__is_same).
            (_GLIBCXX_BUILTIN_IS_SAME_AS): Remove.
            * include/std/type_traits (is_same, is_same_v): Replace uses
            of _GLIBCXX_BUILTIN_IS_SAME_AS.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2020-09-30 17:42 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-92271-4@http.gcc.gnu.org/bugzilla/>
2020-09-30 17:42 ` [Bug c++/92271] for consistency, __is_same_as should be named __is_same cvs-commit at gcc dot gnu.org

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).