From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25948 invoked by alias); 14 Mar 2014 10:41:26 -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 25913 invoked by uid 48); 14 Mar 2014 10:41:22 -0000 From: "manu at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/60517] warning/error for taking address of member of a temporary object Date: Fri, 14 Mar 2014 10:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: manu at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: Message-ID: In-Reply-To: References: 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: 2014-03/txt/msg01147.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D60517 --- Comment #4 from Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez --- (In reply to Marc Glisse from comment #3) > (In reply to Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez from comment #2) > > (In reply to Marc Glisse from comment #1) > > > I see in the dump: > > >=20 > > > # .MEM_4 =3D VDEF <.MEM_8> > > > D.2272 =3D{v} {CLOBBER}; > > > # VUSE <.MEM_4> > > > _5 =3D MEM[(doubleD.39 *)&D.2272]; > > >=20 > > > which looks like something we could warn about in the middle-end. > >=20 > > Could you elaborate? My middle-end foo is not as good as it used to be. >=20 > _5 =3D MEM[(doubleD.39 *)&D.2272]; > says we are reading something inside variable D.2272. And right in the > previous instruction: > D.2272 =3D{v} {CLOBBER}; > we clobbered the content of that variable, so what we are reading is > nonsense. These clobbers are specifically added to indicate when variables > die (like your temporary). Where is the clobber added? The closer to the FE that we warn, the better diagnostic we can generate. I'm not very concerned about maybe-branches, si= nce=20 I expect most bugs to appear in temporaries created in the middle of expressions (such as a.getB().getA().x), where no branching occurs. >>From gcc-bugs-return-446279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Mar 14 10:45:13 2014 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 28092 invoked by alias); 14 Mar 2014 10:45:13 -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 28046 invoked by uid 48); 14 Mar 2014 10:45:10 -0000 From: "mpolacek at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/60523] Warning flag for octal literals Date: Fri, 14 Mar 2014 10:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: mpolacek at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: cc 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: 2014-03/txt/msg01148.txt.bz2 Content-length: 536 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60523 Marek Polacek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpolacek at gcc dot gnu.org --- Comment #3 from Marek Polacek --- I agree with Andrew - if we are ever to implement -Woctal, making it a part of -Wextra doesn't sound sensible. Especially with -Werror it'd be a pain.