public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redboltz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/95765] std::vector should be built without warnings with -Wconversion and/or -Wsystem-headers
Date: Fri, 19 Jun 2020 23:23:24 +0000	[thread overview]
Message-ID: <bug-95765-4-M1LgO4aDsE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95765-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Takatoshi Kondo <redboltz at gmail dot com> ---
Thank you for fixing the warnings.

> Users should not be routinely using -Wsystem-headers to find problems with their own code (that defeats the entire purpose of suppressing warnings in system headers).
>
> I've fixed some warnings in libstdc++ code, but the real problem here is Bug 43167 (and Bug 43167 comment 17 has almost exactly the same example).

I agree. If warnings relate to templates would be reported without
`-Wsystem-headers`, it is ideal.

  parent reply	other threads:[~2020-06-19 23:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19 12:11 [Bug libstdc++/95765] New: " redboltz at gmail dot com
2020-06-19 19:09 ` [Bug libstdc++/95765] " cvs-commit at gcc dot gnu.org
2020-06-19 19:10 ` redi at gcc dot gnu.org
2020-06-19 19:12 ` redi at gcc dot gnu.org
2020-06-19 23:23 ` redboltz at gmail dot com [this message]
2021-03-29 20:05 ` 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-95765-4-M1LgO4aDsE@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).