On 12/15/23 04:53, Thomas Schwinge wrote:
Hi Jason!
I think you usually deal with these kind of GCC Git things? If not,
please let me know.
I just took care of this; I didn't notice it until now because the
subject line didn't seem relevant to me.
On 2023-10-26T10:21:18+0200, I wrote:
Fi
Hi Jason!
I think you usually deal with these kind of GCC Git things? If not,
please let me know.
On 2023-10-26T10:21:18+0200, I wrote:
> First, I've pushed into GCC upstream Git branch devel/rust/libgrust-v2
> the "v2" libgrust changes as posted by Arthur, so that people can easily
> test this
Hi!
Short Friday afternoon status update:
On 2023-10-27T08:51:12+0100, Iain Sandoe wrote:
>> On 26 Oct 2023, at 09:21, Thomas Schwinge wrote:
>> First, I've pushed into GCC upstream Git branch devel/rust/libgrust-v2
>> the "v2" libgrust changes as posted by Arthur, so that people can easily
>>
> On 26 Oct 2023, at 09:21, Thomas Schwinge wrote:
>
> Hi!
>
> First, I've pushed into GCC upstream Git branch devel/rust/libgrust-v2
> the "v2" libgrust changes as posted by Arthur, so that people can easily
> test this before it getting into Git master branch.
>
> I'll myself later try this
Hi!
First, I've pushed into GCC upstream Git branch devel/rust/libgrust-v2
the "v2" libgrust changes as posted by Arthur, so that people can easily
test this before it getting into Git master branch.
I'll myself later try this for GCN and nvptx targets -- in their current
form where they don't su
