public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthias Kretz <m.kretz@gsi.de>
To: <gcc-patches@gcc.gnu.org>, <libstdc++@gcc.gnu.org>
Subject: [PATCH 0/2] Make use of the diagnose_as attribute to improve libstdc++ diagnostics
Date: Mon, 15 Nov 2021 18:04:01 +0100	[thread overview]
Message-ID: <1849892.9kXth2LyAg@excalibur> (raw)

After my two C++ patches for template diagnostics and the diagnose_as 
attribute are in, I'd like to make use of the attribute for std::*string and 
std::pmr::*string as well as for std::experimental::simd diagnostics.

Matthias Kretz (2):
  libstdc++: Use diagnose_as attribute to improve string diagnostics
  libstdc++: Use diagnose_as attribute to improve simd diagnostics

 libstdc++-v3/include/bits/c++config           |  3 +-
 libstdc++-v3/include/bits/stringfwd.h         | 10 ++---
 libstdc++-v3/include/debug/string             | 10 ++---
 libstdc++-v3/include/experimental/bits/simd.h | 37 +++++--------------
 .../include/experimental/bits/simd_detail.h   |  2 +-
 libstdc++-v3/include/experimental/string      | 10 ++---
 libstdc++-v3/include/std/string               | 10 ++---
 7 files changed, 33 insertions(+), 49 deletions(-)

-- 
──────────────────────────────────────────────────────────────────────────
 Dr. Matthias Kretz                           https://mattkretz.github.io
 GSI Helmholtz Centre for Heavy Ion Research               https://gsi.de
 stdₓ::simd
──────────────────────────────────────────────────────────────────────────


             reply	other threads:[~2021-11-15 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 17:04 Matthias Kretz [this message]
2021-11-15 17:05 ` [PATCH 1/2] libstdc++: Use diagnose_as attribute to improve string diagnostics Matthias Kretz
2021-11-15 17:05 ` [PATCH 2/2] libstdc++: Use diagnose_as attribute to improve simd diagnostics Matthias Kretz

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=1849892.9kXth2LyAg@excalibur \
    --to=m.kretz@gsi.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@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).