public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/40635] bogus name and location in 'may be used uninitialized' warning Date: Thu, 19 Dec 2013 10:17:00 -0000 [thread overview] Message-ID: <bug-40635-4-21nzgpWNuY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-40635-4@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 3182 bytes --] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40635 --- Comment #5 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to philipp from comment #4) > I have this or a very similar problem with debian amd64 4:4.8.2-1: > > main.c: In function âmainâ: > main.c:1231:23: error: ârvâ may be used uninitialized in this function > [-Werror=maybe-uninitialized] > return (rv_main >= 0 && rv_main < 0x70) ? rv_main : 1; Can you attach a small, preprocessed testcase? See http://gcc.gnu.org/bugs/minimize.html >From gcc-bugs-return-438088-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 19 10:39:41 2013 Return-Path: <gcc-bugs-return-438088-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 17978 invoked by alias); 19 Dec 2013 10:39:40 -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 17962 invoked by uid 48); 19 Dec 2013 10:39:37 -0000 From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/59557] New: [4.8/4.9 Regression] Date: Thu, 19 Dec 2013 10:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 4.8.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: <bug-59557-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: 2013-12/txt/msg01743.txt.bz2 Content-length: 1041 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY557 Bug ID: 59557 Summary: [4.8/4.9 Regression] Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org Created attachment 31479 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id1479&actioníit testcase A libstdc++ change between r202388 and the 4.8.2 release broke Eigen. Preprocessing the attached testcase with 4.8.2 and then compiling with -O0 gives > ./a.out Brute force distance = 0.00428018, calls = 10000 Segmentation fault while preprocessing with 4.8.1 gets the correct > ./a.out Brute force distance = 0.00428018, calls = 10000 BVH distance = 0.00428018, calls = 756
next prev parent reply other threads:[~2013-12-19 10:17 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-40635-4@http.gcc.gnu.org/bugzilla/> 2013-11-01 21:56 ` manu at gcc dot gnu.org 2013-12-19 10:17 ` manu at gcc dot gnu.org [this message] 2013-12-19 10:40 ` philipp at marek dot priv.at 2013-12-19 10:51 ` manu at gcc dot gnu.org 2013-12-19 10:57 ` philipp at marek dot priv.at 2013-12-19 10:59 ` philipp at marek dot priv.at 2021-03-25 21:07 ` msebor at gcc dot gnu.org 2021-03-25 21:08 ` msebor at gcc dot gnu.org 2021-03-25 22:40 ` msebor at gcc dot gnu.org 2021-12-15 18:43 ` msebor at gcc dot gnu.org 2021-12-15 18:48 ` [Bug tree-optimization/40635] [12 Regression] " msebor at gcc dot gnu.org 2021-12-15 19:00 ` msebor at gcc dot gnu.org 2021-12-15 19:14 ` pinskia at gcc dot gnu.org 2021-12-18 10:46 ` pinskia at gcc dot gnu.org 2022-01-21 13:56 ` rguenth at gcc dot gnu.org 2022-03-17 19:25 ` msebor at gcc dot gnu.org 2022-03-17 22:00 ` pinskia at gcc dot gnu.org 2022-05-06 8:29 ` [Bug tree-optimization/40635] [12/13 " jakub at gcc dot gnu.org 2022-11-20 3:11 ` law at gcc dot gnu.org 2022-12-05 15:00 ` rguenth at gcc dot gnu.org 2022-12-05 15:51 ` cvs-commit at gcc dot gnu.org 2023-05-08 12:21 ` [Bug tree-optimization/40635] [12 " rguenth 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-40635-4-21nzgpWNuY@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).