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 c++/105545] [12/13 Regression] Warning for string assignment with _GLIBCXX_ASSERTIONS since r12-3347-g8af8abfbbace49e6
Date: Tue, 10 May 2022 12:26:00 +0000	[thread overview]
Message-ID: <bug-105545-4-60W2SZ7om3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105545-4@http.gcc.gnu.org/bugzilla/>

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[12/13 Regression]          |[12/13 Regression] Warning
                   |Compiling string assignment |for string assignment with
                   |with _GLIBCXX_ASSERTIONS    |_GLIBCXX_ASSERTIONS since
                   |fails since                 |r12-3347-g8af8abfbbace49e6
                   |r12-3347-g8af8abfbbace49e6  |
           Keywords|                            |diagnostic

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to John Buddery from comment #0)
>    g++ -m64 -c -std=gnu++17 -Wall -O3 -Werror -D_GLIBCXX_ASSERTIONS  x.cpp


This is only a warning. It fails because you asked it to, with -Werror.

Reporting that compilation fails when you turn warnings into errors isn't very
interesting, that's the point of -Werror :-)

So the bug here is a bogus warning, not that compilation fails. Summary
adjusted accordingly.

  parent reply	other threads:[~2022-05-10 12:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 11:15 [Bug c++/105545] New: Compiling string assignment with _GLIBCXX_ASSERTIONS defined fails in 12.1.0, works in 11.1.0 jvb at cyberscience dot com
2022-05-10 11:18 ` [Bug c++/105545] [12/13 Regression] Compiling string assignment with _GLIBCXX_ASSERTIONS fails since r12-3347-g8af8abfbbace49e6 marxin at gcc dot gnu.org
2022-05-10 12:26 ` redi at gcc dot gnu.org [this message]
2022-05-11  7:19 ` [Bug tree-optimization/105545] [12/13 Regression] Warning for string assignment with _GLIBCXX_ASSERTIONS " rguenth at gcc dot gnu.org
2022-05-12 15:17 ` ed at catmur dot uk
2022-05-12 15:51 ` tom at compton dot nu
2022-05-12 16:00 ` tom at compton dot nu
2022-05-31  7:33 ` tom at compton dot nu
2022-06-21 15:35 ` pdimov at gmail dot com
2022-11-03 18:07 ` pdimov at gmail dot com
2023-04-17 16:39 ` [Bug tree-optimization/105545] [12/13/14 " jvb at cyberscience dot com
2023-04-20 12:00 ` redi 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-105545-4-60W2SZ7om3@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).