public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "christian.morales.vega at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/105616] Using regex_replace throws "maybe-uninitialized" warnings
Date: Mon, 11 Jul 2022 14:58:46 +0000	[thread overview]
Message-ID: <bug-105616-4-5kcnHGDBpU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105616-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Cristian Morales Vega <christian.morales.vega at gmail dot com> ---
I don't think so.
Supposedly it was fixed 2 months ago in trunk
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105562#c14). But in
https://godbolt.org/z/8a979Gha8 the warnings are still present (even if the
full compilation doesn't complete because it takes too long for compiler
explorer).

  parent reply	other threads:[~2022-07-11 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 10:42 [Bug libstdc++/105616] New: " christian.morales.vega at gmail dot com
2022-05-16 10:56 ` [Bug libstdc++/105616] " jakub at gcc dot gnu.org
2022-07-11 14:58 ` christian.morales.vega at gmail dot com [this message]
2022-10-27  4:35 ` [Bug tree-optimization/105616] Using regex_replace throws "maybe-uninitialized" warnings with -fsanitize=address pinskia at gcc dot gnu.org
2022-11-22 19:09 ` redi at gcc dot gnu.org
2023-12-04 16:26 ` jg at jguk dot 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-105616-4-5kcnHGDBpU@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).