public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian.s.mcinerney at ieee dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/96063] [10/11 Regression] mismatched-tags warnings in stdlib headers
Date: Wed, 08 Jul 2020 01:24:54 +0000	[thread overview]
Message-ID: <bug-96063-4-sG2l8wi2x5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96063-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Ian McInerney <ian.s.mcinerney at ieee dot org> ---
Is it possible to backport this to the GCC 10 branch? The printing of these
notes makes this warning almost impossible to use on any large project that
uses the standard library.

  parent reply	other threads:[~2020-07-08  1:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-05  0:41 [Bug libstdc++/96063] New: " ian.s.mcinerney at ieee dot org
2020-07-06 11:45 ` [Bug libstdc++/96063] " redi at gcc dot gnu.org
2020-07-06 16:01 ` ian.s.mcinerney at ieee dot org
2020-07-06 16:15 ` redi at gcc dot gnu.org
2020-07-06 16:19 ` redi at gcc dot gnu.org
2020-07-06 16:20 ` ian.s.mcinerney at ieee dot org
2020-07-06 16:21 ` ian.s.mcinerney at ieee dot org
2020-07-06 16:27 ` [Bug c++/96063] [10/11 Regression] " redi at gcc dot gnu.org
2020-07-06 16:34 ` redi at gcc dot gnu.org
2020-07-06 19:42 ` msebor at gcc dot gnu.org
2020-07-07  7:28 ` redi at gcc dot gnu.org
2020-07-07 16:46 ` msebor at gcc dot gnu.org
2020-07-07 17:24 ` cvs-commit at gcc dot gnu.org
2020-07-07 17:31 ` msebor at gcc dot gnu.org
2020-07-08  1:24 ` ian.s.mcinerney at ieee dot org [this message]
2020-07-13  9:15 ` ian.s.mcinerney at ieee dot org
2020-07-13  9:57 ` redi at gcc dot gnu.org
2020-07-13 12:59 ` ian.s.mcinerney at ieee dot org
2020-07-13 15:34 ` cvs-commit at gcc dot gnu.org
2020-07-13 15:36 ` [Bug c++/96063] [10 " msebor 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-96063-4-sG2l8wi2x5@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).