public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-95432-4-NJVELu88zX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95432-4@http.gcc.gnu.org/bugzilla/>

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

--- 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
> 
> 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=26063 ).

Fixed by
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ebde6f2ddc987e7e2d5a218ee8cf0126ec189424
.

  parent reply	other threads:[~2021-03-07 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-30  3:02 [Bug debug/95432] New: " yangyibiao at hust dot edu.cn
2020-05-30  3:03 ` [Bug debug/95432] " yangyibiao at hust dot edu.cn
2021-03-07  7:25 ` pinskia at gcc dot gnu.org
2021-03-07 14:42 ` vries at gcc dot gnu.org [this message]
2021-03-07 20:27 ` pinskia 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-95432-4-NJVELu88zX@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: link
Be 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).