public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/115066] [debug, gsplit-dwarf, gdwarf-4, g3] DW_MACRO_define_strp used for debug_str_offsets index
Date: Thu, 16 May 2024 08:35:49 +0000	[thread overview]
Message-ID: <bug-115066-4-x5UGp3eOux@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115066-4@http.gcc.gnu.org/bugzilla/>

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

Rainer Orth <ro at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2024-05-16
                 CC|                            |ro at gcc dot gnu.org
         Resolution|FIXED                       |---
             Status|RESOLVED                    |REOPENED

--- Comment #10 from Rainer Orth <ro at gcc dot gnu.org> ---
The new test currently FAILs on Solaris/SPARC with the native as:

FAIL: gcc.dg/pr115066.c scan-assembler \\\\.byte\\\\t0xb\\\\t# Define macro
strx

The relevant snippet of pr115066.s is

        .section        ".debug_macro.dwo",#exclude,#progbits
.LLdebug_macro0:
        .uahalf 0x4     ! DWARF macro version number
        .byte   0x2     ! Flags: 32-bit, lineptr present
        .uaword .LLskeleton_debug_line0
        .byte   0x1     ! Define macro

while when using gas, I have

        .section        .debug_macro.dwo,"e",@progbits
.LLdebug_macro0: 
        .uahalf 0x4     ! DWARF macro version number
        .byte   0x2     ! Flags: 32-bit, lineptr present
        .uaword .LLskeleton_debug_line0
        .byte   0xb     ! Define macro strx

AFAICS from dwarf2out.cc (output_macinfo_op), the requirements for using
DW_MACRO_define_strx are (among others)
!DWARF2_INDIRECT_STRING_SUPPORT_MISSING_ON_TARGET && SECTION_MERGE.

However, with the native assembler, SHF_MERGE doesn't work (as emits something
ld cannot link).

I wonder how best to handle this: just skip the test on sparc*-sun-solaris2* &&
!gas?  Theoretically, there could be other targets with similar issues.

  parent reply	other threads:[~2024-05-16  8:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13  8:40 [Bug debug/115066] New: " vries at gcc dot gnu.org
2024-05-13  8:42 ` [Bug debug/115066] " vries at gcc dot gnu.org
2024-05-13  9:12 ` vries at gcc dot gnu.org
2024-05-13 10:27 ` rguenth at gcc dot gnu.org
2024-05-13 10:29 ` vries at gcc dot gnu.org
2024-05-13 10:33 ` jakub at gcc dot gnu.org
2024-05-13 11:11 ` vries at gcc dot gnu.org
2024-05-14 11:35 ` vries at gcc dot gnu.org
2024-05-14 12:00 ` cvs-commit at gcc dot gnu.org
2024-05-14 12:04 ` vries at gcc dot gnu.org
2024-05-16  8:35 ` ro at gcc dot gnu.org [this message]
2024-05-16  9:06 ` vries at gcc dot gnu.org
2024-05-16  9:22 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-22  8:06 ` cvs-commit at gcc dot gnu.org
2024-05-27 14:02 ` clyon 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-115066-4-x5UGp3eOux@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).