public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-4111] libstdc++: Fix dumb typos in ALT128 support in <format> [PR107720]
Date: Wed, 16 Nov 2022 20:59:42 +0000 (GMT)	[thread overview]
Message-ID: <20221116205942.9DB24396DC23@sourceware.org> (raw)

https://gcc.gnu.org/g:dbdce6adb748b95be219f2f5fb97f844a0f9b840

commit r13-4111-gdbdce6adb748b95be219f2f5fb97f844a0f9b840
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Wed Nov 16 20:47:39 2022 +0000

    libstdc++: Fix dumb typos in ALT128 support in <format> [PR107720]
    
    This is only a partial fix for the PR.
    
    libstdc++-v3/ChangeLog:
    
            PR libstdc++/107720
            * include/std/format (__format::_Arg_t): Fix typo in enumerator
            name.
            (_Arg_value::_S_get): Fix missing semi-colons.

Diff:
---
 libstdc++-v3/include/std/format | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/libstdc++-v3/include/std/format b/libstdc++-v3/include/std/format
index 995b05c2ab2..1afcd042bc2 100644
--- a/libstdc++-v3/include/std/format
+++ b/libstdc++-v3/include/std/format
@@ -2578,7 +2578,7 @@ namespace __format
 #ifdef _GLIBCXX_LONG_DOUBLE_ALT128_COMPAT
     _Arg_next_value_,
     _Arg_f128 = _Arg_ldbl,
-    _Arg_ibm128 = _Args_next_value_,
+    _Arg_ibm128 = _Arg_next_value_,
 #else
     _Arg_f128,
 #endif
@@ -2916,9 +2916,9 @@ namespace __format
 #else
 	  // Don't use _Arg_ldbl for this target, it's ambiguous.
 	  else if constexpr (is_same_v<_Tp, __ibm128>)
-	    return _Arg_ibm128
+	    return _Arg_ibm128;
 	  else if constexpr (is_same_v<_Tp, __ieee128>)
-	    return _Arg_f128
+	    return _Arg_f128;
 #endif
 	  else if constexpr (is_same_v<_Tp, const _CharT*>)
 	    return _Arg_str;

                 reply	other threads:[~2022-11-16 20:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221116205942.9DB24396DC23@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).