public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/60165] "may be used uninitialized" warning with -O3 but not with -O2 Date: Thu, 13 Feb 2014 13:33:00 -0000 [thread overview] Message-ID: <bug-60165-4-i4qLWZwUPX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60165-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60165 --- Comment #14 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> --- (In reply to Marc Glisse from comment #9) > The definition of a function changes with inlining ;-) It shouldn't: what happens at run time isn't changed by inlining. > f(&i) is considered as an initialization of i. This heuristic is necessary, > otherwise the number of false positives would make the warning useless. Perhaps, but this isn't documented. > I don't know why you think warnings should be so well defined. According to the gcc man page, it is well-defined: the rule is given explicitly. (In reply to Jakub Jelinek from comment #12) > In your testcase, if fn1 isn't inlined, it is the same thing for GCC, a > function call as a black box which could do anything to the memory pointed > to by the escaped pointer (unless the function is say pure or const, at > which point it couldn't store to it). Here you assume that the function can do anything, while Marc said that GCC assumes that i is initialized. There's a contradiction. Moreover in the case of MPFR, the called function is in the same preprocessed source file, so that it is not obvious for the user that GCC will see it as a black box (when not inlined). >From gcc-bugs-return-443468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 13 13:35:46 2014 Return-Path: <gcc-bugs-return-443468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 22325 invoked by alias); 13 Feb 2014 13:35:46 -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 22287 invoked by uid 55); 13 Feb 2014 13:35:43 -0000 From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/59878] [4.9 Regression] ISL from cloog does not work with trunk Date: Thu, 13 Feb 2014 13:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Version: unknown 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: 4.9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-59878-4-ES2orpJDkM@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59878-4@http.gcc.gnu.org/bugzilla/> References: <bug-59878-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-02/txt/msg01225.txt.bz2 Content-length: 672 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY878 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Author: rguenth Date: Thu Feb 13 13:35:10 2014 New Revision: 207758 URL: http://gcc.gnu.org/viewcvs?rev 7758&root=gcc&view=rev Log: 2014-02-13 Richard Biener <rguenther@suse.de> PR bootstrap/59878 * doc/install.texi (ISL): Update recommended version to 0.12.2, mention the possibility of an in-tree build. (CLooG): Update recommended version to 0.18.1, mention the possibility of an in-tree build and clarify that the ISL bundled with CLooG does not work. Modified: trunk/gcc/ChangeLog trunk/gcc/doc/install.texi
next prev parent reply other threads:[~2014-02-13 13:33 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-13 3:17 [Bug tree-optimization/60165] New: " vincent-gcc at vinc17 dot net 2014-02-13 8:40 ` [Bug tree-optimization/60165] " vincent-gcc at vinc17 dot net 2014-02-13 9:21 ` rguenth at gcc dot gnu.org 2014-02-13 10:09 ` vincent-gcc at vinc17 dot net 2014-02-13 10:17 ` jakub at gcc dot gnu.org 2014-02-13 10:29 ` vincent-gcc at vinc17 dot net 2014-02-13 12:14 ` vincent-gcc at vinc17 dot net 2014-02-13 12:57 ` glisse at gcc dot gnu.org 2014-02-13 13:33 ` vincent-gcc at vinc17 dot net [this message] 2014-02-13 13:48 ` vincent-gcc at vinc17 dot net
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-60165-4-i4qLWZwUPX@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).