GCC Copyright Assignment Forms for the RISC-V Port

Andrew and I maintain various GNU toolchain forks that contains a port to the RISC-V architecture . We're finishing up the binutils upstreaming process and would like to submit patches to GCC. When I signed the copyright assignment for binutils I was told that the GCC process wa

Re: RISC-V vector extension cauldron discussion

Sorry if this is a bit roundabout, I wrote this over a few days and ended up thinking a bunch while writing. As a result, the beginning might not match the end. On Sat, 08 Sep 2018 03:04:38 PDT (-0700), r...@twiddle.net wrote: This attempts to capture (most of) the two hour discussion that we

Re: RISC-V vector extension cauldron discussion

On Tue, 11 Sep 2018 14:34:24 PDT (-0700), r...@twiddle.net wrote: On 09/11/2018 09:28 AM, Palmer Dabbelt wrote: The RISC-V vector extension described something other than what is present in the currently released 2.2 standard.  To clarify the language within this message, based on what I

Re: Target maintainers: doc/install.texi love and care

On Sun, 12 Mar 2017 04:27:26 PDT (-0700), ger...@pfeifer.com wrote: > I noticed that the target-specific sections in doc/install.texi > need a little lover and care. It would be great could you have > a look and streamline/update before the GCC 7 release. I looked at our stuff (RISC-V) and there'

Re: Target maintainers: doc/install.texi love and care

On Mon, 13 Mar 2017 01:59:28 PDT (-0700), ger...@pfeifer.com wrote: > On Sun, 12 Mar 2017, Palmer Dabbelt wrote: >> I looked at our stuff (RISC-V) and there's almost nothing in there. >> Is there something I should add? I looked at the aarch64 stuff in the >> "ho

[PATCH] RISC-V documentation cleanups

A recent mailing list post about install.texi cleanup suggested I take a look at ours, and there were a few problems: * No table of contents entries * Not alphabetically ordered * Missing a note about requiring binutils-2.28 gcc/ChangeLog: 2017-03-13 Palmer Dabbelt : Add table of contents

Backporting Patches to GCC 7

I just submitted two patches against trunk. I'd like to also have them on the 7 branch, so when 7.2 comes out we'll have them. These patches only touch the RISC-V backend, which I'm a maintainer of. Is there a branch maintainer I'm supposed to have sign off on the patches or am I meant to just d

Re: Backporting Patches to GCC 7

On Tue, 09 May 2017 01:50:42 PDT (-0700), richard.guent...@gmail.com wrote: > On Mon, May 8, 2017 at 10:00 PM, Jonathan Wakely > wrote: >> On 5 May 2017 at 21:35, Palmer Dabbelt wrote: >>> I just submitted two patches against trunk. I'd like to also have them on >

Re: Backporting Patches to GCC 7

On Wed, 10 May 2017 01:35:11 PDT (-0700), richard.guent...@gmail.com wrote: > On Wed, May 10, 2017 at 2:31 AM, Palmer Dabbelt wrote: >> On Tue, 09 May 2017 01:50:42 PDT (-0700), richard.guent...@gmail.com wrote: >>> On Mon, May 8, 2017 at 10:00 PM, Jonathan Wakely >>>

[PATCH] RISC-V: Add Jim Wilson as a maintainer

er to have everyone use our proper email address. ChangeLog 2017-11-06 Palmer Dabbelt * MAINTAINERS (RISC-V): Add Jim Wilson as a maintainer. Use my SiFive email address. --- MAINTAINERS | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAI

Re: [PATCH] RISC-V: Add Jim Wilson as a maintainer

On Tue, 07 Nov 2017 05:02:13 PST (-0800), dje@gmail.com wrote: > On Tue, Nov 7, 2017 at 2:14 AM, Jakub Jelinek wrote: >> On Mon, Nov 06, 2017 at 06:39:20PM -0800, Palmer Dabbelt wrote: >>> Jim has recently started working at SiFive, where he'll be contributing >&

Re: [patches] Re: [PATCH] RISC-V: Add Jim Wilson as a maintainer

On Tue, 07 Nov 2017 09:47:37 PST (-0800), Jim Wilson wrote: > On Mon, Nov 6, 2017 at 6:39 PM, Palmer Dabbelt wrote: >> >> +riscv port Jim Wilson >> >> > It is jimw not jim for the email address. Please fix. Sorry. We're still

Re: [patches] Re: [PATCH] RISC-V: Add Jim Wilson as a maintainer

On Tue, 07 Nov 2017 09:53:12 PST (-0800), Palmer Dabbelt wrote: On Tue, 07 Nov 2017 09:47:37 PST (-0800), Jim Wilson wrote: On Mon, Nov 6, 2017 at 6:39 PM, Palmer Dabbelt wrote: +riscv port Jim Wilson It is jimw not jim for the email address. Please fix. Sorry

Re: RISC-V ELF multilibs

On Tue, 29 May 2018 11:02:58 PDT (-0700), Jim Wilson wrote: On 05/26/2018 06:04 AM, Sebastian Huber wrote: Why is the default multilib and a variant identical? This is supposed to be a single multilib, with two names. We use MULTILIB_REUSE to map the two names to a single multilib. rohan:103

RE: RISC-V ELF multilibs

On Thu, 31 May 2018 07:23:22 PDT (-0700), matthew.fort...@mips.com wrote: Palmer Dabbelt writes: On Tue, 29 May 2018 11:02:58 PDT (-0700), Jim Wilson wrote: > On 05/26/2018 06:04 AM, Sebastian Huber wrote: >> Why is the default multilib and a variant identical? > > This is s

Re: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (Jan 13, 2022)

On Wed, 12 Jan 2022 05:48:41 PST (-0800), jia...@iscas.ac.cn wrote: Hi all, There is an agenda for tomorrow's meeting. If you have topics to discuss or share, please let me know and I can add them to the agenda. We should also talk about the ABI spec, we've now got a handful of incompatibilit

Re: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (Aripl 07, 2022)

On Thu, Apr 7, 2022 at 4:16 AM jiawei wrote: > Yes, you are all right, now we are developing this under a temporary > stable dev-spec. There may a lot of changes go to it's forzen version. > Thanks for your remind anyway! > > Regards, > PLCT Jiawei > > > > *ISCAS* > 在 Philipp Tomsich ，2022年4月7日 下

RISC-V GCC Patchwork Sync-Up Meeting

The topic of having some sort of RISC-V development meeting has come up a handful of times, but we never got around to actually setting anything up. We've had a patchwork sync meeting for the RISC-V Linux port for a few months now and it's been super helpful, I figured it be best to just do so

GCC-13 Branch with RISC-V Performance-Related Backports

efer to make the branch sooner rather than later. Unless there's any objections, I'll push what's at github.com/palmer-dabbelt/gcc/gcc-13-perf as a vendor branch.

Re: RISC-V GCC Patchwork Sync-Up Meeting

On Mon, 17 Apr 2023 08:08:42 PDT (-0700), Palmer Dabbelt wrote: The topic of having some sort of RISC-V development meeting has come up a handful of times, but we never got around to actually setting anything up. We've had a patchwork sync meeting for the RISC-V Linux port for a few month

Re: GCC-13 Branch with RISC-V Performance-Related Backports

On Tue, 18 Apr 2023 06:19:07 PDT (-0700), jeffreya...@gmail.com wrote: On 4/18/23 04:34, Kito Cheng wrote: Based on some discussions, it looks like a handful of vendors are planning on maintaining GCC-13 branches that include various performance-related backports (ie, patches not suitable for

Re: GCC-13 Branch with RISC-V Performance-Related Backports

We talked about this a bit on IRC, but just to reflect it to the mailing lists: On Tue, 18 Apr 2023 05:34:11 PDT (-0700), s...@gentoo.org wrote: Palmer Dabbelt writes: Based on some discussions, it looks like a handful of vendors are planning on maintaining GCC-13 branches that include

Re: RISC-V GCC Patchwork Sync-Up Meeting

On Tue, 18 Apr 2023 08:34:34 PDT (-0700), Palmer Dabbelt wrote: On Mon, 17 Apr 2023 08:08:42 PDT (-0700), Palmer Dabbelt wrote: The topic of having some sort of RISC-V development meeting has come up a handful of times, but we never got around to actually setting anything up. We've

Re: [RFC] RISC-V: Go PLT for CALL/JUMP/RVC_JUMP if `h->plt.offset' isn't -1

On Sat, 08 Feb 2025 00:33:37 PST (-0800), Nelson Chu wrote: I got an request about the undefined behaviors, considering the following case, $ cat test.c void main () { foo(); } $ cat lib.h void foo(void); $ riscv64-unknown-linux-gnu-gcc test.c riscv64-unknown-linux-gnu/bin/ld: /tmp/ccRO8fJl.o: