public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/113099] locale without RTTI uses dynamic_cast before gcc 13.2 or has ODR violation since gcc 13.2
Date: Sun, 24 Dec 2023 14:44:44 +0000	[thread overview]
Message-ID: <bug-113099-4-7Jx9vY1CcZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113099-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I'm not sure what you mean by "the compiler is free to generate code that takes
it into account." Takes what into account? What problem does that freedom
cause?

The locale facet instantiations are compiled as C++11 (but other parts of the
library are compiled as C++17 or newer). We should do this so it uses
if-constexpr for everything except C++98:

--- a/libstdc++-v3/include/bits/locale_classes.tcc
+++ b/libstdc++-v3/include/bits/locale_classes.tcc
@@ -87,6 +87,8 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
                                __s2.data(), __s2.data() + __s2.length()) < 0);
     }

+#pragma GCC diagnostic push
+#pragma GCC diagnostic ignored "-Wc++17-extensions"
   template<typename _Facet>
     inline const _Facet*
     __try_use_facet(const locale& __loc) _GLIBCXX_NOTHROW
@@ -97,7 +99,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
       // We know these standard facets are always installed in every locale
       // so dynamic_cast always succeeds, just use static_cast instead.
 #define _GLIBCXX_STD_FACET(...) \
-      if _GLIBCXX17_CONSTEXPR (__is_same(_Facet, __VA_ARGS__)) \
+      if _GLIBCXX_CONSTEXPR (__is_same(_Facet, __VA_ARGS__)) \
        return static_cast<const _Facet*>(__facets[__i])

       _GLIBCXX_STD_FACET(ctype<char>);
@@ -145,6 +147,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
       return static_cast<const _Facet*>(__facets[__i]);
 #endif
     }
+#pragma GCC diagnostic pop

   /**
    *  @brief  Test for the presence of a facet.

  parent reply	other threads:[~2023-12-24 14:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20 23:41 [Bug libstdc++/113099] New: " andysem at mail dot ru
2023-12-21  8:59 ` [Bug libstdc++/113099] " rguenth at gcc dot gnu.org
2023-12-21 21:49 ` redi at gcc dot gnu.org
2023-12-23  9:37 ` andysem at mail dot ru
2023-12-23  9:39 ` andysem at mail dot ru
2023-12-24 14:44 ` redi at gcc dot gnu.org [this message]
2023-12-24 14:46 ` redi at gcc dot gnu.org
2023-12-24 15:04 ` pdimov at gmail dot com
2023-12-24 15:27 ` redi at gcc dot gnu.org
2023-12-24 15:30 ` redi at gcc dot gnu.org
2023-12-24 15:40 ` pdimov at gmail dot com
2023-12-24 16:22 ` andysem at mail dot ru
2023-12-26 12:31 ` redi at gcc dot gnu.org
2023-12-26 15:20 ` andysem at mail dot ru
2024-01-03 12:38 ` redi at gcc dot gnu.org
2024-01-03 12:43 ` redi at gcc dot gnu.org
2024-01-05 10:23 ` cvs-commit at gcc dot gnu.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=bug-113099-4-7Jx9vY1CcZ@http.gcc.gnu.org/bugzilla/ \
    --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).