public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/29409] [gdb, tdep/aarch64] FAIL: gdb.opt/inline-small-func.exp: info breakpoints
Date: Tue, 26 Jul 2022 08:56:31 +0000	[thread overview]
Message-ID: <bug-29409-4717-NTRXOeY724@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29409-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29409

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
After applying this patch:
...
diff --git a/gdb/testsuite/gdb.opt/inline-small-func.h
b/gdb/testsuite/gdb.opt/inline-small
-func.h
index 66323952cf4..79c40ef824a 100644
--- a/gdb/testsuite/gdb.opt/inline-small-func.h
+++ b/gdb/testsuite/gdb.opt/inline-small-func.h
@@ -15,7 +15,7 @@

 int counter = 42;

-inline void
+static inline void __attribute__((always_inline))
 callee () {
   counter = 0; /* callee: body.  */
 }
...
I can run the test-case with clang on x86_64 and run into:
...
FAIL: gdb.opt/inline-small-func.exp: info breakpoints
...

We have insn:
...
00000000004004a7 <main>:
  4004a7:       c7 05 77 0b 20 00 00    movl   $0x0,0x200b77(%rip)        #
601028 <counter>
  4004ae:       00 00 00
  4004b1:       b8 00 00 00 00          mov    $0x0,%eax
  4004b6:       c3                      ret
...
and lines:
...
CU: inline-small-func.c:
File name                      Line number    Starting address    View    Stmt
inline-small-func.c                     20            0x4004a7               x

inline-small-func.h:
inline-small-func.h                     20            0x4004a7       1       x

inline-small-func.c:
inline-small-func.c                     23            0x4004b1               x
inline-small-func.c                      -            0x4004b7
...

This looks similar to the gcc info.  So, why are we supposed to trust llvm?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-07-26  8:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  8:25 [Bug tdep/29409] New: " vries at gcc dot gnu.org
2022-07-26  8:51 ` [Bug tdep/29409] " vries at gcc dot gnu.org
2022-07-26  8:56 ` vries at gcc dot gnu.org [this message]
2022-07-26  9:05 ` vries at gcc dot gnu.org
2022-07-26  9:12 ` luis.machado at arm dot com
2022-07-26 10:58 ` vries at gcc dot gnu.org
2022-07-26 11:14 ` vries at gcc dot gnu.org
2022-07-26 12:57 ` vries at gcc dot gnu.org
2022-07-26 13:10 ` luis.machado at arm dot com
2022-07-26 13:36 ` vries at gcc dot gnu.org
2022-07-26 13:58 ` luis.machado at arm dot com
2022-07-26 14:47 ` vries at gcc dot gnu.org
2022-07-26 15:30 ` vries at gcc dot gnu.org
2022-08-10 13:50 ` vries at gcc dot gnu.org
2022-08-11 11:59 ` vries 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-29409-4717-NTRXOeY724@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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).