https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
Serge Belyshev changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
--- Comment #16 from CVS Commits ---
The master branch has been updated by Sergey Belyshev :
https://gcc.gnu.org/g:7cad8a8f9f7bfa8e98f6a0615541f589fd1d3fc1
commit r12-3047-g7cad8a8f9f7bfa8e98f6a0615541f589fd1d3fc1
Author: Serge Belyshev
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
Serge Belyshev changed:
What|Removed |Added
Keywords||patch
--- Comment #15 from Serge
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
--- Comment #14 from Jim Wilson ---
I posted a patch but didn't get a review, and then got distracted by other
stuff and failed to follow up.
https://gcc.gnu.org/pipermail/gcc-patches/2020-January/539461.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
Serge Belyshev changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
--- Comment #11 from Jim Wilson ---
Since Marxin pinged this and got me thinking about this again, I realized that
there is a simpler fix based on Serge's second suggestion. We can just delete
the gas version number from the uleb128 gas check
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
--- Comment #10 from Jim Wilson ---
The proposed binutils patch has multiple problems and has gone through multiple
iterations. Not clear when or if we will be able to accept it.
The gcc configure patch to eliminate the call to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
Andrew Pinski changed:
What|Removed |Added
Keywords|easyhack|
--- Comment #8 from Andrew Pinski ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
--- Comment #7 from Serge Belyshev ---
(In reply to Jim Wilson from comment #5)
> When you build packages separately, each package after the first uses
> feature tests to configure itself appropriately to use the earlier packages.
> When you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
--- Comment #6 from Jim Wilson ---
By the way, the underlying problem here is, as Andrew Waterman mentioned, that
the RISC-V linker does aggressive link time relaxations to reduce code size,
and this makes lib128 with label subtraction unsafe.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
--- Comment #5 from Jim Wilson ---
The wiki is wrong. Combined tree builds should not be used anymore.
Combined tree builds date back to when Cygnus was maintainer for everything.
We put everything in a single source tree, and wrote configure
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
--- Comment #4 from Andrew Pinski ---
>Combined tree builds are obsolete and shouldn't be used anymore.)
Huh? Where is that documented. In fact the wiki still recommends a combined
build. Combined builds make building easier.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
Jim Wilson changed:
What|Removed |Added
CC||wilson at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
--- Comment #2 from Andrew Waterman ---
Yeah, this is a bit a rat hole. Of course there's nothing about
RISC-V that precludes the use of the leb128 data formats. We fib that
they aren't supported to prevent the DWARF emitters from subtracting
16 matches
Mail list logo
