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 10:58:20 +0000 [thread overview]
Message-ID: <bug-29409-4717-yySCYSXcg4@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 #5 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Luis Machado from comment #4)
> Thanks. FTR, on Ubuntu 22.04 and 20.04 I don't see this. Might also be
> sensitive to compiler version.
Yes, that's quite possible.
With gcc 7.5.0, we have:
...
$ gcc ./src/gdb/testsuite/gdb.opt/inline-small-func.c -O1 -g -c
$ objdump -d inline-small-func.o
inline-small-func.o: file format elf64-x86-64
Disassembly of section .text:
0000000000000000 <main>:
0: c7 05 00 00 00 00 00 movl $0x0,0x0(%rip) # a <main+0xa>
7: 00 00 00
a: b8 00 00 00 00 mov $0x0,%eax
f: c3 ret
$ readelf -wL inline-small-func.o
Contents of the .debug_line section:
CU: inline-small-func.c:
File name Line number Starting address View Stmt
inline-small-func.c 20 0 x
inline-small-func.h:
inline-small-func.h 20 0 1 x
inline-small-func.c:
inline-small-func.c 23 0xa x
inline-small-func.c - 0x10
...
With gcc 8.2.1:
...
$ objdump -d inline-small-func.o
inline-small-func.o: file format elf64-x86-64
Disassembly of section .text:
0000000000000000 <main>:
0: c7 05 00 00 00 00 00 movl $0x0,0x0(%rip) # a <main+0xa>
7: 00 00 00
a: b8 00 00 00 00 mov $0x0,%eax
f: c3 ret
$ readelf -wL inline-small-func.o
Contents of the .debug_line section:
CU: inline-small-func.c:
File name Line number Starting address View Stmt
inline-small-func.c 20 0 x
inline-small-func.c 21 0 1 x
inline-small-func.h:
inline-small-func.h 19 0 2 x
inline-small-func.h 20 0 3 x
inline-small-func.h 20 0 4
inline-small-func.c:
inline-small-func.c 22 0xa x
inline-small-func.c 23 0xa 1
inline-small-func.c - 0x10
...
Same thing for aarch64, I've verified that using a cross compiler.
I think it's due to gcc commit 58006663903 ("[IEPM] Introduce inline entry
point markers").
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-26 10:58 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
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 [this message]
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-yySCYSXcg4@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).