public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/99090] gsplit-dwarf broken on riscv64-linux
Date: Fri, 26 Feb 2021 16:34:09 +0000	[thread overview]
Message-ID: <bug-99090-4-FWt70dglVe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99090-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jim Wilson <wilson at gcc dot gnu.org> ---
Yes we could have partial uleb128 support.  There is only a problem if at least
one label is in the code section.

There is another proposed solution to add special relaxable relocations for
uleb128 but the initial proposal had flaws, and no one has reviewed the second
proposal yet.

Or we could change the -gsplit-dwarf support to work even when there is no
uleb128 support.

  parent reply	other threads:[~2021-02-26 16:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-13 21:20 [Bug debug/99090] New: " wilson at gcc dot gnu.org
2021-02-26 11:59 ` [Bug debug/99090] " jakub at gcc dot gnu.org
2021-02-26 16:34 ` wilson at gcc dot gnu.org [this message]
2021-02-26 17:50 ` jakub at gcc dot gnu.org
2021-02-26 18:24 ` jakub at gcc dot gnu.org
2021-02-27  2:35 ` wilson at gcc dot gnu.org
2021-03-03  8:54 ` cvs-commit at gcc dot gnu.org
2021-03-03  8:58 ` jakub at gcc dot gnu.org
2021-08-20 21:34 ` belyshev at depni dot sinp.msu.ru
2021-09-11 18:48 ` pinskia at gcc dot gnu.org
2022-11-18 22:58 ` law at gcc dot gnu.org
2022-11-28 22:31 ` 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-99090-4-FWt70dglVe@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).