From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id AAFFF3858C27; Wed, 13 Oct 2021 15:54:44 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AAFFF3858C27
From: "cnsun at uwaterloo dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/100464] [11 Regression] emitted binary code
 changes when -g is enabled at -O3
Date: Wed, 13 Oct 2021 15:54:44 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 12.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cnsun at uwaterloo dot ca
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 11.3
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-100464-4-CrhwjFdnN5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-100464-4@http.gcc.gnu.org/bugzilla/>
References: <bug-100464-4@http.gcc.gnu.org/bugzilla/>
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 <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2021 15:54:44 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D100464

--- Comment #15 from Chengnian Sun <cnsun at uwaterloo dot ca> ---
(In reply to Jakub Jelinek from comment #14)
> Yes.  You'll get an error, like:
> error: t.c: =E2=80=98-fcompare-debug=E2=80=99 failure (length)
> or
> error: t.c: =E2=80=98-fcompare-debug=E2=80=99 failure
> Under the hood, the driver invokes the compiler once with
> the options you've given plus -fdump-final-insns=3Dsometempfile1
> and then also with the options you've given plus -gtoggle
> -fcompare-debug-second -fdump-final-insns=3Dsometempfile2 (and will throw=
 away
> stdout/stderr from the compiler).  The (length) failure means sometempfil=
e1
> and sometempfile2 have different lengths, while the other error mean they
> have the same length, but their content differs.

Thank you.=