public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/109559] [12/13/14 Regression] Unexpected -Wmaybe-uninitialized warning when inlining with system header
Date: Wed, 19 Apr 2023 20:30:52 +0000 [thread overview]
Message-ID: <bug-109559-4-sZwwe9AKjv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109559-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109559
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Originally this happened when including boost headers, function_template.hpp in
particular, where newer versions suppress a lot of warnings:
commit b75386f628b46f1060a20b6e015931bac37b7da7 (origin/feature/drone)
Author: Peter Dimov <pdimov@gmail.com>
Date: Sun Feb 12 04:50:04 2023 +0200
Avoid -Wuninitialized under GCC 11.3
commit 9229ed30103df59a4f989ca0235b0d1026bf6e1c
Author: Peter Dimov <pdimov@gmail.com>
Date: Sun Feb 12 04:47:38 2023 +0200
Avoid another -Wmaybe-uninitialized under GCC 11/12
commit 16fca8368b5da14c4bcad977c2738dc6e482e1b7 (tag: boost-1.81.0.beta1, tag:
boost-1.81.0, tag: boost-1.80.0.beta1, tag: boost-1.80.0,
origin/feature/issue-42)
Author: Peter Dimov <pdimov@gmail.com>
Date: Mon May 30 20:25:13 2022 +0300
Keep -Wmaybe-uninitialized disabled
commit 4cf7c718b873223cbab6f8188bea2034f27ba99d
Merge: 389f886 5b4e279
Author: Peter Dimov <pdimov@gmail.com>
Date: Mon May 30 19:56:08 2022 +0300
Merge branch 'gcc12-Wuninitialized' of
https://github.com/jngrad/boost-function into feature/issue-42
commit abc1bf9b4ae3f45251d17b451c69c3e79dfd0cf6 (origin/feature/update-ci)
Author: Peter Dimov <pdimov@gmail.com>
Date: Mon May 30 18:44:07 2022 +0300
Extend GCC 11 workaround to GCC 12 as well
commit 5b4e2797a28f9477d2df5fa915409dac73ff00c6
Author: Jean-Noël Grad <jgrad@icp.uni-stuttgart.de>
Date: Mon May 30 16:16:41 2022 +0200
Avoid -Wuninitialized warnings in GCC 12
commit 277757befc321bda3b9d8038ee59ae6e4616cdca
Author: Peter Dimov <pdimov@gmail.com>
Date: Thu Dec 16 06:18:06 2021 +0200
Disable -Wmaybe-uninitialized in function_template.hpp for GCC 11
commit 7c90434317894f1a0c63c7a395ddf569eff1d308
Author: Romain Geissler <romain.geissler@amadeus.com>
Date: Fri Mar 27 18:56:14 2020 +0000
Avoid -Wmaybe-uninitialized warnings in gcc (issue #27).
next prev parent reply other threads:[~2023-04-19 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 20:23 [Bug middle-end/109559] New: " mpolacek at gcc dot gnu.org
2023-04-19 20:25 ` [Bug middle-end/109559] [12/13/14 Regression] " mpolacek at gcc dot gnu.org
2023-04-19 20:30 ` mpolacek at gcc dot gnu.org [this message]
2023-05-08 12:27 ` rguenth at gcc dot gnu.org
2024-01-12 10:29 ` rguenth at gcc dot gnu.org
2024-02-01 22:12 ` mpolacek at gcc dot gnu.org
2024-02-05 10:45 ` rguenth at gcc dot gnu.org
2024-02-05 12:36 ` rguenth at gcc dot gnu.org
2024-02-05 13:00 ` rguenth at gcc dot gnu.org
2024-02-06 9:53 ` rguenth 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-109559-4-sZwwe9AKjv@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).