From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D6AE9385EC56; Tue, 11 Aug 2020 09:27:12 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D6AE9385EC56 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1597138032; bh=coVv1x8aYCRYCB7DnTCtSZJibCpiVMUI0Vo0ueacWVQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=bxG+jLCbNsaSg6SiineemlcrqBLxVXqDcSfVvdHHC+nhs8z4P2kBXuXmCq1VUPu2r WO2RDU4NYab8EYwfi8RV8sFCu2zb+i5Lxcz5qAysB+T6JlhD7ldxtB0L7tXVeRccdU q96aNBweEMEmAStbZkORQ9G5L3AINElp7+3bUNnc= From: "glisse at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/96564] New maybe use of uninitialized variable warning since GCC >10 Date: Tue, 11 Aug 2020 09:27:12 +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: 11.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: glisse 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: --- 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-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2020 09:27:13 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96564 --- Comment #1 from Marc Glisse --- I think there are duplicates about the fact that while gcc knows that a and= x cannot alias (if you read *x, write to *a, then read from *x again, gcc reu= ses the first value), it does not use that information to fold comparisons betw= een x and a.=