From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 96380 invoked by alias); 15 Jun 2015 13:34:07 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 96347 invoked by uid 48); 15 Jun 2015 13:34:04 -0000 From: "ldionne.2 at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/66543] New: False positive warning "variable set but not used" Date: Mon, 15 Jun 2015 13:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ldionne.2 at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-06/txt/msg01337.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D66543 Bug ID: 66543 Summary: False positive warning "variable set but not used" Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ldionne.2 at gmail dot com Target Milestone: --- The following code triggers a "unused but set variable" warning on GCC trun= k: int main() { auto f =3D []() { }; [=3D](auto) { using Foo =3D decltype(f()); }; } I think it is a false positive, since `f` is obviously used. > g++ --version g++ (GCC) 6.0.0 20150613 (experimental) > g++ -std=3Dc++14 worksheet.cpp -fsyntax-only -Wall -Wno-unused-local-type= defs In function =E2=80=98int main()=E2=80=99: warning: variable =E2=80=98f=E2=80=99 set but not used [-Wunused-but-set-va= riable] auto f =3D []() { }; ^ Regards, Louis Dionne >>From gcc-bugs-return-489006-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jun 15 13:59:47 2015 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 32880 invoked by alias); 15 Jun 2015 13:59:47 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 32833 invoked by uid 48); 15 Jun 2015 13:59:43 -0000 From: "olegendo at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/66358] [5/6 Regression] [SH] ICE: in extract_constrain_insn, at recog.c:2232 Date: Mon, 15 Jun 2015 13:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: olegendo at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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: 2015-06/txt/msg01338.txt.bz2 Content-length: 556 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66358 --- Comment #12 from Oleg Endo --- (In reply to John Paul Adrian Glaubitz from comment #11) > Any news on this issue? The sh4 buildds in Debian are currently building a > snapshot as of 2015-06-13 (r224454), let's see how far it gets. It will take a while to develop the R0 pre-allocating RTL pass as mentioned in c#10. Once this has been done and it's been stabilized it can be backported to the GCC 5 release branch -- assuming that it will fix the R0 reload problems.