public inbox for cygwin-cvs@sourceware.org help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@sourceware.org> To: cygwin-cvs@sourceware.org Subject: [newlib-cygwin] Cygwin: loader script: add DWARF 5 sections Date: Fri, 27 Aug 2021 12:34:06 +0000 (GMT) [thread overview] Message-ID: <20210827123406.E78023857C60@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=801120c1f402f9b0f72b5a231bf9e1cf82614cac commit 801120c1f402f9b0f72b5a231bf9e1cf82614cac Author: Corinna Vinschen <corinna@vinschen.de> Date: Fri Aug 27 14:26:42 2021 +0200 Cygwin: loader script: add DWARF 5 sections Modern gcc's generate additional DWARF 5 debug sections, which were still missing in our Cygwin loader script. With ld from binutils 2.37, this results in diagnostic output when linking the Cygwin DLL... ld: cygwin0.dll:/4: section below image base ld: cygwin0.dll:/20: section below image base ld: cygwin0.dll:/36: section below image base ...and the section addresses given to these sections (.debug_loclists, .debug_rnglists, debug_line_str) will be wrong. Fix this by adding the missing DWARF 5 sections to our linker script template cygwin.sc.in. Add a comment in terms of the deprecated DWARF 4 section .debug_types. Signed-off-by: Corinna Vinschen <corinna@vinschen.de> Signed-off-by: Jon Turney <jon.turney@dronecode.org.uk> Diff: --- winsup/cygwin/cygwin.sc.in | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/winsup/cygwin/cygwin.sc.in b/winsup/cygwin/cygwin.sc.in index 134ae3f76..293d2ab25 100644 --- a/winsup/cygwin/cygwin.sc.in +++ b/winsup/cygwin/cygwin.sc.in @@ -178,8 +178,13 @@ SECTIONS .debug_typenames ALIGN(__section_alignment__) (NOLOAD) : { *(.debug_typenames) } .debug_varnames ALIGN(__section_alignment__) (NOLOAD) : { *(.debug_varnames) } .debug_macro ALIGN(__section_alignment__) (NOLOAD) : { *(.debug_macro) } - /* DWARF 3. */ + /* DWARF 3 */ .debug_ranges ALIGN(__section_alignment__) (NOLOAD) : { *(.debug_ranges) } - /* DWARF 4. */ + /* DWARF 4, merged back into .debug_info with DWARF 5 */ .debug_types ALIGN(__section_alignment__) (NOLOAD) : { *(.debug_types .gnu.linkonce.wt.*) } + /* DWARF 5 */ + .debug_loclists ALIGN(__section_alignment__) (NOLOAD) : { *(.debug_loclists) } + .debug_rnglists ALIGN(__section_alignment__) (NOLOAD) : { *(.debug_rnglists) } + .debug_line_str ALIGN(__section_alignment__) (NOLOAD) : { *(.debug_line_str) } + }
reply other threads:[~2021-08-27 12:34 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210827123406.E78023857C60@sourceware.org \ --to=corinna@sourceware.org \ --cc=cygwin-cvs@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: linkBe 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).