public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91602] GCC fails to build for riscv in a combined tree due to misconfigured leb128 support
Date: Fri, 16 Jul 2021 08:24:50 +0000	[thread overview]
Message-ID: <bug-91602-4-R1pWwPFMlv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91602-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Note, on the DWARF side it has been agreed to get rid of the requirement that
uleb128/sleb128 has to be minimum possible length and I think all consumers
known  to me will not mind non-minimal leb128 as long as it isn't padded too
much (i.e. fits within 10 bytes or so).  So, even heavy relaxations in the
assembler and the linker shouldn't prevent leb128 support, all one needs for
linker relaxations is ULEB128 and SLEB128 relocation that allows subtraction of
two symbols.  But what do you do for non-LEB128 symbol subtractions?  Do you
have relocations for lab1 - lab2 if one has .quad lab1 - lab2 + 15 ?

  parent reply	other threads:[~2021-07-16  8:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-91602-4@http.gcc.gnu.org/bugzilla/>
2021-07-16  8:06 ` belyshev at depni dot sinp.msu.ru
2021-07-16  8:24 ` jakub at gcc dot gnu.org [this message]
2021-07-19 14:40 ` wilson at gcc dot gnu.org
2021-07-21 14:59 ` belyshev at depni dot sinp.msu.ru
2021-08-20 21:29 ` cvs-commit at gcc dot gnu.org
2021-08-20 21:34 ` belyshev at depni dot sinp.msu.ru

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-91602-4-R1pWwPFMlv@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).