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++/61596] -Wunused-local-typedefs warns incorrectly on a typedef that's referenced indirectly Date: Mon, 24 Jan 2022 12:29:19 +0000 [thread overview] Message-ID: <bug-61596-4-YiokjLZxYM@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 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2014-06-26 00:00:00 |2022-1-24 --- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> --- This now warns about libstdc++ code, see PR 104019: /build/trunk/x86_64-unknown-dragonfly6.3/libstdc++-v3/include/bits/shared_ptr_base.h: In member function 'void std::_Sp_counted_array_base<_Alloc>::_M_init(typename std::allocator_traits<_Alloc>::value_type*, _Init)': /build/trunk/x86_64-unknown-dragonfly6.3/libstdc++-v3/include/bits/shared_ptr_base.h:767: warning: typedef 'using value_type = using _Up = typename std::allocator_traits<_Alloc>::value_type' locally defined but not used [-Wunused-local-typedefs] /build/trunk/x86_64-unknown-dragonfly6.3/libstdc++-v3/include/bits/shared_ptr_base.h:768: warning: typedef 'using difference_type = std::ptrdiff_t' locally defined but not used [-Wunused-local-typedefs] /build/trunk/x86_64-unknown-dragonfly6.3/libstdc++-v3/include/bits/shared_ptr_base.h:771: warning: typedef 'using iterator_category = struct std::forward_iterator_tag' locally defined but not used [-Wunused-local-typedefs] In file included from /build/trunk/x86_64-unknown-dragonfly6.3/libstdc++-v3/include/x86_64-unknown-dragonfly6.3/bits/stdc++.h:144: Those typedefs are 100% necessary because otherwise the local class is not a valid iterator type.
next prev parent reply other threads:[~2022-01-24 12:29 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 [this message] 2022-01-25 21:09 ` cvs-commit at gcc dot gnu.org 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-YiokjLZxYM@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).