public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/61596] -Wunused-local-typedefs warns incorrectly on a typedef that's referenced indirectly Date: Tue, 25 Jan 2022 21:09:38 +0000 [thread overview] Message-ID: <bug-61596-4-9WODYFEevb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61596-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61596 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:5c1f274e3e090ee03bedc22dd7169b28e759974e commit r12-6868-g5c1f274e3e090ee03bedc22dd7169b28e759974e Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Jan 25 10:22:42 2022 +0000 libstdc++: Avoid some more warnings [PR104019] With -fno-exceptions we get a -Wmisleading-indentation warning for: if (cond) __try {} __catch (...) {} This is because the __catch(...) expands to if (false), but is indented as though it is controlled by the preceding 'if'. Surround it in braces. The new make_shared<T[]> code triggers a bogus warning due to PR 61596, which can be disabled with a pragma. libstdc++-v3/ChangeLog: PR libstdc++/104019 * include/bits/istream.tcc (basic_istream::sentry): Add braces around try-block. * include/bits/shared_ptr_base.h (_Sp_counted_array_base::_M_init): Add pragmas to disable bogus warnings from PR 61596.
next prev parent reply other threads:[~2022-01-25 21:09 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-24 16:49 [Bug c++/61596] New: " thakis at chromium dot org 2014-06-26 17:01 ` [Bug c++/61596] " paolo.carlini at oracle dot com 2014-07-28 1:53 ` thakis at chromium dot org 2022-01-24 12:29 ` redi at gcc dot gnu.org 2022-01-25 21:09 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-07 10:46 ` redi at gcc dot gnu.org 2022-10-30 20:13 ` pinskia 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-61596-4-9WODYFEevb@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: linkBe 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).