On 9/15/21 8:31 AM, Martin Liška wrote:
On 9/14/21 09:56, Christophe LYON via Gcc-patches wrote:
So adjustment is needed for both arm and aarch64 targets
Hello.
I noticed the same problem and I've got a patch candidate for it.
What do you think about it?
I've now silenced the warning for i
On 9/14/21 09:56, Christophe LYON via Gcc-patches wrote:
So adjustment is needed for both arm and aarch64 targets
Hello.
I noticed the same problem and I've got a patch candidate for it.
What do you think about it?
MartinFrom 2ecedfe5cc421dd36f5770b04553343ecebd3430 Mon Sep 17 00:00:00 2001
F
On Wed, Sep 15, 2021 at 12:25 PM Richard Earnshaw via Gcc-patches <
gcc-patches@gcc.gnu.org> wrote:
>
>
> On 14/09/2021 08:56, Christophe LYON via Gcc-patches wrote:
> >
> > On 10/09/2021 15:16, Jason Merrill via Gcc-patches wrote:
> >> OK, time to finish this up. The main change relative to the
On 14/09/2021 08:56, Christophe LYON via Gcc-patches wrote:
On 10/09/2021 15:16, Jason Merrill via Gcc-patches wrote:
OK, time to finish this up. The main change relative to the last
patch I sent
to the list is dropping the -finterference-tune flag and making that
behavior
the default. A
On 10/09/2021 15:16, Jason Merrill via Gcc-patches wrote:
OK, time to finish this up. The main change relative to the last patch I sent
to the list is dropping the -finterference-tune flag and making that behavior
the default. Any more comments?
The last missing piece of the C++17 stan
OK, time to finish this up. The main change relative to the last patch I sent
to the list is dropping the -finterference-tune flag and making that behavior
the default. Any more comments?
The last missing piece of the C++17 standard library is the hardware
intereference size constants. Mu
