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 symtab/28108] [gcc-11] FAIL: gdb.base/langs.exp: up to foo in langs.exp
Date: Tue, 20 Jul 2021 05:47:18 +0000	[thread overview]
Message-ID: <bug-28108-4717-kdkDBceO2x@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28108-4717@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
With -gdwarf-4, we have:
...
 <0><243>: Abbrev Number: 1 (DW_TAG_compile_unit)
    <244>   DW_AT_producer    : (indirect string, offset: 0x208): GNU C17
11.1.1 20210625 [revision 62bbb113ae68a7e724255e17143520735bcb9ec9]
-mtune=generic -march=x86-64 -gdwarf-4 -fno-stack-protector
    <248>   DW_AT_language    : 12      (ANSI C99)
    <249>   DW_AT_name        : (indirect string, offset: 0x34d):
/home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.base/langs2.c
    <24d>   DW_AT_comp_dir    : (indirect string, offset: 0x1d0):
/home/vries/gdb_versions/devel/build/gdb/testsuite
    <251>   DW_AT_low_pc      : 0x400502
    <259>   DW_AT_high_pc     : 0x3b
    <261>   DW_AT_stmt_list   : 0x20f
...
and at 0x20f:
...
 The Directory Table is empty.

 The File Name Table (offset 0x22c):
  Entry Dir     Time    Size    Name
  1     0       0       0       langs2.cxx

...

With -gdwarf-5, we have:
...
 <0><242>: Abbrev Number: 2 (DW_TAG_compile_unit)
    <243>   DW_AT_producer    : (indirect string, offset: 0x1d0): GNU C17
11.1.1 20210625 [revision 62bbb113ae68a7e724255e17143520735bcb9ec9]
-mtune=generic -march=x86-64 -gdwarf-5 -fno-stack-protector
    <247>   DW_AT_language    : 29      (C11)
    <248>   DW_AT_name        : (indirect line string, offset: 0xfc):
/home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.base/langs2.c
    <24c>   DW_AT_comp_dir    : (indirect line string, offset: 0x0):
/home/vries/gdb_versions/devel/build/gdb/testsuite
    <250>   DW_AT_low_pc      : 0x400502
    <258>   DW_AT_high_pc     : 0x3b
    <260>   DW_AT_stmt_list   : 0x1b4
...
and at 0x1b4:
...
 The Directory Table (offset 0x1d6, lines 1, columns 1):
  Entry Name
  0     (indirect line string, offset: 0x0):
/home/vries/gdb_versions/devel/build/gdb/testsuite

 The File Name Table (offset 0x1e0, lines 2, columns 2):
  Entry Dir     Name
  0     0       (indirect line string, offset: 0xfc):
/home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.base/langs2.c
  1     0       (indirect line string, offset: 0x13f): langs2.cxx
...

So the difference seems to be that the directory and file entries 0 are
implicit in dwarf-4, and explicit in dwarf-5.

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

  reply	other threads:[~2021-07-20  5:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20  5:18 [Bug symtab/28108] New: " vries at gcc dot gnu.org
2021-07-20  5:47 ` vries at gcc dot gnu.org [this message]
2021-07-20 11:03 ` [Bug symtab/28108] " vries at gcc dot gnu.org
2023-10-25 14:24 ` [Bug testsuite/28108] " 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-28108-4717-kdkDBceO2x@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).