Re: Updated Sourceware infrastructure plans

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

Re: Generated files in libgfortran for Fortran intrinsic procedures (was: Updated Sourceware infrastructure plans)

Am Donnerstag, dem 18.04.2024 um 14:01 +0200 schrieb Tobias Burnus: > Hi Janne, > > Janne Blomqvist wrote: > > back when I was active I did think about this > > issue. IMHO the best of my ideas was to convert these into C++ > > templates. I haven't looked at libgfortran but I didn't find it

Re: Deprecation/removal of nios2 target support

On 4/18/24 7:53 AM, Thomas Huth wrote: On 18/04/2024 05.27, Sandra Loosemore wrote: Tomorrow I plan to push patches to mark the nios2 target as obsolete in GCC 14. Background: Intel has EOL'ed the Nios II processor IP and is now directing their FPGA customers to a RISC-V platform instead.

Re: Updated Sourceware infrastructure plans

On Thu, Apr 18, 2024 at 11:15 AM 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 you

Generated files in libgfortran for Fortran intrinsic procedures (was: Updated Sourceware infrastructure plans)

Hi Janne, Janne Blomqvist wrote: back when I was active I did think about this issue. IMHO the best of my ideas was to convert these into C++ templates. I think this will work – but we have to be super careful: With C++, there is the problem that we definitely do not want to add dependency

Re: Updated Sourceware infrastructure plans

On Thu, 18 Apr 2024, Frank Ch. Eigler via Gcc wrote: > Hi - > > > [...] I suggest that a basic principle for such a system is that it > > should be *easy* to obtain and maintain a local copy of the history > > of all pull requests. That includes all versions of a pull request, > > if it gets

Re: Updated Sourceware infrastructure plans

On Thu, 18 Apr 2024, Mark Wielaard wrote: > But we like to get more feedback on what people really think a > "pull-request" style framework should look like. We used to have a > gerrit setup which wasn't really popular. And we already have a > sourcehut mirror that can be used to turn your

Re: Deprecation/removal of nios2 target support

On Thu, Apr 18, 2024 at 10:46 AM Joseph Myers wrote: > On Wed, 17 Apr 2024, Sandra Loosemore wrote: > > > Therefore I'd like to mark Nios II as obsolete in GCC 14 now, and remove > > support from all toolchain components after the release is made. I'm > not sure > > there is an established

Re: Deprecation/removal of nios2 target support

On 4/18/24 9:57 AM, Joel Sherrill wrote: On Thu, Apr 18, 2024 at 10:46 AM Joseph Myers > wrote: On Wed, 17 Apr 2024, Sandra Loosemore wrote: > Therefore I'd like to mark Nios II as obsolete in GCC 14 now, and remove > support from all

Re: Deprecation/removal of nios2 target support

On Thu, Apr 18, 2024, at 17:44, Joseph Myers wrote: > On Wed, 17 Apr 2024, Sandra Loosemore wrote: > >> Therefore I'd like to mark Nios II as obsolete in GCC 14 now, and remove >> support from all toolchain components after the release is made. I'm not >> sure >> there is an established process

Re: Updated Sourceware infrastructure plans

On Thu, Apr 18, 2024 at 5:38 PM Frank Ch. Eigler wrote: > > Hi - > > > [...] I suggest that a basic principle for such a system is that it > > should be *easy* to obtain and maintain a local copy of the history > > of all pull requests. That includes all versions of a pull request, > > if it

Re: Deprecation/removal of nios2 target support

On 4/18/24 10:06, Jeff Law wrote: ACK.  Just one more note to the wider audience.  I looked at QEMU's user mode support for nios2 on/off over the last couple years.  It never seemed to work well enough be able to run the GCC testsuite reliably. I looked at the problems with the nios2

Re: Updated Sourceware infrastructure plans

Hi - > [...] I suggest that a basic principle for such a system is that it > should be *easy* to obtain and maintain a local copy of the history > of all pull requests. That includes all versions of a pull request, > if it gets rebased, and all versions of comments, if the system > allows

Re: Deprecation/removal of nios2 target support

On Wed, 17 Apr 2024, Sandra Loosemore wrote: > Therefore I'd like to mark Nios II as obsolete in GCC 14 now, and remove > support from all toolchain components after the release is made. I'm not sure > there is an established process for obsoleting/removing support in other > components; besides

Youl

Sent from my iPhone

gcc-11-20240418 is now available

Snapshot gcc-11-20240418 is now available on https://gcc.gnu.org/pub/gcc/snapshots/11-20240418/ and on various mirrors, see https://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 11 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Re: Deprecation/removal of nios2 target support

On 4/18/24 8:41 PM, Arnd Bergmann wrote: On Thu, Apr 18, 2024, at 17:44, Joseph Myers wrote: On Wed, 17 Apr 2024, Sandra Loosemore wrote: Therefore I'd like to mark Nios II as obsolete in GCC 14 now, and remove support from all toolchain components after the release is made. I'm not sure

Re: Updated Sourceware infrastructure plans

> 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 you have only a non maintainer build, it is a pain to have to

Re: Updated Sourceware infrastructure plans

Am 18.04.24 um 01:27 schrieb Mark Wielaard: We also should make sure that all generated files (either in git or in the release/snapshot tar balls) can be reliably and reproducibly regenerated. This also helps the (pre-commit) CI buildbots. We already have the autoregen bots for gcc and

Re: [PATCH] [libstdc++] [testsuite] xfail double-prec from_chars for float128_t

On Apr 16, 2024, Alexandre Oliva wrote: > * testsuite/20_util/to_chars/float128-c++23.cc: Xfail run on > aarch64-vxworks. FTR, here's the fixed ChangeLog entry I'm putting in: (s/-/_/) * testsuite/20_util/to_chars/float128_c++23.cc: Xfail run on aarch64-vxworks. --

Re: [PATCH] [testsuite] introduce strndup effective target

On Apr 16, 2024, Alexandre Oliva wrote: > * gcc.dg/builtin-dynamic-object-size-1.c: Likewise. > * gcc.dg/builtin-dynamic-object-size-2.c: Likewise. > * gcc.dg/builtin-dynamic-object-size-3.c: Likewise. > * gcc.dg/builtin-dynamic-object-size-4.c: Likewise. These hunks

[Bug fortran/114767] New: gfortran AVX2 complex multiplication by (0d0,1d0) suboptimal

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114767 Bug ID: 114767 Summary: gfortran AVX2 complex multiplication by (0d0,1d0) suboptimal Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/114767] gfortran AVX2 complex multiplication by (0d0,1d0) suboptimal

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114767 Richard Biener changed: What|Removed |Added Keywords||missed-optimization Last

[Bug lto/114574] [14 regression] ICE when building curl with LTO (fld_incomplete_type_of, at ipa-free-lang-data.cc:257) since r14-9763

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114574 --- Comment #30 from Martin Uecker --- Am Donnerstag, dem 18.04.2024 um 11:57 + schrieb jakub at gcc dot gnu.org: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114574 > > --- Comment #29 from Jakub Jelinek --- > (In reply to uecker from

Results for 14.0.1 20240418 (experimental) [remotes/origin/HEAD r14-10029-g7eecc08ccf] (GCC) testsuite on powerpc64le-unknown-linux-gnu

t/powerpc/ppc-fortran/ieee128-math.f90 -O (test for excess errors) === gcc Summary === # of expected passes179426 # of unexpected failures97 # of unexpected successes 20 # of expected failures 1612 # of unsupported tests 4244 /home/g

Results for 14.0.1 20240418 (experimental) [master r14-10013-g82d6d385f9] (GCC) testsuite on powerpc64-unknown-linux-gnu

failures 5241 # of unsupported tests 23185 /home/gccbuild/build/nightly/build-gcc-trunk/gcc/xg++ version 14.0.1 20240418 (experimental) [master r14-10013-g82d6d385f9] (GCC) === gcc tests === Running target unix/-m32 XPASS: gcc.dg/guality/example.c -O0 execution

[gcc r14-10029] [testsuite] [i386] add -msse2 to tests that require it

https://gcc.gnu.org/g:7eecc08ccf75679e6ae688d92e50afae935547ab commit r14-10029-g7eecc08ccf75679e6ae688d92e50afae935547ab Author: Alexandre Oliva Date: Thu Apr 18 08:01:43 2024 -0300 [testsuite] [i386] add -msse2 to tests that require it Without -msse2, an i586-targeting

[gcc r14-10026] [c++] [testsuite] adjust contracts9.C for negative addresses

https://gcc.gnu.org/g:ce2dfc57b4562fef0d279697d96f672bc903e853 commit r14-10026-gce2dfc57b4562fef0d279697d96f672bc903e853 Author: Alexandre Oliva Date: Thu Apr 18 08:01:35 2024 -0300 [c++] [testsuite] adjust contracts9.C for negative addresses The test expected the address of a

[gcc r14-10027] [testsuite] [arm] accept empty init for bfloat16

https://gcc.gnu.org/g:36d003816352052f610a3f63ab74b6443eb7efb7 commit r14-10027-g36d003816352052f610a3f63ab74b6443eb7efb7 Author: Alexandre Oliva Date: Thu Apr 18 08:01:37 2024 -0300 [testsuite] [arm] accept empty init for bfloat16 Complete r13-2205, adjusting an arm-specific

[gcc r14-10028] [testsuite] [i386] work around fails with --enable-frame-pointer

https://gcc.gnu.org/g:0ea96af1150c221092a0880af51dbe66b75ecb03 commit r14-10028-g0ea96af1150c221092a0880af51dbe66b75ecb03 Author: Alexandre Oliva Date: Thu Apr 18 08:01:40 2024 -0300 [testsuite] [i386] work around fails with --enable-frame-pointer A few x86 tests get unexpected

[gcc r14-10025] [testsuite] [aarch64] Require fpic effective target.

https://gcc.gnu.org/g:df92df0c19f7783519a392f7ac7d4e617250c328 commit r14-10025-gdf92df0c19f7783519a392f7ac7d4e617250c328 Author: Alexandre Oliva Date: Thu Apr 18 08:01:32 2024 -0300 [testsuite] [aarch64] Require fpic effective target. Co-authored-by: Olivier Hainque

[gcc r14-10024] [testsuite] [i386] require fpic for pr111497.C

https://gcc.gnu.org/g:514c6b1cb766dc0a14121016ce84b9f5a1ef4e41 commit r14-10024-g514c6b1cb766dc0a14121016ce84b9f5a1ef4e41 Author: Alexandre Oliva Date: Thu Apr 18 08:01:29 2024 -0300 [testsuite] [i386] require fpic for pr111497.C Fix another test that uses -fPIC without requiring

[gcc r14-10022] [testsuite] [analyzer] include sys/select.h if available

https://gcc.gnu.org/g:e965162bb9de6d2cd68cdc0e26dda56abd25fcdf commit r14-10022-ge965162bb9de6d2cd68cdc0e26dda56abd25fcdf Author: Alexandre Oliva Date: Thu Apr 18 08:01:21 2024 -0300 [testsuite] [analyzer] include sys/select.h if available Test that calls select fails on vxworks

[gcc r14-10023] [testsuite] xfail pr103798-2 in C++ on vxworks too [PR113706]

https://gcc.gnu.org/g:cc02ebfcfd0755b330c50a840ab713fedd6d8887 commit r14-10023-gcc02ebfcfd0755b330c50a840ab713fedd6d8887 Author: Alexandre Oliva Date: Thu Apr 18 08:01:26 2024 -0300 [testsuite] xfail pr103798-2 in C++ on vxworks too [PR113706] pr103798-2.c fails in C++ on

[Bug c++/113706] c-c++-common/pr103798-2.c FAILs as C++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113706 --- Comment #11 from GCC Commits --- The master branch has been updated by Alexandre Oliva : https://gcc.gnu.org/g:cc02ebfcfd0755b330c50a840ab713fedd6d8887 commit r14-10023-gcc02ebfcfd0755b330c50a840ab713fedd6d8887 Author: Alexandre Oliva

[gcc r14-10020] [testsuite] [analyzer] skip access-mode: O_ACCMODE on vxworks

https://gcc.gnu.org/g:5be4f203c491b654ae2b2d5a01b58613f74aba1d commit r14-10020-g5be4f203c491b654ae2b2d5a01b58613f74aba1d Author: Alexandre Oliva Date: Thu Apr 18 08:01:11 2024 -0300 [testsuite] [analyzer] skip access-mode: O_ACCMODE on vxworks O_ACCMODE is not defined on

[gcc r14-10021] [testsuite] [analyzer] require fork where used

https://gcc.gnu.org/g:8a1170903212ed31fd970d3c1b9fabf50868d01a commit r14-10021-g8a1170903212ed31fd970d3c1b9fabf50868d01a Author: Alexandre Oliva Date: Thu Apr 18 08:01:15 2024 -0300 [testsuite] [analyzer] require fork where used Mark tests that fail due to the lack of fork, as

Results for 14.0.1 20240418 (experimental) [remotes/origin/HEAD r14-10014-ga2f4be3dae0] (GCC) testsuite on powerpc64le-unknown-linux-gnu

of unsupported tests 4242 /home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240418 (experimental) [remotes/origin/HEAD r14-10014-ga2f4be3dae0] (GCC) === gfortran tests === Running target unix XPASS: gfortran.dg/large_real_kind_form_io_2.f90

[Bug rtl-optimization/114768] New: Volatile reads can be optimized away

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114768 Bug ID: 114768 Summary: Volatile reads can be optimized away Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

Results for 14.0.1 20240418 (experimental) [master r14-10029-g7eecc08ccf] (GCC) testsuite on powerpc64-unknown-linux-gnu

failures 5241 # of unsupported tests 23185 /home/gccbuild/build/nightly/build-gcc-trunk/gcc/xg++ version 14.0.1 20240418 (experimental) [master r14-10029-g7eecc08ccf] (GCC) === gcc tests === Running target unix/-m32 XPASS: gcc.dg/guality/example.c -O0 execution

[gcc r14-10014] AArch64: remove reliance on register allocator for simd/gpreg costing. [PR114741]

https://gcc.gnu.org/g:a2f4be3dae04fa8606d1cc8451f0b9d450f7e6e6 commit r14-10014-ga2f4be3dae04fa8606d1cc8451f0b9d450f7e6e6 Author: Tamar Christina Date: Thu Apr 18 11:47:42 2024 +0100 AArch64: remove reliance on register allocator for simd/gpreg costing. [PR114741] In PR114741 we

[Bug target/114741] [14 regression] aarch64 sve: unnecessary fmov for scalar int bit operations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114741 --- Comment #9 from GCC Commits --- The master branch has been updated by Tamar Christina : https://gcc.gnu.org/g:a2f4be3dae04fa8606d1cc8451f0b9d450f7e6e6 commit r14-10014-ga2f4be3dae04fa8606d1cc8451f0b9d450f7e6e6 Author: Tamar Christina

Re: [PATCH] [testsuite] [arm] accept empty init for bfloat16

On Apr 16, 2024, Mike Stump wrote: > Indeed, I kinda expect coverage already for that feature in > another test case. *nod*, jsm added gcc.dg/c11-empty-init-[123].c (and more) in the patch that implemented this c23 feature. -- Alexandre Oliva, happy hacker

[Bug rtl-optimization/114768] Volatile reads can be optimized away

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114768 --- Comment #2 from Jakub Jelinek --- --- gcc/rtlanal.cc.jj 2024-02-24 12:45:28.674249100 +0100 +++ gcc/rtlanal.cc 2024-04-18 15:09:55.199499083 +0200 @@ -1637,12 +1637,15 @@ set_noop_p (const_rtx set) return true; if (MEM_P

Results for 14.0.1 20240417 (experimental) [master r14-10005-gbf2b5231312] (GCC) testsuite on x86_64-pc-linux-gnu

LAST_UPDATED: Wed Apr 17 13:30:07 UTC 2024 (revision r14-10005-gbf2b5231312) Native configuration is x86_64-pc-linux-gnu === gcc tests === Running target unix XPASS: gcc.dg/guality/example.c -O0 execution test XPASS: gcc.dg/guality/example.c -O1 -DPREVENT_OPTIMIZATION

Regressions on master at commit r14-10005 vs commit r14-9993 on Linux/x86_64

Regressions on master at commit r14-10005 vs commit r14-9993 on Linux/x86_64 New failures: New passes: FAIL: gcc.dg/vect/vect-early-break_124-pr114403.c execution test FAIL: gcc.dg/vect/vect-early-break_124-pr114403.c execution test FAIL: gcc.dg/vect/vect-early-break_124-pr114403.c -flto

[Bug middle-end/112938] ice with -fstrub=internal

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112938 Alexandre Oliva changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED

[Bug libgcc/114762] wrong code with _BitInt() division by "BITINT_NN_MIN"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114762 --- Comment #1 from Zdenek Sojka --- Created attachment 57981 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57981=edit testcase trying reasonable input for division (and multiplication) This can be used to test various input

[Bug rtl-optimization/114768] Volatile reads can be optimized away

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114768 Richard Biener changed: What|Removed |Added Last reconfirmed||2024-04-18

[Bug tree-optimization/114769] New: Suspicious code in vect_recog_sad_pattern()

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114769 Bug ID: 114769 Summary: Suspicious code in vect_recog_sad_pattern() Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug ipa/113291] [14 Regression] compilation never (?) finishes with recursive always_inline functions at -O and above since r14-2172

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113291 Jeffrey A. Law changed: What|Removed |Added Priority|P1 |P2 CC|

[Bug rtl-optimization/114768] Volatile reads can be optimized away

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114768 --- Comment #6 from Segher Boessenkool --- Heh, crossed :-) I can confirm my patch works (tested and everything). I have no idea about zero_extract, which is a blight that should be eradicated tooth and nail!

[Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678 Christophe Lyon changed: What|Removed |Added CC||clyon at gcc dot gnu.org --- Comment

Re: [PATCH]AArch64: remove reliance on register allocator for simd/gpreg costing. [PR114741]

On 18/04/2024 11:11, Tamar Christina wrote: > Hi All, > > In PR114741 we see that we have a regression in codegen when SVE is enable > where > the simple testcase: > > void foo(unsigned v, unsigned *p) > { > *p = v & 1; > } > > generates > > foo: > fmovs31, w0 > and

[Bug tree-optimization/114761] Ignored [[likely]] attribute with multiple if statements doing the same thing

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114761 --- Comment #5 from Alexander Zaitsev --- > Is this based on real code or you just was looking at the differences between > gcc and clang here? Really, not on a real code. I came up with this example when I found that GCC for this example

[Bug lto/114574] [14 regression] ICE when building curl with LTO (fld_incomplete_type_of, at ipa-free-lang-data.cc:257) since r14-9763

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114574 --- Comment #29 from Jakub Jelinek --- (In reply to uecker from comment #28) > I do not fully understand yet what happens for may_alias, but it if we later > complete the struct with the may_alias attribute it seems we would also need > to

[Bug rtl-optimization/114766] New: ^ constraint modifier unexpectedly affects register class selection.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114766 Bug ID: 114766 Summary: ^ constraint modifier unexpectedly affects register class selection. Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords:

Results for 12.3.1 20240418 [remotes/origin/releases/gcc-12 r12-10335-ge2403376c2] (GCC) testsuite on powerpc64le-unknown-linux-gnu

2081 # of unexpected failures170 # of unexpected successes 14 # of expected failures 1468 # of unsupported tests 3885 /home/gccbuild/build/nightly/build-gcc-12/gcc/xgcc version 12.3.1 20240418 [remotes/origin/releases/gcc-12 r12-10335-ge2403376c2] (GCC)

[Bug rtl-optimization/114768] Volatile reads can be optimized away

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114768 Jakub Jelinek changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org

[Bug tree-optimization/114767] gfortran AVX2 complex multiplication by (0d0,1d0) suboptimal

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114767 --- Comment #2 from mjr19 at cam dot ac.uk --- Ah, I see. An inability to alternate negation with noop also means that conjugation is treated suboptimally. do i=1,n c(i)=conjg(c(i)) enddo Here gfortran-13 and -14 are differently

[Bug target/114676] [12/13/14 Regression] DSE removes assignment that is used later

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114676 --- Comment #15 from Aleksei Nikiforov --- I think fixing compiled code should be possible. I'm not sure if this bug should be just closed.

Regressions on master at commit r14-10009 vs commit r14-10005 on Linux/x86_64

Regressions on master at commit r14-10009 vs commit r14-10005 on Linux/x86_64 New failures: New passes: FAIL: gcc.dg/torture/convert-dfp-2.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (test for excess errors) FAIL: gcc.dg/torture/convert-dfp.c -O2 -flto -fuse-linker-plugin

Results for 14.0.1 20240418 (experimental) [master r14-10009-g69576bc01ca] (GCC) testsuite on x86_64-pc-linux-gnu

gnu/import/git/gcc-test-master-intel64/bld/gcc/xgcc version 14.0.1 20240418 (experimental) [master r14-10009-g69576bc01ca] (GCC) === gfortran tests === Running target unix === gfortran Summary for unix === # of expected passes70038 # of expected failu

[Bug libgomp/114765] linking to libgomp and setting CPU_PROC_BIND causes affinity reset

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114765 --- Comment #2 from Stijn De Weirdt --- hi jakub, apologies for my ignorance, but how is working as expected? i can't make this up from the description of the variable; and it's unexpected since there is no openmp code being run (naively then;

Results for 14.0.1 20240418 (experimental) [remotes/origin/HEAD r14-10014-ga2f4be3dae] (GCC) testsuite on powerpc64le-unknown-linux-gnu

t/powerpc/ppc-fortran/ieee128-math.f90 -O (test for excess errors) === gcc Summary === # of expected passes179426 # of unexpected failures97 # of unexpected successes 20 # of expected failures 1612 # of unsupported tests 4244 /home/g

[gcc/devel/jlaw/crc] Refactored sym-exec: Added comments, changed members' names ...

https://gcc.gnu.org/g:525b7590e3668c7a72b0d77c89bdd1ac5f6ada8a commit 525b7590e3668c7a72b0d77c89bdd1ac5f6ada8a Author: Mariam Arutunian Date: Mon Apr 15 15:36:18 2024 +0400 Refactored sym-exec: Added comments, changed members' names ... Diff: --- gcc/sym-exec/condition.cc | 14 ++--

[Bug rtl-optimization/114768] Volatile reads can be optimized away

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114768 --- Comment #1 from Richard Biener --- It's the combine pass that removes the seemingly noop-move. For QOI reasons GCC preserves volatile accesses elsewhere even when inconsistency is directly visible like here.

[Bug libgomp/114765] linking to libgomp and setting CPU_PROC_BIND causes affinity reset

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114765 --- Comment #6 from Jakub Jelinek --- (In reply to Alexander Monakov from comment #5) > Can libgomp defer changing affinity of the initial thread to the launch of > the first parallel region (i.e. change it only at thread pool > initialization,

[Bug c++/114764] New: noexcept on a friend complains about incomplete type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114764 Bug ID: 114764 Summary: noexcept on a friend complains about incomplete type Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3

Results for 14.0.1 20240418 (experimental) [remotes/origin/HEAD r14-10013-g82d6d385f9] (GCC) testsuite on powerpc64le-unknown-linux-gnu

t/powerpc/ppc-fortran/ieee128-math.f90 -O (test for excess errors) === gcc Summary === # of expected passes179426 # of unexpected failures97 # of unexpected successes 20 # of expected failures 1612 # of unsupported tests 4244 /home/g

Re: [PATCH] libgcc: Fix up __divmodbitint4 [PR114755]

On Thu, Apr 18, 2024 at 11:25:43AM +0200, Christophe Lyon wrote: > On Thu, 18 Apr 2024 at 09:37, Jakub Jelinek wrote: > > The following testcase aborts on aarch64-linux but does not on x86_64-linux. > > In both cases there is UB in the __divmodbitint4 implemenetation. > > When the divisor is

[PATCH]AArch64: remove reliance on register allocator for simd/gpreg costing. [PR114741]

Hi All, In PR114741 we see that we have a regression in codegen when SVE is enable where the simple testcase: void foo(unsigned v, unsigned *p) { *p = v & 1; } generates foo: fmovs31, w0 and z31.s, z31.s, #1 str s31, [x1] ret instead of: foo:

[Bug libgcc/114762] wrong code with _BitInt() division by "BITINT_NN_MIN"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114762 Jakub Jelinek changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug libgomp/114765] linking to libgomp and setting CPU_PROC_BIND causes affinity reset

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114765 --- Comment #1 from Jakub Jelinek --- That is how it should behave. Don't use OMP_PROC_BIND=true unless that is what you want...

Results for 14.0.1 20240418 (experimental) [master revision gcc-14-10029-g7eecc08ccf7] (GCC) testsuite on arm-unknown-eabi

/mve-vshr.c scan-assembler-times vshl.u[0-9]+tq[0-9]+, q[0-9]+ 3 === gcc Summary === # of expected passes160445 # of unexpected failures268 # of expected failures 1016 # of unresolved testcases 1 # of unsupported tests 9372 /home/tcwg-buildsl

[PATCH v2] gcc-14: Add Ada changes

Co-authored-by: Fernando Oleo Blanco --- Hello Fernando, Thanks again for your changes. After consulting other colleagues, I'm proposing this revised version. Does that look ok to you? As it was simpler I've created a new commit with a Co-authored-by line, but can easily change that if you

[Bug rtl-optimization/114729] RISC-V SPEC2017 507.cactu excessive spillls with -fschedule-insns

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114729 --- Comment #11 from Jeffrey A. Law --- Yup. -fsched-verbose=99 is *very* verbose. But that's the point, to see all the gory details. It can be dialed down, but I've never done so myself. What stands out to me is this: ;;| Pressure

Re: [PATCH] libgcc: Fix up __divmodbitint4 [PR114755]

On Thu, 18 Apr 2024 at 09:37, Jakub Jelinek wrote: > > Hi! > > The following testcase aborts on aarch64-linux but does not on x86_64-linux. > In both cases there is UB in the __divmodbitint4 implemenetation. > When the divisor is negative with most significant limb (even when partial) > all ones,

Results for 14.0.1 20240418 (experimental) [remotes/origin/HEAD r14-10013-g82d6d385f97] (GCC) testsuite on powerpc64le-unknown-linux-gnu

of unsupported tests 4242 /home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240418 (experimental) [remotes/origin/HEAD r14-10013-g82d6d385f97] (GCC) === gfortran tests === Running target unix XPASS: gfortran.dg/large_real_kind_form_io_2.f90

Re: [PATCH, rs6000] Use bcdsub. instead of bcdadd. for bcd invalid number checking

On Thu, Apr 18, 2024 at 11:14:42AM +0800, Kewen.Lin wrote: > on 2024/4/18 10:01, HAO CHEN GUI wrote: > > This patch replace bcdadd. with bcdsub. for bcd invalid number checking. > > bcdadd on two same numbers might cause overflow which also set > > overflow/invalid bit so that we can't

[Bug target/114741] [14 regression] aarch64 sve: unnecessary fmov for scalar int bit operations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114741 Tamar Christina changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug target/114513] [11/12/13/14 Regression] [aarch64] floating-point registers are used when GPRs are preferred

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114513 Bug 114513 depends on bug 114741, which changed state. Bug 114741 Summary: [14 regression] aarch64 sve: unnecessary fmov for scalar int bit operations https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114741 What|Removed

[Bug libgomp/114765] New: linking to libgomp and setting CPU_PROC_BIND causes affinity reset

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114765 Bug ID: 114765 Summary: linking to libgomp and setting CPU_PROC_BIND causes affinity reset Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal

[Bug libgomp/114765] linking to libgomp and setting CPU_PROC_BIND causes affinity reset

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114765 --- Comment #3 from Jakub Jelinek --- (In reply to Stijn De Weirdt from comment #2) > apologies for my ignorance, but how is working as expected? i can't make > this up from the description of the variable; and it's unexpected since > there is

Results for 14.0.1 20240418 (experimental) [remotes/origin/HEAD r14-10013-g82d6d385f9] (GCC) testsuite on powerpc64le-unknown-linux-gnu

== gcc Summary === # of expected passes178407 # of unexpected failures128 # of unexpected successes 13 # of expected failures 1595 # of unsupported tests 5028 /home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240418 (experimental) [remotes

Results for 14.0.1 20240418 (experimental) [master r14-10014-ga2f4be3dae] (GCC) testsuite on powerpc64-unknown-linux-gnu

failures 5241 # of unsupported tests 23185 /home/gccbuild/build/nightly/build-gcc-trunk/gcc/xg++ version 14.0.1 20240418 (experimental) [master r14-10014-ga2f4be3dae] (GCC) === gcc tests === Running target unix/-m32 XPASS: gcc.dg/guality/example.c -O0 execution

[Bug libgomp/114765] linking to libgomp and setting CPU_PROC_BIND causes affinity reset

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114765 Alexander Monakov changed: What|Removed |Added CC||amonakov at gcc dot gnu.org ---

[PATCH] libgfortran: Fix up the autoreconf warnings.

@tschwinge since he did quite a bit of work on getting autoreconf to work in the GCC-13 cycle. This does not address the issues with regenerating lib code, but it does make things somewhat smoother for cases where the updates are only in Makefile.am, configure.ac or libtool.m4 for example. It is

Results for 13.2.1 20240418 [releases/gcc-13 r13-8617-gafbf411b31] (GCC) testsuite on powerpc64le-unknown-linux-gnu

f expected failures 1550 # of unsupported tests 3992 /home/gccbuild/build/nightly/build-gcc-13/gcc/xgcc version 13.2.1 20240418 [releases/gcc-13 r13-8617-gafbf411b31] (GCC) === gfortran tests === Running target unix XPASS: gfortran.dg/large_real_kind_form_io_2

Results for 14.0.1 20240418 (experimental) [master r14-10011-g6e62ede7aac] (GCC) testsuite on x86_64-pc-linux-gnu

ect/git/gcc-test-master-intel64/bld/gcc/xgcc version 14.0.1 20240418 (experimental) [master r14-10011-g6e62ede7aac] (GCC) === gfortran tests === Running target unix === gfortran Summary for unix === # of expected passes70038 # of expected failu

[gcc r14-10017] [libstdc++] [testsuite] disable SRA for compare_exchange_padding

https://gcc.gnu.org/g:dcf0bd14cda706be8d0c18963812beefca51df39 commit r14-10017-gdcf0bd14cda706be8d0c18963812beefca51df39 Author: Alexandre Oliva Date: Thu Apr 18 08:00:59 2024 -0300 [libstdc++] [testsuite] disable SRA for compare_exchange_padding On arm-vx7r2, the uses of

[gcc r14-10018] [testsuite] introduce strndup effective target

https://gcc.gnu.org/g:5dfbc05c4a8da4a177056c57e13e5050c637056e commit r14-10018-g5dfbc05c4a8da4a177056c57e13e5050c637056e Author: Alexandre Oliva Date: Thu Apr 18 08:01:04 2024 -0300 [testsuite] introduce strndup effective target A number of tests that call strndup fail on

[gcc r14-10016] [libstdc++] [testsuite] xfail double-prec from_chars for float128_t

https://gcc.gnu.org/g:5b178179e85ace01a97def40531e915c180aaeca commit r14-10016-g5b178179e85ace01a97def40531e915c180aaeca Author: Alexandre Oliva Date: Thu Apr 18 08:00:56 2024 -0300 [libstdc++] [testsuite] xfail double-prec from_chars for float128_t Tests 20_util/from_chars/4.cc

[gcc r14-10015] [libstdc++] define zoneinfo_dir_override on vxworks

https://gcc.gnu.org/g:da3504ae4d1e6872585b1107a4932efd3824e943 commit r14-10015-gda3504ae4d1e6872585b1107a4932efd3824e943 Author: Alexandre Oliva Date: Thu Apr 18 08:00:52 2024 -0300 [libstdc++] define zoneinfo_dir_override on vxworks VxWorks fails to load kernel-mode modules

[gcc r14-10019] [testsuite] [analyzer] avoid vxworks libc mode_t

https://gcc.gnu.org/g:76a1bcc05f152da17770e94eaaf7aa491af2ff01 commit r14-10019-g76a1bcc05f152da17770e94eaaf7aa491af2ff01 Author: Alexandre Oliva Date: Thu Apr 18 08:01:07 2024 -0300 [testsuite] [analyzer] avoid vxworks libc mode_t Define macro that prevents mode_t from being

[Bug libgomp/114765] linking to libgomp and setting CPU_PROC_BIND causes affinity reset

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114765 --- Comment #4 from Stijn De Weirdt --- hi jakub, thanks for the explanation. so if i understand this, the main thread/process of any binary linked with libgomp becomes an OpenMP thread, because of the libgomp constructor doing something. and

Re: [PATCH] [vxworks] avoid mangling __STDC_VERSION_LIMITS_H__

> On 16 Apr 2024, at 05:27, Alexandre Oliva wrote: > > > The mangling of the macro name that guards limits.h from reinclusion > was mangling a c23-required macro as well. Make the edit pattern > stricter. > > Regstrapped on x86_64-linux-gnu. Also tested with gcc-13 on arm-, > aarch64-,

[Bug rtl-optimization/114768] Volatile reads can be optimized away

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114768 Segher Boessenkool changed: What|Removed |Added CC||segher at gcc dot gnu.org ---

[gcc r12-10342] Darwin: Partial reversion of r14-3648 (Inits Section).

https://gcc.gnu.org/g:a732f63ebc032fbcd7740156d497472d16bdea50 commit r12-10342-ga732f63ebc032fbcd7740156d497472d16bdea50 Author: Iain Sandoe Date: Sun Sep 10 14:48:42 2023 +0100 Darwin: Partial reversion of r14-3648 (Inits Section). Although the Darwin ABI places both hot and

Results for 14.0.1 20240418 (experimental) [master revision gcc-14-10029-g7eecc08ccf7] (GCC) testsuite on arm-unknown-eabi

cases 1 # of unsupported tests 9459 /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/destdir/x86_64-pc-linux-gnu/bin/arm-eabi-gcc version 14.0.1 20240418 (experimental) [master revision gcc-14-10029-g7eecc08ccf7] (GCC) Host is x86_64-pc-linux-gnu === g++ te

  1   2   3   >