Noticed trivial syntax errors in gcc/ada/expect.c when tried to compile gcc 13.2 as cross-compiler
for target i686-pc-msdosdjgpp.
Errors were there since
Tiedostossa, joka sisällytettiin kohdasta expect.c:54:
expect.c:Funktio ”__gnat_waitpid”:
expect.c:353:13:virhe: expected ”(” before numeric
On Thu, 17 Aug 2023 at 13:22, Jonathan Wakely via Libstdc++
wrote:
>
> Tested x86_64-linux. Pushed to trunk. Backport to gcc-13 will follow.
Re the backport, I forgot to say that this changes the order/values of
the enumerators for _Pres_type. In theory that could cause
incompatibilities between
On Fri, 18 Aug 2023 at 14:52, Richard Biener wrote:
>
> On Fri, 18 Aug 2023, Richard Sandiford wrote:
>
> > Richard Biener writes:
> > > The following avoids running into somehow flawed logic in fold_vec_perm
> > > for non-VLA vectors.
> > >
> > > Bootstrap & regtest running on x86_64-unknown-lin
(Pinging since I realised that this is required for my later Low Overhead Loop
patch series to work)
Ok for trunk with the updated changelog that Christophe mentioned?
Thanks,
Stamatis/Stam Markianos-Wright
From: Stam Markianos-Wright
Sent: Tuesday, August 1,
Thank you very much, I think this should also be backported to Gcc12/13.
Huacai
On Sat, Aug 19, 2023 at 11:59 AM Chenghua Xu wrote:
>
> Pushed as r14-3331.
>
> Thanks.
> chenglulu writes:
>
> > LGTM!
> >
> > 在 2023/8/16 上午9:48, Guo Jie 写道:
> >> gcc/ChangeLog:
> >>
> >> * config/loongarch/t-
On Fri, 18 Aug 2023 at 17:11, Richard Biener wrote:
>
> On Fri, 18 Aug 2023, Richard Biener wrote:
>
> > On Thu, 17 Aug 2023, Prathamesh Kulkarni wrote:
> >
> > > On Tue, 15 Aug 2023 at 14:28, Richard Sandiford
> > > wrote:
> > > >
> > > > Richard Biener writes:
> > > > > On Mon, 14 Aug 2023, Pr
Here is a rebased patch following the resize_and_overwrite change.
I confirm that tests are now fixed after the change in tzdb.cc.
I'll prepare a fix for those tests still but preparing also a test to
detect allocations in the lib.
François
On 17/08/2023 21:44, Jonathan Wakely wrote:
On Thu
On 8/17/23 12:59, Eric Gallager via Gcc-patches wrote:
Subject:
[PATCH] improve error when /usr/include isn't found [PR90835]
From:
Eric Gallager via Gcc-patches
Date:
8/17/23, 12:59
To:
gcc-patches@gcc.gnu.org
CC:
ia...@gcc.gnu.org, Eric Gallager
This is a pretty simple patch that ought
Bordering on obvious, tested on darwin where the test case fails before (and
now passes).
OK to commit?
FX
0001-Testsuite-fix-contructor-priority-test.patch
Description: Binary data
Hi,
gcc.dg/analyzer/ currently has 80 failures on Darwin (both x86_64-apple-darwin
and aarch64-apple-darwin). All those come from two issues:
1. Many tests use memset() without including the header. We can fix
that easily.
2. Other tests fail because of the use of macOS headers, which redefin
Hi FX,
thanks for chasing these fails down,
> On 19 Aug 2023, at 22:28, FX Coudert wrote:
>
> gcc.dg/analyzer/ currently has 80 failures on Darwin (both
> x86_64-apple-darwin and aarch64-apple-darwin). All those come from two issues:
>
> 1. Many tests use memset() without including the head
Hi,
With the proposed design of these switches, how would I restrict AVX10.1
to particular AVX-512 subsets?
For example, usage of the |_mm256_rol_epi32| intrinsic should be
compatible on any AVX10/256 implementation, /as well as /any AVX-512VL
without AVX10 implementation (e.g. Skylake-X).
Thanks, I committed the version with Iain's suggested change in wording:
https://gcc.gnu.org/pipermail/gcc-patches/2023-August/627796.html
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=9a5d1fceb86a61c9ead380df89ce3c4ba387d2e5
(sorry that this got sent multiple times; I thought the email hadn't
On Thu, Aug 17, 2023 at 11:38 PM Eric Gallager wrote:
>
> On Thu, Aug 17, 2023 at 4:05 PM Iain Sandoe wrote:
> >
> > Hi Eric,
> >
> > thanks for working on this.
> >
> > > On 17 Aug 2023, at 20:35, Eric Gallager wrote:
> > >
> > > This is a pretty simple patch that ought to help Darwin users und
> Am 20.08.2023 um 00:45 schrieb ZiNgA BuRgA via Gcc-patches
> :
>
> Hi,
>
> With the proposed design of these switches, how would I restrict AVX10.1 to
> particular AVX-512 subsets?
>
> For example, usage of the |_mm256_rol_epi32| intrinsic should be compatible
> on any AVX10/256 impleme
15 matches
Mail list logo