public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at debian dot 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: Tue, 09 Mar 2021 11:20:38 +0000 [thread overview]
Message-ID: <bug-99488-4-ir9P4FPXN9@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
Matthias Klose <doko at debian dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |syq at debian dot org
Known to work| |10.2.1
Target| |mips64el-linux-gnu
Known to fail| |11.0
--- Comment #1 from Matthias Klose <doko at debian dot org> ---
<mjw> doko, odd, don't know how that happens, something must have missed
merging the sections together.
<mjw> doko, Since this is mips there might be some confusion about section
types/flags. I would look to see if those sections have different types/flags
and then try to work back who created which with those. e.g. both gas and gcc
can create a .debug_line_str section.
next prev parent reply other threads:[~2021-03-09 11:20 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 ` doko at debian dot org [this message]
2021-03-09 13:54 ` [Bug target/99488] " jakub at gcc dot gnu.org
2021-03-11 15:55 ` mark at gcc dot gnu.org
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-ir9P4FPXN9@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).