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 5E3853857823; Sun,  7 Mar 2021 14:42:01 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5E3853857823
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/95432] inconsistent behaviors at -O2
Date: Sun, 07 Mar 2021 14:42:01 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-95432-4-NJVELu88zX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-95432-4@http.gcc.gnu.org/bugzilla/>
References: <bug-95432-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: Sun, 07 Mar 2021 14:42:01 -0000

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

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> Assembly:
>         .loc 1 12 3 is_stmt 1 view .LVU12
>         .loc 1 10 8 is_stmt 0 view .LVU13
>         movaps  %xmm0, (%rsp)
>         .loc 1 11 8 view .LVU14
>         movaps  %xmm0, 32(%rsp)
>         .loc 1 12 13 view .LVU15
>         call    foo
> .LVL1:
>         .loc 1 13 13 view .LVU16
>         leaq    32(%rsp), %rdi
>         .loc 1 12 13 view .LVU17
>         movl    %eax, %edx
> .LVL2:
>         .loc 1 13 3 is_stmt 1 view .LVU18
>         .loc 1 13 13 is_stmt 0 view .LVU19
>         call    foo
> .LVL3:
>         .loc 1 14 3 is_stmt 1 view .LVU20
>         .loc 1 14 6 is_stmt 0 view .LVU21
>=20
> Looks correct to me, both call foo have the correct line on them.  I think
> this is another GDB issue, most likely how dwarf3 and is_stmt is handled
> just like 95431 even.

Ack, this is gdb PR breakpoints/26063 (
https://sourceware.org/bugzilla/show_bug.cgi?id=3D26063 ).

Fixed by
https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Debde6f2ddc98=
7e7e2d5a218ee8cf0126ec189424
.=