Results for 13.2.1 20240314 [releases/gcc-13 r13-8438-gbdbcfbfcf5] (GCC) testsuite on powerpc64le-unknown-linux-gnu

unexpected successes 3 # of expected failures 1438 # of unsupported tests 2769 /home/gccbuild/build/nightly/build-gcc-13/gcc/xgcc version 13.2.1 20240314 [releases/gcc-13 r13-8438-gbdbcfbfcf5] (GCC) === gfortran tests === Running target unix XPASS: g

[Bug libgomp/114335] OpenACC: use of accelerator constant/read-only memory for "readonly" modifier mappings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114335 Tobias Burnus changed: What|Removed |Added Keywords||missed-optimization,

Regressions on releases/gcc-13 at commit r13-8438 vs commit r13-8432 on Linux/i686

Regressions on releases/gcc-13 at commit r13-8438 vs commit r13-8432 on Linux/i686 New failures: FAIL: gcc.dg/2111-1.c (test for excess errors) FAIL: gcc.dg/980816-1.c (test for excess errors) FAIL: gcc.dg/990506-0.c (test for excess errors) FAIL: gcc.dg/bconstp-4.c (test for errors, line

Results for 13.2.1 20240314 [releases/gcc-13-ia32 r13-8438-gbdbcfbfcf59] (GCC) testsuite on i686-pc-linux-gnu

ed tests 3018 /export/gnu/import/git/gcc-test-release-1-ia32/bld/gcc/xgcc version 13.2.1 20240314 [releases/gcc-13-ia32 r13-8438-gbdbcfbfcf59] (GCC) === gfortran tests === Running target unix === gfortran Summary === # of expected passes

Re: Builtin for consulting value analysis (better ffs() code gen)

On Mär 14 2024, Andrew Cooper via Gcc wrote: > so any known-constant value can be folded.  What I'm dealing with is the > remainder of the cases. Which cases remain? -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now

[Bug libstdc++/114336] New: Manual should document implementation-defined behaviour in C++20 and C++23

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114336 Bug ID: 114336 Summary: Manual should document implementation-defined behaviour in C++20 and C++23 Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords:

[Bug libgomp/114335] New: OpenACC: use of accelerator constant/read-only memory for "readonly" modifier mappings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114335 Bug ID: 114335 Summary: OpenACC: use of accelerator constant/read-only memory for "readonly" modifier mappings Product: gcc Version: unknown Status: UNCONFIRMED

[committed] libstdc++: Correct notes about std::call_once in manual [PR66146]

Pushed to trunk. I should backport this too. -- >8 -- The bug with exceptions thrown during a std::call_once call affects all targets, so fix the docs that say it only affects non-Linux targets. libstdc++-v3/ChangeLog: PR libstdc++/66146 * doc/xml/manual/status_cxx2011.xml:

Results of testsuite (branch: master; revision: r14-9460; build config: lto,O3; languages: fortran; tasks: 16) on x86_64-linux-gnu.

106 # of unexpected successes 16 # of expected failures 1551 # of unsupported tests 3284 /home/toon/scratch/bld1948/gcc/xgcc version 14.0.1 20240314 (experimental) [master r14-9460-g8f6e0814b4b] (GCC) === gfortran tests === Running target unix

[committed] libstdc++: Update C++23 status in the manual

I think we have all C++23 changes in this table now. At some point soon we should replace the C++20 table of papers with the C++20 table of contents, as we do for the other standards. Pushed to trunk. -- >8 -- libstdc++-v3/ChangeLog: * doc/xml/manual/status_cxx2023.xml: Update C++23

Results for 12.3.1 20240314 [releases/gcc-12 r12-10214-ga861f940ef] (GCC) testsuite on powerpc64le-unknown-linux-gnu

12/gcc/xgcc version 12.3.1 20240314 [releases/gcc-12 r12-10214-ga861f940ef] (GCC) === gfortran tests === Running target unix XPASS: gfortran.dg/default_format_2.f90 -O0 execution test XPASS: gfortran.dg/default_format_2.f90 -O1 execution test XPASS: gfortran.dg/defaul

[Bug libstdc++/66146] call_once not C++11-compliant on ppc64le

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66146 --- Comment #55 from GCC Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:e6836bbbd7a01af0791c02087e568b4822418c0d commit r14-9467-ge6836bbbd7a01af0791c02087e568b4822418c0d Author: Jonathan Wakely

[gcc r14-9467] libstdc++: Correct notes about std::call_once in manual [PR66146]

https://gcc.gnu.org/g:e6836bbbd7a01af0791c02087e568b4822418c0d commit r14-9467-ge6836bbbd7a01af0791c02087e568b4822418c0d Author: Jonathan Wakely Date: Thu Mar 14 11:52:17 2024 + libstdc++: Correct notes about std::call_once in manual [PR66146] The bug with exceptions thrown

[gcc r14-9466] libstdc++: Update C++23 status in the manual

https://gcc.gnu.org/g:2a556dbec2e522655175374c68d61a39b1463c7e commit r14-9466-g2a556dbec2e522655175374c68d61a39b1463c7e Author: Jonathan Wakely Date: Thu Mar 14 11:47:56 2024 + libstdc++: Update C++23 status in the manual libstdc++-v3/ChangeLog: *

[Bug target/114334] [14 Regression] ICE: in extract_insn, at recog.cc:2812 (unrecognizable insn and:HF?) with lroundf16() and -ffast-math -mavx512fp16

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114334 Richard Biener changed: What|Removed |Added Target Milestone|--- |14.0

Re: Builtin for consulting value analysis (better ffs() code gen)

On 14/03/2024 11:02 am, Florian Weimer wrote: > * Andrew Cooper via Gcc: > >> Anyway - is there a way of doing this that I've managed to overlook? > Use __builtin_ffs? > > I think there's some concern for GCC that some of the alternative x86-64 > implementations do not follow the AMD and Intel

Re: [PATCH] bitint, v2: Fix up adjustment of large/huge _BitInt arguments of returns_twice calls [PR113466]

On Thu, 14 Mar 2024, Jakub Jelinek wrote: > On Thu, Mar 14, 2024 at 09:59:12AM +0100, Richard Biener wrote: > > On Thu, 14 Mar 2024, Jakub Jelinek wrote: > > > > > On Thu, Mar 14, 2024 at 09:48:45AM +0100, Richard Biener wrote: > > > > Ugh. OK, but I wonder whether we might want to simply delay

Re: [PATCH] aarch64: Fix TImode __sync_*_compare_and_exchange expansion with LSE [PR114310]

On 14/03/2024 08:37, Jakub Jelinek wrote: Hi! The following testcase ICEs with LSE atomics. The problem is that the @atomic_compare_and_swap expander uses aarch64_reg_or_zero predicate for the desired operand, which is fine, given that for most of the modes and even for TImode in some cases

Re: [PATCH v2] openmp: Change to using a hashtab to lookup offload target addresses for indirect function calls

Hi Kwok, On January 22, 2024, Kwok Cheung Yeung wrote: There was a bug in the declare-target-indirect-2.c libgomp testcase (testing indirect calls in offloaded target regions, spread over multiple teams/threads) that due to an errant fallthrough in a switch statement resulted in only one

[Bug preprocessor/110558] __has_include argument expansion results in unexpected filename

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110558 Lewis Hyatt changed: What|Removed |Added Target Milestone|--- |14.0 Resolution|---

[Bug preprocessor/80755] __has_include_next: internal compiler error: NULL directory in find_file

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80755 Lewis Hyatt changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug preprocessor/110558] __has_include argument expansion results in unexpected filename

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110558 --- Comment #6 from GCC Commits --- The master branch has been updated by Lewis Hyatt : https://gcc.gnu.org/g:942497ad74272e0ef16020d628e471c5f21474b0 commit r14-9465-g942497ad74272e0ef16020d628e471c5f21474b0 Author: Lewis Hyatt Date: Tue

[gcc r14-9465] libcpp: Fix macro expansion for argument of __has_include [PR110558]

https://gcc.gnu.org/g:942497ad74272e0ef16020d628e471c5f21474b0 commit r14-9465-g942497ad74272e0ef16020d628e471c5f21474b0 Author: Lewis Hyatt Date: Tue Dec 12 17:46:36 2023 -0500 libcpp: Fix macro expansion for argument of __has_include [PR110558] When the file name for a #include

[Bug preprocessor/80755] __has_include_next: internal compiler error: NULL directory in find_file

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80755 --- Comment #7 from GCC Commits --- The master branch has been updated by Lewis Hyatt : https://gcc.gnu.org/g:6c166e55b15894ceb07dcc7b55f900e50e24ec5b commit r14-9464-g6c166e55b15894ceb07dcc7b55f900e50e24ec5b Author: Lewis Hyatt Date: Wed

[gcc r14-9464] libcpp: Fix __has_include_next ICE in the last directory of the path [PR80755]

https://gcc.gnu.org/g:6c166e55b15894ceb07dcc7b55f900e50e24ec5b commit r14-9464-g6c166e55b15894ceb07dcc7b55f900e50e24ec5b Author: Lewis Hyatt Date: Wed Dec 20 16:27:42 2023 -0500 libcpp: Fix __has_include_next ICE in the last directory of the path [PR80755] In libcpp/files.cc,

Re: Builtin for consulting value analysis (better ffs() code gen)

On 14/03/2024 6:04 am, Alexander Monakov wrote: > On Thu, 14 Mar 2024, Andrew Cooper via Gcc wrote: > >> I suppose that what I'm looking for is something a little like >> __builtin_constant_p() which can either be used in a straight if(), or >> in a __builtin_choose_expr(). >> >> Anyway - is there

[Bug modula2/114333] set type comparison against a cardinal should cause an error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114333 --- Comment #3 from GCC Commits --- The master branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:b7f70cfdb6f7ab369ecca14a99a0064d2a11ddd2 commit r14-9463-gb7f70cfdb6f7ab369ecca14a99a0064d2a11ddd2 Author: Gaius Mulley Date:

[Bug modula2/114333] set type comparison against a cardinal should cause an error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114333 Gaius Mulley changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[gcc r14-9463] PR modula2/114333 set type comparison against a cardinal should cause an error

https://gcc.gnu.org/g:b7f70cfdb6f7ab369ecca14a99a0064d2a11ddd2 commit r14-9463-gb7f70cfdb6f7ab369ecca14a99a0064d2a11ddd2 Author: Gaius Mulley Date: Thu Mar 14 11:23:42 2024 + PR modula2/114333 set type comparison against a cardinal should cause an error The type checker

Results for 14.0.1 20240314 (experimental) [remotes/origin/HEAD r14-9460-g8f6e0814b4b] (GCC) testsuite on powerpc64le-unknown-linux-gnu

=== gcc Summary === # of expected passes179047 # of unexpected failures132 # of unexpected successes 19 # of expected failures 1614 # of unsupported tests 4186 /home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240314 (ex

Re: [PATCH 1/3] bpf: Fix CO-RE field expression builtins

Jose E. Marchesi writes: >> This patch corrects bugs within the CO-RE builtin field expression >> related builtins. >> The following bugs were identified and corrected based on the expected >> results of bpf-next selftests testsuite. >> It addresses the following problems: >> - Expressions

[Bug target/114334] New: [14 Regression] ICE: in extract_insn, at recog.cc:2812 (unrecognizable insn and:HF?) with lroundf16() and -ffast-math -mavx512fp16

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114334 Bug ID: 114334 Summary: [14 Regression] ICE: in extract_insn, at recog.cc:2812 (unrecognizable insn and:HF?) with lroundf16() and -ffast-math -mavx512fp16 Product: gcc

Results for 20240314 master r14-9461-g90a7da695284da (GCC) testsuite on aarch64-unknown-linux-gnu

$ ../configure --prefix=/home/gaius/opt --libexecdir=/home/gaius/opt/lib --enable-host-shared --enable-threads=posix --enable-clocale=gnu --enable-checking --enable-long-longx --enable-languages=m2 --disable-multilib --enable-plugin --enable-bootstrap gcc-branch: master git commit

Regressions on master at commit r14-9458 vs commit r14-9443 on Linux/x86_64

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

Re: Re: [PATCH] RISC-V: Introduce option -mrvv-autovec-max-lmul for RVV autovec

>> This PR is not really resolved or affected by the patch if I'm not >>mistaken. We still have code paths that will generate a larger LMUL >>(also in vsetvl last I checked, but that was a while ago). Ok. we should only mention PR target/112651 which is enough. >>Should it really be called

Results for 14.0.1 20240314 (experimental) [master r14-9458-g746b71e26bd] (GCC) testsuite on x86_64-pc-linux-gnu

lved testcases 2 # of unsupported tests 10715 /export/project/git/gcc-test-master-intel64/bld/gcc/xgcc version 14.0.1 20240314 (experimental) [master r14-9458-g746b71e26bd] (GCC) === gfortran tests === Running target unix === gfortran

Re: Builtin for consulting value analysis (better ffs() code gen)

* Andrew Cooper via Gcc: > Anyway - is there a way of doing this that I've managed to overlook? Use __builtin_ffs? I think there's some concern for GCC that some of the alternative x86-64 implementations do not follow the AMD and Intel behavior. Thanks, Florian

Results for 14.0.1 20240314 (experimental) [master revision gcc-14-9460-g8f6e0814b4b] (GCC) testsuite on aarch64-unknown-linux-gnu

d failures30 # of unexpected successes 10 # of expected failures 1892 # of unsupported tests 4658 /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/aarch64-unknown-linux-gnu/bin/aarch64-unknown-linux-gnu-gcc version 14.0.1 20240314 (experimental) [master rev

Re: [PATCH] RISC-V: Introduce option -mrvv-autovec-max-lmul for RVV autovec

Should it really be called autovec-max-lmul? We also use TARGET_MAX_LMUL for builtins etc. Or are we just following LLVM's naming here? Isn't -mrvv-max-lmul sufficient? > PR target/112648 This PR is not really resolved or affected by the

Results for 13.2.1 20240314 [releases/gcc-13 r13-8438-gbdbcfbfcf5] (GCC) testsuite on powerpc64le-unknown-linux-gnu

3/gcc/xgcc version 13.2.1 20240314 [releases/gcc-13 r13-8438-gbdbcfbfcf5] (GCC) === gfortran tests === Running target unix XPASS: gfortran.dg/default_format_2.f90 -O0 execution test XPASS: gfortran.dg/default_format_2.f90 -O1 execution test XPASS: gfortran.dg/default_fo

Results for 14.0.1 20240314 (experimental) [remotes/origin/HEAD r14-9459-g618e34d56c] (GCC) testsuite on powerpc64le-unknown-linux-gnu

(test for excess errors) === gcc Summary === # of expected passes178039 # of unexpected failures148 # of unexpected successes 12 # of expected failures 1597 # of unsupported tests 4965 /home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc

[PATCH] bitint, v2: Fix up adjustment of large/huge _BitInt arguments of returns_twice calls [PR113466]

On Thu, Mar 14, 2024 at 09:59:12AM +0100, Richard Biener wrote: > On Thu, 14 Mar 2024, Jakub Jelinek wrote: > > > On Thu, Mar 14, 2024 at 09:48:45AM +0100, Richard Biener wrote: > > > Ugh. OK, but I wonder whether we might want to simply delay > > > fixing the CFG for inserts before

[gcc r14-9462] OpenACC 2.7: front-end support for readonly modifier

https://gcc.gnu.org/g:ddf852dac2abaca317c10b8323f338123b0585c8 commit r14-9462-gddf852dac2abaca317c10b8323f338123b0585c8 Author: Chung-Lin Tang Date: Thu Mar 14 10:39:52 2024 + OpenACC 2.7: front-end support for readonly modifier This patch implements the front-end support

[Bug tree-optimization/114324] [13/14 Regression] AVX2 vectorisation performance regression with gfortran 13/14

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114324 --- Comment #3 from Richard Biener --- So the missed feature is to implement swapping operands of a MINUS_EXPR during SLP discovery by introducing a conditional negate (for example by multiplying with { 1, -1 } or with two_operator negate,

Re: [PATCH] vect: Call vect_convert_output with the right vecitype [PR114108]

On Thu, Mar 14, 2024 at 11:14 AM Tejas Belagod wrote: > > > Ping. > > Thanks, > Tejas. > > On 3/13/24 6:07 PM, Tejas Belagod wrote: > > Ping! > > > > On 3/7/24 4:14 PM, Tejas Belagod wrote: > >> This patch fixes a bug where vect_recog_abd_pattern called > >> vect_convert_output > >> with the

Results for 14.0.1 20240314 (experimental) [master revision gcc-14-9460-g8f6e0814b4b] (GCC) testsuite on arm-unknown-eabi

# From https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_eabi-build/424/: LAST_UPDATED: 2024-03-14T09:39:36+00:00 (master revision gcc-14-9460-g8f6e0814b4b) arm-eabi {-marm/-march=armv7-a/-mfpu=vfpv3-d16/-mfloat-abi=softfp} Target is arm-unknown-eabi Host is

Re: [PATCH] vect: Call vect_convert_output with the right vecitype [PR114108]

Ping. Thanks, Tejas. On 3/13/24 6:07 PM, Tejas Belagod wrote: Ping! On 3/7/24 4:14 PM, Tejas Belagod wrote: This patch fixes a bug where vect_recog_abd_pattern called vect_convert_output with the incorrect vecitype for the corresponding pattern_stmt. vect_convert_output expects vecitype

Results for 13.2.1 20240314 [native/releases/gcc-13 r13-8438-gbdbcfbfcf59] (GCC) testsuite on x86_64-pc-linux-gnu

LAST_UPDATED: Thu Mar 14 08:40:05 UTC 2024 (revision r13-8438-gbdbcfbfcf59) Native configuration is x86_64-pc-linux-gnu === gcc tests === Running target unix FAIL: gcc.dg/analyzer/data-model-4.c (test for excess errors) ERROR: tcl error code NONE ERROR: tcl error code NONE

Regressions on native/releases/gcc-13 at commit r13-8438 vs commit r13-8432 on Linux/x86_64

Regressions on native/releases/gcc-13 at commit r13-8438 vs commit r13-8432 on Linux/x86_64 New failures: FAIL: gcc.dg/20040622-2.c (test for excess errors) FAIL: gcc.dg/20040622-2.c (test for excess errors) FAIL: gcc.dg/analyzer/torture/conftest-1.c -O0 (test for excess errors) FAIL:

Results for 14.0.1 20240314 (experimental) [master r14-9458-g746b71e26bd433] (GCC) testsuite on aarch64-suse-linux-gnu

1 /opt/gcc/gcc-20240314/Build/./gcc/gccgo version 14.0.1 20240314 (experimental) [master r14-9458-g746b71e26bd433] (GCC) === libgomp tests === Running target unix/-mabi=lp64 === libgomp Summary === # of expected passes16260 # of expected

[Committed] IBM Z: Fix -munaligned-symbols

With this fix we make sure that only symbols with a natural alignment smaller than 2 are considered misaligned with -munaligned-symbols. Background is that -munaligned-symbols is only supposed to affect symbols whose natural alignment wouldn't be enough to fulfill our ABI requirement of having all

[gcc r14-9461] IBM Z: Fix -munaligned-symbols

https://gcc.gnu.org/g:90a7da695284da49182446ba45fbcddb9eb7fc91 commit r14-9461-g90a7da695284da49182446ba45fbcddb9eb7fc91 Author: Andreas Krebbel Date: Thu Mar 14 09:54:31 2024 +0100 IBM Z: Fix -munaligned-symbols With this fix we make sure that only symbols with a natural

Results for 14.0.1 20240314 (experimental) [remotes/origin/HEAD r14-9459-g618e34d56c] (GCC) testsuite on powerpc64le-unknown-linux-gnu

Summary === # of expected passes179047 # of unexpected failures116 # of unexpected successes 19 # of expected failures 1614 # of unsupported tests 4188 /home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240314 (experimental) [remote

[Bug libfortran/114304] [13/14 Regression] libgfortran I/O – bogus "Semicolon not allowed as separator with DECIMAL='point'"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114304 --- Comment #19 from Tobias Burnus --- Regarding the LAPACK issue: Actually, I am inclined to * regard it as LAPACK bug * that was also fixed upstream, see comment 6, to make g95 happy. as ';' is not a value separator - while ' ;' is fine,

Results for 14.0.1 20240314 (experimental) [remotes/origin/HEAD r14-9459-g618e34d56cc] (GCC) testsuite on powerpc64le-unknown-linux-gnu

=== gcc Summary === # of expected passes179047 # of unexpected failures132 # of unexpected successes 19 # of expected failures 1614 # of unsupported tests 4186 /home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240314 (ex

[PATCH v2] match.pd: Only merge truncation with conversion for -fno-signed-zeros

This optimisation does not honour signed zeros, so should not be enabled except with -fno-signed-zeros. OK for master? I do not have commit rights for GCC, so if the patch is fine would someone be able to commit for me? The bug is present in all GCC versions from 12.1.0 onwards - is it possible

[Bug fortran/105473] semicolon allowed when list-directed read integer with decimal='point'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473 Tobias Burnus changed: What|Removed |Added Attachment #57693|0 |1 is obsolete|

[Bug modula2/114333] set type comparison against a cardinal should cause an error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114333 --- Comment #2 from Gaius Mulley --- Created attachment 57694 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57694=edit Proposed fix Here is a proposed fix. The fixes were mainly made in M2Check.mod with a few checking calls made in

[Bug fortran/111853] f951: Segmentation fault at gfc_expression_rank

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111853 Francois-Xavier Coudert changed: What|Removed |Added CC||fxcoudert at gcc dot gnu.org

Re: [PATCH] bitint: Fix up adjustment of large/huge _BitInt arguments of returns_twice calls [PR113466]

On Thu, 14 Mar 2024, Jakub Jelinek wrote: > On Thu, Mar 14, 2024 at 09:48:45AM +0100, Richard Biener wrote: > > Ugh. OK, but I wonder whether we might want to simply delay > > fixing the CFG for inserts before returns-twice? Would that make > > things less ugly? > > You mean in lower_call just

[Bug modula2/114333] set type comparison against a cardinal should cause an error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114333 Gaius Mulley changed: What|Removed |Added Last reconfirmed||2024-03-14 Ever confirmed|0

[gcc r14-9460] gimple-iterator: Some gsi_safe_insert_*before fixes

https://gcc.gnu.org/g:8f6e0814b4bfd0a399055e9214562aebfcd902ad commit r14-9460-g8f6e0814b4bfd0a399055e9214562aebfcd902ad Author: Jakub Jelinek Date: Thu Mar 14 09:57:13 2024 +0100 gimple-iterator: Some gsi_safe_insert_*before fixes When trying to use the gsi_safe_insert*before

Re: [PATCH 1/3] bpf: Fix CO-RE field expression builtins

> This patch corrects bugs within the CO-RE builtin field expression > related builtins. > The following bugs were identified and corrected based on the expected > results of bpf-next selftests testsuite. > It addresses the following problems: > - Expressions with pointer dereferencing now

Re: [PATCH] bitint: Fix up adjustment of large/huge _BitInt arguments of returns_twice calls [PR113466]

On Thu, Mar 14, 2024 at 09:48:45AM +0100, Richard Biener wrote: > Ugh. OK, but I wonder whether we might want to simply delay > fixing the CFG for inserts before returns-twice? Would that make > things less ugly? You mean in lower_call just remember if we added anything before ECF_RETURNS_TWICE

Re: [PATCH] bitint: Fix up adjustment of large/huge _BitInt arguments of returns_twice calls [PR113466]

On Thu, 14 Mar 2024, Jakub Jelinek wrote: > Hi! > > This patch (on top of the just posted gsi_safe_insert* fixes patch) > fixes the instrumentation of large/huge _BitInt SSA_NAME arguments of > returns_twice calls. > > In this case it isn't just a matter of using gsi_safe_insert_before instead

Results for 12.3.1 20240314 [remotes/origin/releases/gcc-12 r12-10213-g3a23863d1b] (GCC) testsuite on powerpc64le-unknown-linux-gnu

2078 # 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 20240314 [remotes/origin/releases/gcc-12 r12-10213-g3a23863d1b] (GCC)

Re: [PATCH] gimple-iterator: Some gsi_safe_insert_*before fixes

On Thu, 14 Mar 2024, Jakub Jelinek wrote: > Hi! > > When trying to use the gsi_safe_insert*before APIs in bitint lowering, > I've discovered 3 issues and the following patch addresses those: > > 1) both split_block and split_edge update CDI_DOMINATORS if they are >available, but because

[Bug tree-optimization/114331] Missed optimization: indicate knownbits from dominating condition switch(trunc(a))

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114331 --- Comment #2 from Jakub Jelinek --- I thought we don't, if the testcase starts with void dummy (void); short int foo (void); int src(void) { short int num = foo (); switch(num){ instead then evrp1 optimizes away the BIT_AND_EXPR.

[Bug fortran/105473] semicolon allowed when list-directed read integer with decimal='point'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473 --- Comment #34 from Tobias Burnus --- Created attachment 57693 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57693=edit Extended testcase; comment shows results for gfortran(trunk),ifort,ifx,flang See PR114304 for some related issue

[Bug modula2/114333] New: set type comparison against a cardinal should cause an error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114333 Bug ID: 114333 Summary: set type comparison against a cardinal should cause an error Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[PATCH] aarch64: Fix TImode __sync_*_compare_and_exchange expansion with LSE [PR114310]

Hi! The following testcase ICEs with LSE atomics. The problem is that the @atomic_compare_and_swap expander uses aarch64_reg_or_zero predicate for the desired operand, which is fine, given that for most of the modes and even for TImode in some cases it can handle zero immediate just fine, but the

[Bug tree-optimization/114331] Missed optimization: indicate knownbits from dominating condition switch(trunc(a))

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

[Bug tree-optimization/114324] [13/14 Regression] AVX2 vectorisation performance regression with gfortran 13/14

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114324 Richard Biener changed: What|Removed |Added Target Milestone|12.4|13.3 CC|

[Bug tree-optimization/114324] [13/14 Regression] AVX2 vectorisation performance regression with gfortran 13/14

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114324 Richard Biener changed: What|Removed |Added Priority|P3 |P2 --- Comment #2 from Richard Biener

[PATCH] bitint: Fix up adjustment of large/huge _BitInt arguments of returns_twice calls [PR113466]

Hi! This patch (on top of the just posted gsi_safe_insert* fixes patch) fixes the instrumentation of large/huge _BitInt SSA_NAME arguments of returns_twice calls. In this case it isn't just a matter of using gsi_safe_insert_before instead of gsi_insert_before, we need to do more. One thing is

[PATCH] gimple-iterator: Some gsi_safe_insert_*before fixes

Hi! When trying to use the gsi_safe_insert*before APIs in bitint lowering, I've discovered 3 issues and the following patch addresses those: 1) both split_block and split_edge update CDI_DOMINATORS if they are available, but because edge_before_returns_twice_call first splits and then adds

[Bug target/111822] [12/13/14 Regression] during RTL pass: lr_shrinkage ICE: in operator[], at vec.h:910 with -O2 -m32 -flive-range-shrinkage -fno-dce -fnon-call-exceptions since r12-5301-g04520645038

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111822 Hongtao Liu changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[gcc r12-10214] i386[stv]: Handle REG_EH_REGION note

https://gcc.gnu.org/g:a861f940efffae2782c559cd04df2d2740cd28bd commit r12-10214-ga861f940efffae2782c559cd04df2d2740cd28bd Author: liuhongt Date: Wed Mar 13 10:40:01 2024 +0800 i386[stv]: Handle REG_EH_REGION note When we split (insn 37 36 38 10 (set (reg:DI 104 [ _18 ])

Re: [PATCH v2] gcc, libcpp: Add warning switch for "#pragma once in main file" [PR89808]

On Sat, Mar 2, 2024 at 5:04 AM Ken Matsui wrote: > > This patch adds a warning switch for "#pragma once in main file". The > warning option name is Wpragma-once-outside-header, which is the same > as Clang. Ping. > > PR preprocessor/89808 > > gcc/c-family/ChangeLog: > > *

Re: [PATCH] LoongArch: Remove unused and incorrect "sge_" define_insn

在 2024/3/13 下午9:03, Xi Ruoyao 写道: If this insn is really used, we'll have something like slti $r4,$r0,$r5 in the code. The assembler will reject it because slti wants 2 register operands and 1 immediate operand. But we've not got any bug report for this, indicating this define_insn is

Re: [PATCH] contrib/gcc-changelog/git_check_commit.py: Implement --num-commits

On Fri, Mar 8, 2024 at 8:42 AM Patrick Palka wrote: > > On Wed, 28 Feb 2024, Ken Matsui wrote: > > > This patch implements a --num-commits (-n) flag for shorthand for > > the range of hash~N..hash commits. Ping. > > > > contrib/ChangeLog: > > > > * gcc-changelog/git_check_commit.py:

[gcc r13-8438] i386[stv]: Handle REG_EH_REGION note

https://gcc.gnu.org/g:bdbcfbfcf591381f0faf95c881e3772b56d0a404 commit r13-8438-gbdbcfbfcf591381f0faf95c881e3772b56d0a404 Author: liuhongt Date: Wed Mar 13 10:40:01 2024 +0800 i386[stv]: Handle REG_EH_REGION note When we split (insn 37 36 38 10 (set (reg:DI 104 [ _18 ])

[gcc r14-9459] i386[stv]: Handle REG_EH_REGION note

https://gcc.gnu.org/g:618e34d56cc38e9c3ae95a413228068e53ed76bb commit r14-9459-g618e34d56cc38e9c3ae95a413228068e53ed76bb Author: liuhongt Date: Wed Mar 13 10:40:01 2024 +0800 i386[stv]: Handle REG_EH_REGION note When we split (insn 37 36 38 10 (set (reg:DI 104 [ _18 ])

[Bug target/114323] [14 Regression] MVE vector load intrinsic miscompiled since r14-5622-g4d7647edfd7d98

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114323 Christophe Lyon changed: What|Removed |Added Last reconfirmed||2024-03-14

Re: [PATCH V12]: Improve code sinking pass

On Wed, Mar 13, 2024 at 9:27 PM Jeff Law wrote: > > > > On 3/13/24 4:22 AM, Richard Biener wrote: > > > > > ... this hunk is OK (please test and split it out separatley). In the > > spirit of > > moving the stmt the least amount (in this case not schedule it within the > > basic-block). In the

Re: [PATCH] i386[stv]: Handle REG_EH_REGION note

On Thu, Mar 14, 2024 at 8:32 AM Hongtao Liu wrote: > > On Thu, Mar 14, 2024 at 3:22 PM Uros Bizjak wrote: > > > > On Thu, Mar 14, 2024 at 2:33 AM liuhongt wrote: > > > > > > When we split > > > (insn 37 36 38 10 (set (reg:DI 104 [ _18 ]) > > > (mem:DI (reg/f:SI 98 [

Re: [PATCH v2 01/12] extend.texi: Arrange pre-existing built-in traits alphabetically

On Thu, Mar 14, 2024 at 12:28 AM Ken Matsui wrote: > > Ok for trunk? It appears that my update notes have somehow vanished. I have rectified several inconsistencies and introduced sub-sections to enhance readability. Although I contemplated merging certain patches for a more streamlined

Re: [PATCH] match.pd: Only merge truncation with conversion for -fno-signed-zeros

On Wed, Mar 13, 2024 at 3:39 PM Joe Ramsay wrote: > > This optimisation does not honour signed zeros, so should not be > enabled except with -fno-signed-zeros. > > OK for master? I do not have commit rights for GCC, so if the patch > is fine would someone be able to commit for me? The bug is

[PATCH v2 02/12] extend.texi: Add documentation for __is_array

gcc/ChangeLog: * doc/extend.texi (__is_array): New documentation. Signed-off-by: Ken Matsui --- gcc/doc/extend.texi | 5 + 1 file changed, 5 insertions(+) diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index b13f9d6f934..5aeb9bdd47a 100644 --- a/gcc/doc/extend.texi +++

Re: [PATCH] i386[stv]: Handle REG_EH_REGION note

On Thu, Mar 14, 2024 at 3:22 PM Uros Bizjak wrote: > > On Thu, Mar 14, 2024 at 2:33 AM liuhongt wrote: > > > > When we split > > (insn 37 36 38 10 (set (reg:DI 104 [ _18 ]) > > (mem:DI (reg/f:SI 98 [ CallNative_nclosure.0_1 ]) [6 MEM[(struct > > SQRefCounted

[PATCH v2 04/12] extend.texi: Add documentation for __is_function

gcc/ChangeLog: * doc/extend.texi (__is_function): New documentation. Signed-off-by: Ken Matsui --- gcc/doc/extend.texi | 5 + 1 file changed, 5 insertions(+) diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index ae06e4da022..a94ad7955fe 100644 --- a/gcc/doc/extend.texi +++

[PATCH v2 11/12] extend.texi: Add documentation for __remove_pointer

gcc/ChangeLog: * doc/extend.texi (__remove_pointer): New documentation. Signed-off-by: Ken Matsui --- gcc/doc/extend.texi | 5 + 1 file changed, 5 insertions(+) diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index e4a4060be2b..10ddf50182d 100644 --- a/gcc/doc/extend.texi

[PATCH v2 12/12] extend.texi: Add subsections for type- and expression-yielding traits

gcc/ChangeLog: * doc/extend.texi (Expression-yielding Type Traits): New subsection. (Type-yielding Type Traits): Likewise. (__remove_pointer): Move under the Type-yielding Type Traits subsection. Signed-off-by: Ken Matsui --- gcc/doc/extend.texi | 18

[PATCH v2 07/12] extend.texi: Add documentation for __is_member_pointer

gcc/ChangeLog: * doc/extend.texi (__is_member_pointer): New documentation. Signed-off-by: Ken Matsui --- gcc/doc/extend.texi | 5 + 1 file changed, 5 insertions(+) diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index 7644ea5b80b..86ac0c7ed07 100644 ---

[PATCH v2 09/12] extend.texi: Add documentation for __is_reference

gcc/ChangeLog: * doc/extend.texi (__is_reference): New documentation. Signed-off-by: Ken Matsui --- gcc/doc/extend.texi | 5 + 1 file changed, 5 insertions(+) diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index 293eb5706f9..6af5294c7b0 100644 --- a/gcc/doc/extend.texi +++

[PATCH v2 08/12] extend.texi: Add documentation for __is_object

gcc/ChangeLog: * doc/extend.texi (__is_object): New documentation. Signed-off-by: Ken Matsui --- gcc/doc/extend.texi | 5 + 1 file changed, 5 insertions(+) diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index 86ac0c7ed07..293eb5706f9 100644 --- a/gcc/doc/extend.texi +++

[PATCH v2 01/12] extend.texi: Arrange pre-existing built-in traits alphabetically

Ok for trunk? -- >8 -- This patch arranges pre-existing built-in traits alphabetically for better codebase consistency and easier future integration of changes. gcc/ChangeLog: * doc/extend.texi (Type Traits): Arrange pre-existing built-in traits alphabetically. Signed-off-by:

[PATCH v2 06/12] extend.texi: Add documentation for __is_member_object_pointer

gcc/ChangeLog: * doc/extend.texi (__is_member_object_pointer): New documentation. Signed-off-by: Ken Matsui --- gcc/doc/extend.texi | 5 + 1 file changed, 5 insertions(+) diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index f08574318d0..7644ea5b80b 100644 ---

[PATCH v2 03/12] extend.texi: Add documentation for __is_bounded_array

gcc/ChangeLog: * doc/extend.texi (__is_bounded_array): New documentation. (__is_array): Add @anchor to get linked from __is_bounded_array. Signed-off-by: Ken Matsui --- gcc/doc/extend.texi | 9 + 1 file changed, 9 insertions(+) diff --git a/gcc/doc/extend.texi

[PATCH v2 05/12] extend.texi: Add documentation for __is_member_function_pointer

gcc/ChangeLog: * doc/extend.texi (__is_member_function_pointer): New documentation. Signed-off-by: Ken Matsui --- gcc/doc/extend.texi | 5 + 1 file changed, 5 insertions(+) diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index a94ad7955fe..f08574318d0 100644 ---

<    1   2   3   4   5   >