public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "thakis at chromium dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/61596] New: -Wunused-local-typedefs warns incorrectly on a typedef that's referenced indirectly Date: Tue, 24 Jun 2014 16:49:00 -0000 [thread overview] Message-ID: <bug-61596-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61596 Bug ID: 61596 Summary: -Wunused-local-typedefs warns incorrectly on a typedef that's referenced indirectly Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: thakis at chromium dot org -Wunused-local-typedefs warns that the typedef in line "XXX" is unused, but it's used in line "YYY": auto f() { struct S { typedef int t; // XXX }; return S(); } void g() { auto x = f(); decltype(x)::t y; // YYY } /example.cpp: In function ‘auto f()’: 2 : warning: typedef ‘f()::S::t’ locally defined but not used [-Wunused-local-typedefs] struct S { typedef int t; }; ^ (This is with 4.9.0. Testcase from Richard Smith.) >From gcc-bugs-return-454805-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jun 24 17:03:36 2014 Return-Path: <gcc-bugs-return-454805-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 31502 invoked by alias); 24 Jun 2014 17:03:36 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 31455 invoked by uid 55); 24 Jun 2014 17:03:33 -0000 From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/61268] [4.10 regression] ICE in vt_expand_var_loc_chain, at var-tracking.c:8262 Date: Tue, 24 Jun 2014 17:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 4.10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.10.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-61268-4-2wIVzqJ8dS@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-61268-4@http.gcc.gnu.org/bugzilla/> References: <bug-61268-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-06/txt/msg01887.txt.bz2 Content-length: 682 https://gcc.gnu.org/bugzilla/show_bug.cgi?ida268 --- Comment #7 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #6 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- >> --- Comment #5 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> --- > [...] >> The patch passed bootstrap on x86_64-linux-gnu but could you test it for >> sparc too? > > Sure: sparc-sun-solaris2.11 bootstrap in progress. I'll be leaving for > a short vacation before that finishes, so don't expect a result before > tuesday next week. The bootstrap finished successfully and the ICE is gone. Thanks. Rainer
next reply other threads:[~2014-06-24 16:49 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-24 16:49 thakis at chromium dot org [this message] 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 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@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).