public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99488] dwz: /usr/lib/gcc/mips64el-linux-gnuabi64/11/go1: Found two copies of .debug_line_str section Date: Thu, 11 Mar 2021 15:55:09 +0000 [thread overview] Message-ID: <bug-99488-4-pz5H6b2Qwk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99488-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99488 --- Comment #3 from Mark Wielaard <mark at gcc dot gnu.org> --- So gcc/dwarf2out.c creates it as: #define DEBUG_STR_SECTION_FLAGS \ (HAVE_GAS_SHF_MERGE && flag_merge_debug_strings \ ? SECTION_DEBUG | SECTION_MERGE | SECTION_STRINGS | 1 \ : SECTION_DEBUG) debug_line_str_section = get_section (DEBUG_LINE_STR_SECTION, DEBUG_STR_SECTION_FLAGS, NULL); And gas/dwarf2dbg.c sets the flags as: bfd_set_section_flags (line_str_seg, SEC_READONLY | SEC_DEBUGGING | SEC_OCTETS | SEC_MERGE | SEC_STRINGS); I hope that results in the same section type/flags set. But you should probably check because MIPS has some special cases.
next prev parent reply other threads:[~2021-03-11 15:55 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-09 11:19 [Bug target/99488] New: " doko at debian dot org 2021-03-09 11:20 ` [Bug target/99488] " doko at debian dot org 2021-03-09 13:54 ` jakub at gcc dot gnu.org 2021-03-11 15:55 ` mark at gcc dot gnu.org [this message] 2021-03-11 16:00 ` jakub at gcc dot gnu.org 2021-03-15 11:51 ` doko at debian dot org 2021-03-15 11:53 ` doko at debian dot org 2021-03-15 12:21 ` jakub at gcc dot gnu.org 2021-03-15 12:37 ` mark at gcc dot gnu.org 2021-03-15 12:41 ` jakub at gcc dot gnu.org 2021-03-23 6:58 ` syq at debian dot org 2021-04-18 1:22 ` syq at debian dot org 2021-04-23 10:03 ` syq at debian dot org 2021-06-21 8:30 ` syq at debian dot org 2021-06-23 7:51 ` syq at debian dot org 2021-06-23 8:04 ` pinskia at gcc dot gnu.org 2021-06-23 8:29 ` jakub at gcc dot gnu.org 2021-06-24 2:41 ` syq at debian dot org 2021-06-24 2:43 ` syq at debian dot org 2021-06-24 8:11 ` syq at debian dot org 2021-06-24 8:15 ` syq at debian dot org 2021-06-24 8:17 ` pinskia 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-99488-4-pz5H6b2Qwk@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: 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).