Re: [Linaro-TCWG-CI] gcc-15-168-g21e7aa5f3ea: FAIL: 6 regressions on aarch64

2024-05-28 Thread Christophe Lyon via Gcc-regression
Hi Harald, On Mon, 6 May 2024 at 21:02, wrote: > > Dear contributor, our automatic CI has detected problems related to your > patch(es). Please find some details below. If you have any questions, > please follow up on linaro-toolch...@lists.linaro.org mailing list, Libera's > #linaro-tcwg

[gcc r15-297] aarch64: Add aarch64-w64-mingw32 target to libatomic

2024-05-07 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:0c23efc04b754a1959f7151ef101ad0daba1e5af commit r15-297-g0c23efc04b754a1959f7151ef101ad0daba1e5af Author: Zac Walker Date: Fri Mar 1 02:23:45 2024 +0100 aarch64: Add aarch64-w64-mingw32 target to libatomic libatomic/ChangeLog: *

[gcc r15-298] Add aarch64-w64-mingw32 target to libgcc

2024-05-07 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:d6d7afcdbc04adb0ec42a44b2d7e05600945af42 commit r15-298-gd6d7afcdbc04adb0ec42a44b2d7e05600945af42 Author: Zac Walker Date: Mon Feb 12 15:22:47 2024 +0100 Add aarch64-w64-mingw32 target to libgcc Reuse MinGW definitions from i386 for libgcc. Move reused files

[gcc r15-296] aarch64: Build and add objects for Cygwin and MinGW for AArch64

2024-05-07 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:10a2f11b4101bdea84048ca90cd06e362f254c4c commit r15-296-g10a2f11b4101bdea84048ca90cd06e362f254c4c Author: Zac Walker Date: Tue Feb 20 13:55:51 2024 +0100 aarch64: Build and add objects for Cygwin and MinGW for AArch64 gcc/ChangeLog: *

[gcc r15-295] Rename "x86 Windows Options" to "Cygwin and MinGW Options"

2024-05-07 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:e8d003736e6c3ba9bddbd74bb07b5d91d3674b9f commit r15-295-ge8d003736e6c3ba9bddbd74bb07b5d91d3674b9f Author: Zac Walker Date: Thu Apr 11 13:43:23 2024 +0200 Rename "x86 Windows Options" to "Cygwin and MinGW Options" Rename "x86 Windows Options" to "Cygwin and

[gcc r15-293] aarch64: Add Cygwin and MinGW environments for AArch64

2024-05-07 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:565b782bfa85332a4aba91dec3b871d2f50f1fb8 commit r15-293-g565b782bfa85332a4aba91dec3b871d2f50f1fb8 Author: Zac Walker Date: Thu Apr 11 13:41:51 2024 +0200 aarch64: Add Cygwin and MinGW environments for AArch64 Define Cygwin and MinGW environment such as

[gcc r15-294] aarch64: Add SEH to machine_function

2024-05-07 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:38e422e2ef539ccf6db1bdd340079631b1141637 commit r15-294-g38e422e2ef539ccf6db1bdd340079631b1141637 Author: Zac Walker Date: Tue Feb 20 18:10:08 2024 +0100 aarch64: Add SEH to machine_function SEH is not enabled in aarch64-w64-mingw32 target yet. However, it

[gcc r15-292] Exclude i386 functionality from aarch64 build

2024-05-07 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:de2bcdaf399d3f97af6ab312893ffe089e69d42b commit r15-292-gde2bcdaf399d3f97af6ab312893ffe089e69d42b Author: Zac Walker Date: Thu Apr 11 13:38:59 2024 +0200 Exclude i386 functionality from aarch64 build This patch defines TARGET_AARCH64_MS_ABI in config.gcc and

[gcc r15-291] Rename section and encoding functions from i386 which will be used in aarch64

2024-05-07 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:99d7d5ec8d88415a7e1f74fade0841a0ebbd0092 commit r15-291-g99d7d5ec8d88415a7e1f74fade0841a0ebbd0092 Author: Zac Walker Date: Tue Feb 20 17:22:31 2024 +0100 Rename section and encoding functions from i386 which will be used in aarch64 gcc/ChangeLog:

[gcc r15-290] Reuse MinGW from i386 for AArch64

2024-05-07 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:1f05dfc131c7996a85dd82b3300f7b5f93d4b1bd commit r15-290-g1f05dfc131c7996a85dd82b3300f7b5f93d4b1bd Author: Zac Walker Date: Fri Mar 1 02:41:50 2024 +0100 Reuse MinGW from i386 for AArch64 This patch creates a new config/mingw directory to share MinGW

[gcc r15-289] aarch64: Add aarch64-w64-mingw32 COFF

2024-05-07 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:21fbaa1a2d274a36454332a6e10a496024bbc560 commit r15-289-g21fbaa1a2d274a36454332a6e10a496024bbc560 Author: Zac Walker Date: Thu Apr 11 14:46:07 2024 +0200 aarch64: Add aarch64-w64-mingw32 COFF Define ASM specific for COFF format on AArch64.

[gcc r15-288] aarch64: Mark x18 register as a fixed register for MS ABI

2024-05-07 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:b9415046fa27d6b3faea89871dbb84b673afadaf commit r15-288-gb9415046fa27d6b3faea89871dbb84b673afadaf Author: Zac Walker Date: Thu Apr 11 13:30:27 2024 +0200 aarch64: Mark x18 register as a fixed register for MS ABI Define the MS ABI for aarch64-w64-mingw32.

[gcc r15-287] Introduce aarch64-w64-mingw32 target

2024-05-07 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:13bad1ac7a6ea4dbbde67c69d31c218a2f2d7a5d commit r15-287-g13bad1ac7a6ea4dbbde67c69d31c218a2f2d7a5d Author: Zac Walker Date: Fri Mar 1 01:40:53 2024 +0100 Introduce aarch64-w64-mingw32 target Add the initial aarch64-w64-mingw32 target for gcc. This is

Re: Updated Sourceware infrastructure plans

2024-04-18 Thread Christophe Lyon via Gcc
Hi, On Thu, 18 Apr 2024 at 10:15, FX Coudert wrote: > > > I regenerate auto* files from time to time for libgfortran. Regenerating > > them has always been very fragile (using --enable-maintainer-mode), > > and difficult to get right. > > I have never found them difficult to regenerate, but if

[gcc r14-10006] libcpp: Regenerate aclocal.m4 and configure [PR 114748]

2024-04-17 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:a9fefbf71726bb0ce89c79e547ab3319af3227a8 commit r14-10006-ga9fefbf71726bb0ce89c79e547ab3319af3227a8 Author: Christophe Lyon Date: Wed Apr 17 13:56:19 2024 + libcpp: Regenerate aclocal.m4 and configure [PR 114748] As discussed in the PR, aclocal.m4 and

[gcc r14-9865] rust: Add rust.install-dvi and rust.install-html rules

2024-04-09 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:73fb0a6153f4781587c925c56683b61632e63dee commit r14-9865-g73fb0a6153f4781587c925c56683b61632e63dee Author: Christophe Lyon Date: Thu Apr 4 16:21:46 2024 + rust: Add rust.install-dvi and rust.install-html rules rust has the (empty) rust.dvi and rust.html

Re: [RFC] add regenerate Makefile target

2024-04-08 Thread Christophe Lyon via Gcc
Hi, On Mon, 25 Mar 2024 at 15:19, Christophe Lyon wrote: > > On Thu, 21 Mar 2024 at 15:32, Christophe Lyon > wrote: > > > > On Wed, 20 Mar 2024 at 16:34, Simon Marchi wrote: > > > > > > On 3/18/24 13:25, Christophe Lyon wrote: > > > > Well the rule to regenerate Makefile.in (eg in in opcodes/)

[gcc r14-9807] modula2: Add m2.install-dvi in gcc/m2/Make-lang.in

2024-04-05 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:6f1005649ff5f544eefba29ba4fb121dba0c6683 commit r14-9807-g6f1005649ff5f544eefba29ba4fb121dba0c6683 Author: Christophe Lyon Date: Thu Apr 4 16:15:12 2024 + modula2: Add m2.install-dvi in gcc/m2/Make-lang.in m2 has a m2.dvi build rule, but lacks the

Re: Patches submission policy change

2024-04-05 Thread Christophe Lyon via Gcc
On Thu, 4 Apr 2024 at 10:12, Jan Beulich wrote: > > On 03.04.2024 15:11, Christophe Lyon wrote: > > On Wed, 3 Apr 2024 at 10:30, Jan Beulich wrote: > >> > >> On 03.04.2024 10:22, Christophe Lyon wrote: > >>> Dear release managers and developers, > >>> > >>> TL;DR: For the sake of improving

Re: Patches submission policy change

2024-04-05 Thread Christophe Lyon via Gcc
Hi Mark, On 4/4/24 23:35, Mark Wielaard wrote: Hi Christophe, On Wed, Apr 03, 2024 at 10:22:24AM +0200, Christophe Lyon via Gdb wrote: TL;DR: For the sake of improving precommit CI coverage and simplifying workflows, I’d like to request a patch submission policy change, so that we now

[gcc r14-9800] go: Add go.install-dvi rule in go/Make-lang.in

2024-04-05 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:12b04452b40d49bb5322653cb5716b1ebf71b73d commit r14-9800-g12b04452b40d49bb5322653cb5716b1ebf71b73d Author: Christophe Lyon Date: Thu Apr 4 16:18:52 2024 + go: Add go.install-dvi rule in go/Make-lang.in go has a go.dvi build rule, but lacks the

Re: Patches submission policy change

2024-04-03 Thread Christophe Lyon via Gcc
On Wed, 3 Apr 2024 at 14:59, Joel Sherrill wrote: > > Another possible issue which may be better now than in years past > is that the versions of autoconf/automake required often had to be > installed by hand. I think newlib has gotten better but before the > rework on its Makefile/configure, I

Re: Patches submission policy change

2024-04-03 Thread Christophe Lyon via Gcc
On Wed, 3 Apr 2024 at 12:21, Jan Beulich wrote: > > On 03.04.2024 10:57, Richard Biener wrote: > > On Wed, 3 Apr 2024, Jan Beulich wrote: > >> On 03.04.2024 10:45, Jakub Jelinek wrote: > >>> On Wed, Apr 03, 2024 at 10:22:24AM +0200, Christophe Lyon wrote: > Any concerns/objections? > >>> >

Re: Patches submission policy change

2024-04-03 Thread Christophe Lyon via Gcc
On Wed, 3 Apr 2024 at 10:30, Jan Beulich wrote: > > On 03.04.2024 10:22, Christophe Lyon wrote: > > Dear release managers and developers, > > > > TL;DR: For the sake of improving precommit CI coverage and simplifying > > workflows, I’d like to request a patch submission policy change, so > > that

Patches submission policy change

2024-04-03 Thread Christophe Lyon via Gcc
Dear release managers and developers, TL;DR: For the sake of improving precommit CI coverage and simplifying workflows, I’d like to request a patch submission policy change, so that we now include regenerated files. This was discussed during the last GNU toolchain office hours meeting [1]

[gcc r14-9755] aarch64: Fix typo in comment about FEATURE_STRING

2024-04-02 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:d5aa2ca06aa7a6a2f826c4da19204b6db1402995 commit r14-9755-gd5aa2ca06aa7a6a2f826c4da19204b6db1402995 Author: Christophe Lyon Date: Fri Mar 29 14:25:05 2024 + aarch64: Fix typo in comment about FEATURE_STRING Fix the comment to document FEATURE_STRING

[gcc r14-9734] modula2: Fix m2.install-info in gcc/m2/Make-lang.in

2024-03-31 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:14d0c863aa9415f5d78047910233d67d91f4ecf5 commit r14-9734-g14d0c863aa9415f5d78047910233d67d91f4ecf5 Author: Christophe Lyon Date: Fri Mar 29 17:59:38 2024 + modula2: Fix m2.install-info in gcc/m2/Make-lang.in Fix a few typos: the generated filename is

[gcc r14-9733] modula2: Add m2.install-html rule to gcc/m2/Make-lang.in

2024-03-31 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:ec2c15f14f2278d431756f3d05e6ab7f436bea5e commit r14-9733-gec2c15f14f2278d431756f3d05e6ab7f436bea5e Author: Christophe Lyon Date: Fri Mar 29 17:10:36 2024 + modula2: Add m2.install-html rule to gcc/m2/Make-lang.in This rule was missing, and 'make

[gcc r14-9725] Fix lrcpc3 testcase

2024-03-29 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:28dca4be504dda29f55eafe958cdf299ec89b94e commit r14-9725-g28dca4be504dda29f55eafe958cdf299ec89b94e Author: Christophe Lyon Date: Fri Mar 29 14:19:59 2024 + Fix lrcpc3 testcase There was a typo in the testcase, with GCC_CPUINFO pointing to the wrong

Re: Building Single Tree for a Specific Set of CFLAGS

2024-03-28 Thread Christophe Lyon via Gcc
On 3/27/24 20:07, Joel Sherrill wrote: On Wed, Mar 27, 2024 at 3:53 AM Christophe Lyon via Gcc <mailto:gcc@gcc.gnu.org>> wrote: Hi! On 3/26/24 22:52, Joel Sherrill via Gcc wrote: > Hi > > For RTEMS, we normally build a multilib'ed gcc+newlib, but

Re: [RFC] add regenerate Makefile target

2024-03-27 Thread Christophe Lyon via Gcc
Hi! On Mon, 25 Mar 2024 at 15:19, Christophe Lyon wrote: > > On Thu, 21 Mar 2024 at 15:32, Christophe Lyon > wrote: > > > > On Wed, 20 Mar 2024 at 16:34, Simon Marchi wrote: > > > > > > On 3/18/24 13:25, Christophe Lyon wrote: > > > > Well the rule to regenerate Makefile.in (eg in in

Re: [RFC] add regenerate Makefile target

2024-03-27 Thread Christophe Lyon via Gcc
On Tue, 26 Mar 2024 at 16:42, Jens Remus wrote: > > Am 15.03.2024 um 09:50 schrieb Christophe Lyon: > > On Thu, 14 Mar 2024 at 19:10, Simon Marchi wrote: > >> On 2024-03-13 04:02, Christophe Lyon via Gdb wrote: > ... > >> There's just the issue of files that are generated using tools that are >

Re: Building Single Tree for a Specific Set of CFLAGS

2024-03-27 Thread Christophe Lyon via Gcc
Hi! On 3/26/24 22:52, Joel Sherrill via Gcc wrote: Hi For RTEMS, we normally build a multilib'ed gcc+newlib, but I have a case where the CPU model is something not covered by our multilibs and not one we are keen to add. I've looked around but not found anything that makes me feel confident.

Re: [RFC] add regenerate Makefile target

2024-03-25 Thread Christophe Lyon via Gcc
On Thu, 21 Mar 2024 at 15:32, Christophe Lyon wrote: > > On Wed, 20 Mar 2024 at 16:34, Simon Marchi wrote: > > > > On 3/18/24 13:25, Christophe Lyon wrote: > > > Well the rule to regenerate Makefile.in (eg in in opcodes/) is a bit > > > more complex > > > than just calling automake. IIUC it

Re: [RFC] add regenerate Makefile target

2024-03-21 Thread Christophe Lyon via Gcc
On Wed, 20 Mar 2024 at 16:34, Simon Marchi wrote: > > On 3/18/24 13:25, Christophe Lyon wrote: > > Well the rule to regenerate Makefile.in (eg in in opcodes/) is a bit > > more complex > > than just calling automake. IIUC it calls automake --foreign it any of > > *.m4 file from

Re: [RFC] add regenerate Makefile target

2024-03-19 Thread Christophe Lyon via Gcc
Hi, On Mon, 18 Mar 2024 at 18:25, Christophe Lyon wrote: > > On Sat, 16 Mar 2024 at 18:16, Simon Marchi wrote: > > > > > > > > On 2024-03-15 04:50, Christophe Lyon via Gdb wrote: > > > On Thu, 14 Mar 2024 at 19:10, Simon Marchi wrote: > > >> My first thought it: why is it a Makefile target,

[gcc r14-9537] arm: [MVE intrinsics] Fix support for loads [PR target/114323]

2024-03-19 Thread Christophe Lyon via Gcc-cvs
https://gcc.gnu.org/g:167ec6df7fd8deb67759acd5dbe72c1982a55873 commit r14-9537-g167ec6df7fd8deb67759acd5dbe72c1982a55873 Author: Christophe Lyon Date: Fri Mar 15 19:55:43 2024 + arm: [MVE intrinsics] Fix support for loads [PR target/114323] The testcase in this PR shows that

Re: [RFC] add regenerate Makefile target

2024-03-18 Thread Christophe Lyon via Gcc
On Fri, 15 Mar 2024 at 15:25, Tom Tromey wrote: > > > "Eric" == Eric Gallager writes: > > Eric> Also there are the files generated by cgen, too, which no one seems to > Eric> know how to regenerate, either. > > I thought I sent out some info on this a while ago. > > Anyway what I do is make

Re: [RFC] add regenerate Makefile target

2024-03-18 Thread Christophe Lyon via Gcc
On Sat, 16 Mar 2024 at 18:16, Simon Marchi wrote: > > > > On 2024-03-15 04:50, Christophe Lyon via Gdb wrote: > > On Thu, 14 Mar 2024 at 19:10, Simon Marchi wrote: > >> My first thought it: why is it a Makefile target, instead of some script > >> on the side (like autoregen.sh). It would be

Re: [RFC] add regenerate Makefile target

2024-03-18 Thread Christophe Lyon via Gcc
On Fri, 15 Mar 2024 at 15:13, Eric Gallager wrote: > > On Fri, Mar 15, 2024 at 4:53 AM Christophe Lyon via Gcc > wrote: > > > > On Thu, 14 Mar 2024 at 19:10, Simon Marchi wrote: > > > > > > > > > > > > On 2024-03-13 04:02, Christophe Lyo

Re: [RFC] add regenerate Makefile target

2024-03-15 Thread Christophe Lyon via Gcc
On Thu, 14 Mar 2024 at 19:10, Simon Marchi wrote: > > > > On 2024-03-13 04:02, Christophe Lyon via Gdb wrote: > > Hi! > > > > After recent discussions on IRC and on the lists about maintainer-mode > > and various problems with auto-generated source files, I've written > > this small prototype. >

[RFC] add regenerate Makefile target

2024-03-13 Thread Christophe Lyon via Gcc
Hi! After recent discussions on IRC and on the lists about maintainer-mode and various problems with auto-generated source files, I've written this small prototype. Based on those discussions, I assumed that people generally want to update autotools files using a script similar to autoregen.py,

Re: Help needed with maintainer-mode

2024-03-04 Thread Christophe Lyon via Gcc
On Mon, 4 Mar 2024 at 16:41, Richard Earnshaw wrote: > > > > On 04/03/2024 15:36, Richard Earnshaw (lists) wrote: > > On 04/03/2024 14:46, Christophe Lyon via Gcc wrote: > >> On Mon, 4 Mar 2024 at 12:25, Jonathan Wakely wrote: > >>> > >>> O

Re: Help needed with maintainer-mode

2024-03-04 Thread Christophe Lyon via Gcc
On Mon, 4 Mar 2024 at 12:25, Jonathan Wakely wrote: > > On Mon, 4 Mar 2024 at 10:44, Christophe Lyon via Gcc wrote: > > > > Hi! > > > > On Mon, 4 Mar 2024 at 10:36, Thomas Schwinge wrote: > > > > > > Hi! > > > > > > On 2024-03

Re: Help needed with maintainer-mode

2024-03-04 Thread Christophe Lyon via Gcc
Hi! On Mon, 4 Mar 2024 at 10:36, Thomas Schwinge wrote: > > Hi! > > On 2024-03-04T00:30:05+, Sam James wrote: > > Mark Wielaard writes: > >> On Fri, Mar 01, 2024 at 05:32:15PM +0100, Christophe Lyon wrote: > >>> [...], I read > >>> https://gcc.gnu.org/wiki/Regenerating_GCC_Configuration >

Re: Help needed with maintainer-mode

2024-03-01 Thread Christophe Lyon via Gcc
On Fri, 1 Mar 2024 at 14:08, Mark Wielaard wrote: > > Hi Christophe, > > On Thu, 2024-02-29 at 18:39 +0100, Christophe Lyon wrote: > > On Thu, 29 Feb 2024 at 12:00, Mark Wielaard wrote: > > > That python script works across gcc/binutils/gdb: > > >

Re: Help needed with maintainer-mode

2024-03-01 Thread Christophe Lyon via Gcc
On Fri, 1 Mar 2024 at 14:08, Mark Wielaard wrote: > > Hi Christophe, > > On Thu, 2024-02-29 at 18:39 +0100, Christophe Lyon wrote: > > On Thu, 29 Feb 2024 at 12:00, Mark Wielaard wrote: > > > That python script works across gcc/binutils/gdb: > > >

Re: Help needed with maintainer-mode

2024-03-01 Thread Christophe Lyon via Gcc
On Thu, 29 Feb 2024 at 20:49, Thiago Jung Bauermann wrote: > > > Hello, > > Christophe Lyon writes: > > > I hoped improving this would be as simple as adding > > --enable-maintainer-mode when configuring, after making sure > > autoconf-2.69 and automake-1.15.1 were in the PATH (using our host's

Re: Help needed with maintainer-mode

2024-02-29 Thread Christophe Lyon via Gcc
On Thu, 29 Feb 2024 at 12:00, Mark Wielaard wrote: > > Hi Christophe, > > On Thu, Feb 29, 2024 at 11:22:33AM +0100, Christophe Lyon via Gcc wrote: > > I've noticed that sourceware's buildbot has a small script > > "autoregen.py" which does not use the project's

Re: Help needed with maintainer-mode

2024-02-29 Thread Christophe Lyon via Gcc
On Thu, 29 Feb 2024 at 11:41, Richard Earnshaw (lists) wrote: > > On 29/02/2024 10:22, Christophe Lyon via Gcc wrote: > > Hi! > > > > Sorry for cross-posting, but I'm not sure the rules/guidelines are the > > same in gcc vs binutils/gdb. > > > > TL;DR:

Help needed with maintainer-mode

2024-02-29 Thread Christophe Lyon via Gcc
Hi! Sorry for cross-posting, but I'm not sure the rules/guidelines are the same in gcc vs binutils/gdb. TL;DR: are there some guidelines about how to use/enable maintainer-mode? In the context of the Linaro CI, I've been looking at enabling maintainer-mode at configure time in our

Re: Checks that autotools generated files were re-generated correctly

2023-11-07 Thread Christophe Lyon via Gcc
On Tue, 7 Nov 2023 at 15:36, Martin Jambor wrote: > > Hello, > > On Tue, Nov 07 2023, Maxim Kuvyrkov wrote: > n>> On Nov 6, 2023, at 21:19, Christophe Lyon > wrote: > >> > >> Hi! > >> > >> On Mon, 6 Nov 2023 at 18:05, Martin Jambor wrote: > >>> > >>> Hello, > >>> > >>> I have inherited Martin

Re: Checks that autotools generated files were re-generated correctly

2023-11-06 Thread Christophe Lyon via Gcc
Hi! On Mon, 6 Nov 2023 at 18:05, Martin Jambor wrote: > > Hello, > > I have inherited Martin Liška's buildbot script that checks that all > sorts of autotools generated files, mainly configure scripts, were > re-generated correctly when appropriate. While the checks are hopefully > useful, they

Re: [PATCH] testsuite: Fix gcc.target/arm/mve/mve_vadcq_vsbcq_fpscr_overwrite.c

2023-09-14 Thread Christophe Lyon via Gcc-patches
ping? On Fri, 8 Sept 2023 at 10:43, Christophe Lyon wrote: > The test was declaring 'int *carry;' and wrote to '*carry' without > initializing 'carry' first, leading to an attempt to write at address > zero, and a crash. > > Fix by declaring 'int carry;' and passing '' instead of 'carry' > as

Re: [PATCH] libstdc++: Remove some more unconditional uses of atomics

2023-09-14 Thread Christophe Lyon via Gcc-patches
On Thu, 14 Sept 2023 at 11:06, Jonathan Wakely wrote: > On Thu, 14 Sept 2023 at 09:41, Christophe Lyon > wrote: > > > > > > > > On Thu, 14 Sept 2023 at 10:17, Jonathan Wakely > wrote: > >> > >> On Thu, 14 Sept 2023 at 08:44, Christophe Lyon > >> wrote: > >> > > >> > Hi, > >> > > >> > > >> >

[PATCH v2 2/2] libstdc++: Add dg-require-thread-fence in several tests

2023-09-14 Thread Christophe Lyon via Gcc-patches
Some targets like arm-eabi with newlib and default settings rely on __sync_synchronize() to ensure synchronization. Newlib does not implement it by default, to make users aware they have to take special care. This makes a few tests fail to link. This patch requires the missing thread-fence

Re: [PATCH] libstdc++: Remove some more unconditional uses of atomics

2023-09-14 Thread Christophe Lyon via Gcc-patches
On Thu, 14 Sept 2023 at 10:17, Jonathan Wakely wrote: > On Thu, 14 Sept 2023 at 08:44, Christophe Lyon > wrote: > > > > Hi, > > > > > > On Wed, 13 Sept 2023 at 14:32, Jonathan Wakely > wrote: > >> > >> Tested x86_64-linux and aarch64-linux. I intend to push this to trunk. > >> > >> -- >8 -- >

Re: [PATCH] libstdc++: Remove some more unconditional uses of atomics

2023-09-14 Thread Christophe Lyon via Gcc-patches
Hi, On Wed, 13 Sept 2023 at 14:32, Jonathan Wakely wrote: > Tested x86_64-linux and aarch64-linux. I intend to push this to trunk. > > -- >8 -- > > These atomics cause linker errors on arm4t where __sync_synchronize is > not defined. For single-threaded targets we don't need the atomics. > > I

Re: [PATCH 2/2] libstdc++: Add dg-require-thread-fence in several tests

2023-09-13 Thread Christophe Lyon via Gcc-patches
On Tue, 12 Sept 2023 at 11:07, Jonathan Wakely wrote: > On Tue, 12 Sept 2023 at 08:59, Christophe Lyon > wrote: > > > > > > > > On Mon, 11 Sept 2023 at 18:11, Jonathan Wakely > wrote: > >> > >> On Mon, 11 Sept 2023 at 16:40, Christophe Lyon > >> wrote: > >> > > >> > > >> > > >> > On Mon, 11

Re: [PATCH] Tweak language choice in config-list.mk

2023-09-13 Thread Christophe Lyon via Gcc-patches
Hi! On Thu, 7 Sept 2023 at 11:30, Richard Sandiford via Gcc-patches < gcc-patches@gcc.gnu.org> wrote: > When I tried to use config-list.mk, the build for every triple except > the build machine's failed for m2. This is because, unlike other > languages, m2 builds target objects during all-gcc.

Re: [PATCH 2/2] libstdc++: Add dg-require-thread-fence in several tests

2023-09-12 Thread Christophe Lyon via Gcc-patches
On Mon, 11 Sept 2023 at 18:11, Jonathan Wakely wrote: > On Mon, 11 Sept 2023 at 16:40, Christophe Lyon > wrote: > > > > > > > > On Mon, 11 Sept 2023 at 17:22, Jonathan Wakely > wrote: > >> > >> On Mon, 11 Sept 2023 at 14:57, Christophe Lyon > >> wrote: > >> > > >> > > >> > > >> > On Mon, 11

Re: [PATCH 2/2] libstdc++: Add dg-require-thread-fence in several tests

2023-09-11 Thread Christophe Lyon via Gcc-patches
On Mon, 11 Sept 2023 at 17:22, Jonathan Wakely wrote: > On Mon, 11 Sept 2023 at 14:57, Christophe Lyon > wrote: > > > > > > > > On Mon, 11 Sept 2023 at 15:12, Jonathan Wakely > wrote: > >> > >> On Mon, 11 Sept 2023 at 13:36, Christophe Lyon > >> wrote: > >> > > >> > > >> > > >> > On Mon, 11

Re: [PATCH] analyzer: Move gcc.dg/analyzer tests to c-c++-common (2) [PR96395]

2023-09-11 Thread Christophe Lyon via Gcc-patches
Hi! On Wed, 6 Sept 2023 at 22:22, David Malcolm via Gcc-patches < gcc-patches@gcc.gnu.org> wrote: > On Wed, 2023-09-06 at 15:50 +0200, Benjamin Priour wrote: > > Hi David, > > Thanks for the review. > > > > > > > > On Tue, Sep 5, 2023 at 1:53 PM David Malcolm > > wrote: > > > > > On Mon,

Re: [PATCH 2/2] libstdc++: Add dg-require-thread-fence in several tests

2023-09-11 Thread Christophe Lyon via Gcc-patches
On Mon, 11 Sept 2023 at 15:12, Jonathan Wakely wrote: > On Mon, 11 Sept 2023 at 13:36, Christophe Lyon > wrote: > > > > > > > > On Mon, 11 Sept 2023 at 12:59, Jonathan Wakely > wrote: > >> > >> On Sun, 10 Sept 2023 at 20:31, Christophe Lyon > >> wrote: > >> > > >> > Some targets like arm-eabi

Re: [PATCH 2/2] libstdc++: Add dg-require-thread-fence in several tests

2023-09-11 Thread Christophe Lyon via Gcc-patches
On Mon, 11 Sept 2023 at 12:59, Jonathan Wakely wrote: > On Sun, 10 Sept 2023 at 20:31, Christophe Lyon > wrote: > > > > Some targets like arm-eabi with newlib and default settings rely on > > __sync_synchronize() to ensure synchronization. Newlib does not > > implement it by default, to make

[PATCH 2/2] libstdc++: Add dg-require-thread-fence in several tests

2023-09-10 Thread Christophe Lyon via Gcc-patches
Some targets like arm-eabi with newlib and default settings rely on __sync_synchronize() to ensure synchronization. Newlib does not implement it by default, to make users aware they have to take special care. This makes a few tests fail to link. This patch requires the missing thread-fence

[PATCH 1/2] testsuite: Add and use thread_fence effective-target

2023-09-10 Thread Christophe Lyon via Gcc-patches
Some targets like arm-eabi with newlib and default settings rely on __sync_synchronize() to ensure synchronization. Newlib does not implement it by default, to make users aware they have to take special care. This makes a few tests fail to link. This patch adds a new thread_fence effective

[PATCH] testsuite: Fix gcc.target/arm/mve/mve_vadcq_vsbcq_fpscr_overwrite.c

2023-09-08 Thread Christophe Lyon via Gcc-patches
The test was declaring 'int *carry;' and wrote to '*carry' without initializing 'carry' first, leading to an attempt to write at address zero, and a crash. Fix by declaring 'int carry;' and passing '' instead of 'carry' as parameter. 2023-09-08 Christophe Lyon gcc/testsuite/

Re: [Patch] contrib/gcc-changelog: Check whether revert-commit exists

2023-09-08 Thread Christophe Lyon via Gcc-patches
On Thu, 7 Sept 2023 at 11:45, Jakub Jelinek wrote: > On Thu, Sep 07, 2023 at 10:20:19AM +0200, Christophe Lyon via Gcc-patches > wrote: > > On Tue, 5 Sept 2023 at 16:38, Tobias Burnus > wrote: > > > > > That's based on the fail > > > https://gcc.gnu.or

Re: [Patch] contrib/gcc-changelog: Check whether revert-commit exists

2023-09-07 Thread Christophe Lyon via Gcc-patches
Hi! On Tue, 5 Sept 2023 at 16:38, Tobias Burnus wrote: > That's based on the fail > https://gcc.gnu.org/pipermail/gccadmin/2023q3/020349.html > and on the discussion on IRC. > Sorry I didn't notice the problem, nor the discussion on IRC, but I can see that my commits created the problem, sorry

[PATCH] testsuite: Remove unwanted 'dg-do run' from gcc.dg/vect tests

2023-09-04 Thread Christophe Lyon via Gcc-patches
Tests under gcc.dg/vect use check_vect_support_and_set_flags to set compilation flags as appropriate for the target, but they also set dg-do-what-default to 'run' or 'compile', depending on the actual target hardware (or simulator) capabilities. For instance on arm, we use options to enable Neon,

Re: [PATCH] analyzer: Add support of placement new and improved operator new [PR105948,PR94355]

2023-09-04 Thread Christophe Lyon via Gcc-patches
Hi Benjanmin, On Fri, 1 Sept 2023 at 17:45, David Malcolm via Gcc-patches < gcc-patches@gcc.gnu.org> wrote: > On Fri, 2023-09-01 at 16:48 +0200, Benjamin Priour wrote: > > Patch has been updated as per your suggestions and successfully > > regstrapped > > on x86_64-linux-gnu. > > The new

Re: [PATCH] libstdc++: Use GLIBCXX_CHECK_LINKER_FEATURES for cross-builds (PR111238)

2023-09-01 Thread Christophe Lyon via Gcc-patches
On Thu, 31 Aug 2023 at 21:43, Jonathan Wakely wrote: > On Thu, 31 Aug 2023 at 18:42, Jonathan Wakely wrote: > > > > On Thu, 31 Aug 2023 at 16:26, Christophe Lyon > > wrote: > > > > > > As discussed in PR104167 (comments #8 and below), and PR111238, using > > > -Wl,-gc-sections in the libstdc++

[PATCH] libstdc++: Use GLIBCXX_CHECK_LINKER_FEATURES for cross-builds (PR111238)

2023-08-31 Thread Christophe Lyon via Gcc-patches
As discussed in PR104167 (comments #8 and below), and PR111238, using -Wl,-gc-sections in the libstdc++ testsuite for arm-eabi (cross-toolchain) avoids link failures for a few tests: 27_io/filesystem/path/108636.cc std/time/clock/gps/1.cc std/time/clock/gps/io.cc std/time/clock/tai/1.cc

Re: [PATCH 5/9] arm: [MVE intrinsics] add support for p8 and p16 polynomial types

2023-08-29 Thread Christophe Lyon via Gcc-patches
On Tue, 29 Aug 2023 at 08:06, Prathamesh Kulkarni < prathamesh.kulka...@linaro.org> wrote: > On Tue, 15 Aug 2023 at 00:05, Christophe Lyon via Gcc-patches > wrote: > > > > Although they look like aliases for u8 and u16, we need to define them > > so that we

[PATCH 9/9] arm: [MVE intrinsics] rework vmullbq_poly vmulltq_poly

2023-08-14 Thread Christophe Lyon via Gcc-patches
Implement vmull[bt]q_poly using the new MVE builtins framework. 2023-08-14 Christophe Lyon gcc/ * config/arm/arm-mve-builtins-base.cc (vmullbq_poly) (vmulltq_poly): New. * config/arm/arm-mve-builtins-base.def (vmullbq_poly) (vmulltq_poly): New.

[PATCH 4/9] arm: [MVE intrinsics] rework vmullbq_int vmulltq_int

2023-08-14 Thread Christophe Lyon via Gcc-patches
Implement vmullbq_int, vmulltq_int using the new MVE builtins framework. 2023-08-14 Christophe Lyon gcc/ * config/arm/arm-mve-builtins-base.cc (vmullbq_int, vmulltq_int): New. * config/arm/arm-mve-builtins-base.def (vmullbq_int, vmulltq_int): New.

[PATCH 8/9] arm: [MVE intrinsics] add unspec_mve_function_exact_insn_vmull_poly

2023-08-14 Thread Christophe Lyon via Gcc-patches
Introduce a function that will be used to build vmull[bt]q_poly intrinsics that use poly types. 2023-08-14 Christophe Lyon gcc/ * config/arm/arm-mve-builtins-functions.h (class unspec_mve_function_exact_insn_vmull_poly): New. ---

[PATCH 7/9] arm: [MVE intrinsics] add binary_widen_poly shape

2023-08-14 Thread Christophe Lyon via Gcc-patches
This patch adds the binary_widen_poly shape description. 2023-08-14 Christophe Lyon gcc/ * config/arm/arm-mve-builtins-shapes.cc (binary_widen_poly): New. * config/arm/arm-mve-builtins-shapes.h (binary_widen_poly): New. --- gcc/config/arm/arm-mve-builtins-shapes.cc |

[PATCH 3/9] arm: [MVE intrinsics] add binary_widen shape

2023-08-14 Thread Christophe Lyon via Gcc-patches
This patch adds the binary_widen shape description. 2023-08-14 Christophe Lyon gcc/: * config/arm/arm-mve-builtins-shapes.cc (binary_widen): New. * config/arm/arm-mve-builtins-shapes.h (binary_widen): New. --- gcc/config/arm/arm-mve-builtins-shapes.cc | 42

[PATCH 6/9] arm: [MVE intrinsics] add support for U and p formats in parse_element_type

2023-08-14 Thread Christophe Lyon via Gcc-patches
Introduce these two format specifiers to define the shape of vmull[bt]q_poly intrinsics. 'U' is used to define a double-width unsigned 'p' is used to define an element of 'poly' type. 2023-08-14 Christophe Lyon gcc/ * config/arm/arm-mve-builtins-shapes.cc

[PATCH 5/9] arm: [MVE intrinsics] add support for p8 and p16 polynomial types

2023-08-14 Thread Christophe Lyon via Gcc-patches
Although they look like aliases for u8 and u16, we need to define them so that we can handle p8 and p16 suffixes with the general framework. They will be used by vmull[bt]q_poly intrinsics. 2023-08-14 Christophe Lyon gcc/ * config/arm/arm-mve-builtins.cc (type_suffixes):

[PATCH 2/9] arm: [MVE intrinsics] add unspec_mve_function_exact_insn_vmull

2023-08-14 Thread Christophe Lyon via Gcc-patches
Introduce a function that will be used to build vmull intrinsics with the _int variant. 2023-08-14 Christophe Lyon gcc/ * config/arm/arm-mve-builtins-functions.h (class unspec_mve_function_exact_insn_vmull): New. --- gcc/config/arm/arm-mve-builtins-functions.h | 74

[PATCH 1/9] arm: [MVE intrinsics] factorize vmullbq vmulltq

2023-08-14 Thread Christophe Lyon via Gcc-patches
Factorize vmullbq, vmulltq so that they use the same parameterized names. 2023-08-14 Christophe Lyon gcc/ * config/arm/iterators.md (mve_insn): Add vmullb, vmullt. (isu): Add VMULLBQ_INT_S, VMULLBQ_INT_U, VMULLTQ_INT_S, VMULLTQ_INT_U. (supf): Add

[PATCH] arm: [MVE intrinsics] Remove dead check for float type in parse_element_type

2023-08-14 Thread Christophe Lyon via Gcc-patches
Fix a likely copy/paste error, where we check if ch == 'f' after we checked it's either 's' or 'u'. 2023-08-14 Christophe Lyon gcc/ * config/arm/arm-mve-builtins-shapes.cc (parse_element_type): Remove dead check. --- gcc/config/arm/arm-mve-builtins-shapes.cc | 3 +--

[PATCH] arm: [MVE intrinsics] fix binary_acca_int32 and binary_acca_int64 shapes

2023-08-14 Thread Christophe Lyon via Gcc-patches
Fix these two shapes, where we were failing to check the last non-predicate parameter. 2023-08-14 Christophe Lyon gcc/ * config/arm/arm-mve-builtins-shapes.cc (binary_acca_int32): Fix loop bound. (binary_acca_int64): Likewise. ---

Re: [PATCH] ipa-sra: Don't consider CLOBBERS as writes preventing splitting

2023-08-11 Thread Christophe Lyon via Gcc-patches
On Fri, 11 Aug 2023 at 15:50, Martin Jambor wrote: > Hello, > > On Fri, Aug 11 2023, Christophe Lyon wrote: > > Hi Martin, > > > > > > On Fri, 4 Aug 2023 at 18:26, Martin Jambor wrote: > > > >> Hello, > >> > >> On Wed, Aug 02 2023, Richard Biener wrote: > >> > On Mon, Jul 31, 2023 at 7:05 PM

Re: [PATCH] ipa-sra: Don't consider CLOBBERS as writes preventing splitting

2023-08-11 Thread Christophe Lyon via Gcc-patches
Hi Martin, On Fri, 4 Aug 2023 at 18:26, Martin Jambor wrote: > Hello, > > On Wed, Aug 02 2023, Richard Biener wrote: > > On Mon, Jul 31, 2023 at 7:05 PM Martin Jambor wrote: > >> > >> Hi, > >> > >> when IPA-SRA detects whether a parameter passed by reference is > >> written to, it does not

Re: [PATCH] MATCH: [PR110937/PR100798] (a ? ~b : b) should be optimized to b ^ -(a)

2023-08-11 Thread Christophe Lyon via Gcc-patches
On Thu, 10 Aug 2023 at 20:52, Andrew Pinski wrote: > On Thu, Aug 10, 2023 at 6:39 AM Christophe Lyon via Gcc-patches > wrote: > > > > Hi Andrew, > > > > > > On Wed, 9 Aug 2023 at 21:20, Andrew Pinski via Gcc-patches < > > gcc-patches@gcc.gnu.o

Re: [PATCH] MATCH: [PR110937/PR100798] (a ? ~b : b) should be optimized to b ^ -(a)

2023-08-10 Thread Christophe Lyon via Gcc-patches
Hi Andrew, On Wed, 9 Aug 2023 at 21:20, Andrew Pinski via Gcc-patches < gcc-patches@gcc.gnu.org> wrote: > This adds a simple match pattern for this case. > I noticed it a couple of different places. > One while I was looking at code generation of a parser and > also while I was looking at

Re: [PATCH] testsuite: Fix gcc.dg/analyzer/allocation-size-multiline-[123].c [PR 110426]

2023-08-10 Thread Christophe Lyon via Gcc-patches
Hi! On Wed, 9 Aug 2023 at 22:30, David Malcolm wrote: > On Tue, 2023-08-08 at 15:01 +, Christophe Lyon wrote: > > For 32-bit newlib targets (e.g. arm-eabi) int32_t is "long int". > > > > Like previous patches in these tests, update the matching regexps to > > match "aka (long )?int". > > >

[PATCH] testsuite: Fix gcc.dg/analyzer/allocation-size-multiline-[123].c [PR 110426]

2023-08-08 Thread Christophe Lyon via Gcc-patches
For 32-bit newlib targets (e.g. arm-eabi) int32_t is "long int". Like previous patches in these tests, update the matching regexps to match "aka (long )?int". Tested on arm-eabi and aarch64-linux-gnu. 2023-08-08 Christophe Lyon gcc/testsuite/ PR analyzer/110426 *

Re: arm: Remove unsigned variant of vcaddq_m

2023-08-01 Thread Christophe Lyon via Gcc-patches
Hi Stam, On Tue, 1 Aug 2023 at 19:22, Stamatis Markianos-Wright via Gcc-patches < gcc-patches@gcc.gnu.org> wrote: > Hi all, > > The unsigned variants of the vcaddq_m operation are not needed within the > compiler, as the assembly output of the signed and unsigned versions of the > ops is

[PATCH][COMMITTED] doc: Fix spelling in arm_v8_1m_main_cde_mve_fp

2023-08-01 Thread Christophe Lyon via Gcc-patches
Fix spelling mistakes introduced by my previous patch in this area. Committed as obvious. 2023-08-01 Christophe Lyon gcc/ * doc/sourcebuild.texi (arm_v8_1m_main_cde_mve_fp): Fix spelling. --- gcc/doc/sourcebuild.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

[PATCH 2/6] arm: [MVE intrinsics] rework vcaddq vhcaddq

2023-07-13 Thread Christophe Lyon via Gcc-patches
Implement vcaddq, vhcaddq using the new MVE builtins framework. 2023-07-13 Christophe Lyon gcc/ * config/arm/arm-mve-builtins-base.cc (vcaddq_rot90) (vcaddq_rot270, vhcaddq_rot90, vhcaddq_rot270): New. * config/arm/arm-mve-builtins-base.def (vcaddq_rot90)

[PATCH 4/6] arm: [MVE intrinsics] rework vcmulq

2023-07-13 Thread Christophe Lyon via Gcc-patches
Implement vcmulq using the new MVE builtins framework. 2023-07-13 Christophe Lyon gcc/ * config/arm/arm-mve-builtins-base.cc (vcmulq, vcmulq_rot90) (vcmulq_rot180, vcmulq_rot270): New. * config/arm/arm-mve-builtins-base.def (vcmulq, vcmulq_rot90)

[PATCH 5/6] arm: [MVE intrinsics] factorize vcmlaq

2023-07-13 Thread Christophe Lyon via Gcc-patches
Factorize vcmlaq builtins so that they use parameterized names. 2023-17-13 Christophe Lyon gcc/ * config/arm/arm_mve_builtins.def (vcmlaq_rot90_f) (vcmlaq_rot270_f, vcmlaq_rot180_f, vcmlaq_f): Add "_f" suffix. * config/arm/iterators.md (MVE_VCMLAQ_M): New.

[PATCH 3/6] arm: [MVE intrinsics factorize vcmulq

2023-07-13 Thread Christophe Lyon via Gcc-patches
Factorize vcmulq builtins so that they use parameterized names. We can merged them with vcadd. 2023-07-13 Christophe Lyon gcc/: * config/arm/arm_mve_builtins.def (vcmulq_rot90_f) (vcmulq_rot270_f, vcmulq_rot180_f, vcmulq_f): Add "_f" suffix. *

[PATCH 1/6] arm: [MVE intrinsics] Factorize vcaddq vhcaddq

2023-07-13 Thread Christophe Lyon via Gcc-patches
Factorize vcaddq, vhcaddq so that they use the same parameterized names. To be able to use the same patterns, we add a suffix to vcaddq. Note that vcadd uses UNSPEC_VCADDxx for builtins without predication, and VCADDQ_ROTxx_M_x (that is, not starting with "UNSPEC_"). The UNPEC_* names are also

[PATCH 6/6] arm: [MVE intrinsics] rework vcmlaq

2023-07-13 Thread Christophe Lyon via Gcc-patches
Implement vcmlaq using the new MVE builtins framework. 2023-07-13 Christophe Lyon gcc/ * config/arm/arm-mve-builtins-base.cc (vcmlaq, vcmlaq_rot90) (vcmlaq_rot180, vcmlaq_rot270): New. * config/arm/arm-mve-builtins-base.def (vcmlaq, vcmlaq_rot90)

  1   2   3   4   5   6   7   8   9   10   >