public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: binutils@sourceware.org
Subject: Re: [Bug] DWARF-5 section names in PE/PEP and weak symbols
Date: Sat, 29 Jan 2022 08:57:39 +0100	[thread overview]
Message-ID: <87zgnf3rf0.fsf@Rainer.invalid> (raw)
In-Reply-To: <b51431d6-eaf3-552c-3ceb-e8ee3fe1540f@redhat.com> (Nick Clifton via Binutils's message of "Wed, 15 Dec 2021 13:12:32 +0000")

Nick Clifton via Binutils writes:
> Quick question - if instead of deleting the references to the .debug_loclists
> section you move them into the /DISCARD/ section earlier in the pe.se file,
> does this also solve the problem.  (The point being that if the script
> explitcitly discards this information we also have room to add a comment
> explaining why.  Plus it will prevent future changes to the pe.sc file
> from adding the section back in).  (Also the change would be needed in
> the pep.sc file as well, obviously.  Plus the .zdebug_loclists section
> would need similar treatment).

Just moving *(.debug_loclists) to the DISCARD section still results in
the erroneous resolution of the fputs symbol.  Also moving
*(.zdebug_loclists) recovers the correct behaviour.  I have no idea what
that means in terms of actual attempt at debugging, though.

--8<---------------cut here---------------start------------->8---
diff --git a/ld/scripttempl/pe.sc b/ld/scripttempl/pe.sc
index e9d1f78cb32..bbe3f341906 100644
--- a/ld/scripttempl/pe.sc
+++ b/ld/scripttempl/pe.sc
@@ -203,6 +203,8 @@ SECTIONS
     *(.debug\$S)
     *(.debug\$T)
     *(.debug\$F)
+    *(.debug_loclists)
+    *(.zdebug_loclists)
     *(.drectve)
     ${RELOCATING+ *(.note.GNU-stack)}
     ${RELOCATING+ *(.gnu.lto_*)}
@@ -447,6 +449,7 @@ SECTIONS
   {
     *(.zdebug_line_str)
   }
+/* ===
   .debug_loclists ${RELOCATING+BLOCK(__section_alignment__)} ${RELOCATING+(NOLOAD)} :
   {
     *(.debug_loclists)
@@ -455,6 +458,7 @@ SECTIONS
   {
     *(.zdebug_loclists)
   }
+=== */
   .debug_macro ${RELOCATING+BLOCK(__section_alignment__)} ${RELOCATING+(NOLOAD)} :
   {
     *(.debug_macro)
diff --git a/ld/scripttempl/pep.sc b/ld/scripttempl/pep.sc
index afa2d23871c..cd8a2defe4e 100644
--- a/ld/scripttempl/pep.sc
+++ b/ld/scripttempl/pep.sc
@@ -208,6 +208,8 @@ SECTIONS
     *(.debug\$S)
     *(.debug\$T)
     *(.debug\$F)
+    *(.debug_loclists)
+    *(.zdebug_loclists)
     *(.drectve)
     ${RELOCATING+ *(.note.GNU-stack)}
     ${RELOCATING+ *(.gnu.lto_*)}
@@ -452,6 +454,7 @@ SECTIONS
   {
     *(.zdebug_line_str)
   }
+/* ===
   .debug_loclists ${RELOCATING+BLOCK(__section_alignment__)} ${RELOCATING+(NOLOAD)} :
   {
     *(.debug_loclists)
@@ -460,6 +463,7 @@ SECTIONS
   {
     *(.zdebug_loclists)
   }
+=== */
   .debug_macro ${RELOCATING+BLOCK(__section_alignment__)} ${RELOCATING+(NOLOAD)} :
   {
     *(.debug_macro)
--8<---------------cut here---------------end--------------->8---


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  parent reply	other threads:[~2022-01-29  7:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 18:27 Achim Gratz
2021-12-15 13:12 ` Nick Clifton
2021-12-20 19:45   ` Achim Gratz
2022-01-23  8:10     ` Achim Gratz
2022-01-29  7:57   ` Achim Gratz [this message]
2022-02-13 20:17   ` Achim Gratz
2022-02-14 11:02     ` ASSI
2022-02-15 17:58       ` Achim Gratz
2022-02-15 19:08         ` Achim Gratz
2022-02-15 20:19         ` Achim Gratz

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=87zgnf3rf0.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=binutils@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).