On 28/08/2020 15:26, Martin Liška wrote:
On 8/28/20 4:24 PM, Andrew Stubbs wrote:
Should I just add "true" to fix it? That's enough to make it build.
Yes, please and push it as obvious.
I've committed the attached.
Andrew
amdgcn: Update vec_safe_grow_cleared usage
An API change broke the
On 8/28/20 12:49 AM, Martin Liška wrote:
On 8/28/20 1:29 AM, Martin Sebor wrote:
With --enable-valgrind-annotations the change to the member function
signature in this patch triggers compilation errors during bootstrap:
I must confirm I didn't tested the configuration. Feel free to install
On 8/28/20 4:24 PM, Andrew Stubbs wrote:
Should I just add "true" to fix it? That's enough to make it build.
Yes, please and push it as obvious.
Thanks,
Martin
On 11/08/2020 12:36, Martin Liška wrote:
Hello.
All right, I did it in 3 steps:
1) - new exact argument is added (no default value) - I tested the on
x86_64-linux-gnu
and I build all cross targets.
2) set default value of exact = false
3) change places which calculate its own growth to use
On 8/28/20 1:29 AM, Martin Sebor wrote:
With --enable-valgrind-annotations the change to the member function
signature in this patch triggers compilation errors during bootstrap:
I must confirm I didn't tested the configuration. Feel free to install
the patch, it's obvious.
Thank you,
Martin
With --enable-valgrind-annotations the change to the member function
signature in this patch triggers compilation errors during bootstrap:
/src/gcc/trunk/gcc/ggc-common.c: In function ‘void gt_pch_save(FILE*)’:
/src/gcc/trunk/gcc/ggc-common.c:509:33: error: no matching function for
call to
On Tue, 2020-08-11 at 13:36 +0200, Martin Liška wrote:
> Hello.
>
> All right, I did it in 3 steps:
> 1) - new exact argument is added (no default value) - I tested the on
> x86_64-linux-gnu
> and I build all cross targets.
> 2) set default value of exact = false
> 3) change places which
On 8/12/20 2:28 PM, Martin Liška wrote:
I guess Richi can defend his strategy for this
Richi?
Martin
On 8/12/20 6:28 AM, Martin Liška wrote:
On 8/11/20 4:58 PM, Martin Sebor wrote:
On 8/11/20 5:36 AM, Martin Liška wrote:
Hello.
All right, I did it in 3 steps:
1) - new exact argument is added (no default value) - I tested the on
x86_64-linux-gnu
and I build all cross targets.
2) set default
On 8/11/20 4:58 PM, Martin Sebor wrote:
On 8/11/20 5:36 AM, Martin Liška wrote:
Hello.
All right, I did it in 3 steps:
1) - new exact argument is added (no default value) - I tested the on
x86_64-linux-gnu
and I build all cross targets.
2) set default value of exact = false
3) change places
On 8/11/20 5:36 AM, Martin Liška wrote:
Hello.
All right, I did it in 3 steps:
1) - new exact argument is added (no default value) - I tested the on
x86_64-linux-gnu
and I build all cross targets.
2) set default value of exact = false
3) change places which calculate its own growth to use the
first 1) and then wait some time before the rest is
installed.
Thoughts?
Martin
>From c659680bd65bdaa749d8c07fc99b45542a872786 Mon Sep 17 00:00:00 2001
From: Martin Liska
Date: Mon, 10 Aug 2020 11:11:05 +0200
Subject: [PATCH 1/3] vec: add exact argument for various grow functions.
gcc/
12 matches
Mail list logo
