Re: [pushed][PATCH] LoongArch: Improve lasx_xvpermi_q_ insn pattern

Pushed to r14-6968. 在 2024/1/5 下午3:37, Jiahao Xu 写道: For instruction xvpermi.q, unused bits in operands[3] need be set to 0 to avoid causing undefined behavior on LA464. gcc/ChangeLog: * config/loongarch/lasx.md: Set the unused bits in operand[3] to 0. gcc/testsuite/ChangeLog:

[Bug middle-end/88670] [meta-bug] generic vector extension issues

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88670 Bug 88670 depends on bug 112787, which changed state. Bug 112787 Summary: Codegen regression of large GCC vector extensions when enabling SVE https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112787 What|Removed

[Bug target/112787] Codegen regression of large GCC vector extensions when enabling SVE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112787 Andrew Pinski changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libgomp/113192] [11/12/13/14 Regression] ERROR: couldn't execute "../../../gcc/libgomp/testsuite/flock": no such file or directory

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113192 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |11.5

[Bug target/113116] [14 Regression] ~11-17% exec time regression of 436.cactusADM on aarch64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113116 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |14.0

[Bug middle-end/113199] [14 Regression][GCN] ICE (segfault) due to invalid 'loop_mask_46 = VEC_PERM_EXPR' when compiling Newlib's wcsftime.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113199 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |14.0

[Bug lto/113208] [14 Regression] lto1: error: Alias and target's comdat groups differs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113208 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |14.0

[Bug lto/113204] [14 Regression] lto1: error: qsort comparator non-negative on sorted output: 64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113204 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |14.0

[Bug middle-end/113163] [14 Regression][GCN] ICE in vect_peel_nonlinear_iv_init, at tree-vect-loop.cc:9420

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113163 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |14.0

[Bug sanitizer/105347] [12/13/14 Regression] Failed to build from source on FreeBSD 11.* due to using nonexistent sha224.h

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105347 --- Comment #2 from Andrew Pinski --- https://github.com/llvm/llvm-project/commit/18a7ebda99044473fdbce6376993714ff54e6690

[Bug sanitizer/105347] [12/13/14 Regression] Failed to build from source on FreeBSD 11.* due to using nonexistent sha224.h

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105347 Andrew Pinski changed: What|Removed |Added Keywords||build Summary|Failed to

[Bug other/113188] graphite-isl-ast-to-gimple.c: ‘isl_val_free’ was not declared in this scope

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113188 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug bootstrap/113181] When compiling sanitizer_printf.cc, getting error: multiple definition of ‘enum fsconfig_command’

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113181 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug target/113248] RISC-V: Invalid vsetvli fusion using -mtune=generic-ooo

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113248 --- Comment #1 from GCC Commits --- The master branch has been updated by Pan Li : https://gcc.gnu.org/g:6cf47447f6fba84a17864fc7a19a532a62b6e736 commit r14-6967-g6cf47447f6fba84a17864fc7a19a532a62b6e736 Author: Juzhe-Zhong Date: Sat Jan 6

[Committed] RISC-V: Update MAX_SEW for available vsevl info[VSETVL PASS]

This patch fixes a bug of VSETVL PASS in this following situation: Ignore curr info since prev info available with it: prev_info: VALID (insn 8, bb 2) Demand fields: demand_ratio_and_ge_sew demand_avl SEW=16, VLMUL=mf4, RATIO=64, MAX_SEW=64 TAIL_POLICY=agnostic,

[PATCH v3 8/8] libstdc++: Optimize std::is_unbounded_array compilation performance

This patch optimizes the compilation performance of std::is_unbounded_array by dispatching to the new __is_unbounded_array built-in trait. libstdc++-v3/ChangeLog: * include/std/type_traits (is_unbounded_array_v): Use __is_unbounded_array built-in trait. Signed-off-by: Ken Matsui

[PATCH v3 1/8] c++: Implement __is_const built-in trait

This patch implements built-in trait for std::is_const. gcc/cp/ChangeLog: * cp-trait.def: Define __is_const. * constraint.cc (diagnose_trait_expr): Handle CPTK_IS_CONST. * semantics.cc (trait_expr_value): Likewise. (finish_trait_expr): Likewise.

[PATCH v3 6/8] libstdc++: Optimize std::is_pointer compilation performance

This patch optimizes the compilation performance of std::is_pointer by dispatching to the new __is_pointer built-in trait. libstdc++-v3/ChangeLog: * include/bits/cpp_type_traits.h (__is_pointer): Use __is_pointer built-in trait. Optimize its implementation. *

[PATCH v3 5/8] c++: Implement __is_pointer built-in trait

This patch implements built-in trait for std::is_pointer. gcc/cp/ChangeLog: * cp-trait.def: Define __is_pointer. * constraint.cc (diagnose_trait_expr): Handle CPTK_IS_POINTER. * semantics.cc (trait_expr_value): Likewise. (finish_trait_expr): Likewise.

[PATCH v3 7/8] c++: Implement __is_unbounded_array built-in trait

This patch implements built-in trait for std::is_unbounded_array. gcc/cp/ChangeLog: * cp-trait.def: Define __is_unbounded_array. * constraint.cc (diagnose_trait_expr): Handle CPTK_IS_UNBOUNDED_ARRAY. * semantics.cc (trait_expr_value): Likewise.

[PATCH v3 4/8] libstdc++: Optimize std::is_volatile compilation performance

This patch optimizes the compilation performance of std::is_volatile by dispatching to the new __is_volatile built-in trait. libstdc++-v3/ChangeLog: * include/std/type_traits (is_volatile): Use __is_volatile built-in trait. (is_volatile_v): Likewise. Signed-off-by: Ken

[PATCH v3 3/8] c++: Implement __is_volatile built-in trait

This patch implements built-in trait for std::is_volatile. gcc/cp/ChangeLog: * cp-trait.def: Define __is_volatile. * constraint.cc (diagnose_trait_expr): Handle CPTK_IS_VOLATILE. * semantics.cc (trait_expr_value): Likewise. (finish_trait_expr): Likewise.

[PATCH v3 2/8] libstdc++: Optimize std::is_const compilation performance

This patch optimizes the compilation performance of std::is_const by dispatching to the new __is_const built-in trait. libstdc++-v3/ChangeLog: * include/std/type_traits (is_const): Use __is_const built-in trait. (is_const_v): Likewise. Signed-off-by: Ken Matsui ---

[PATCH v3 0/8] Optimize more type traits

Changes in v3: - Rebased on top of master. - Fixed __is_pointer in cpp_type_traits.h. Changes in v2: - Removed testsuite_tr1.h includes from the testcases. --- This patch series implements __is_const, __is_volatile, __is_pointer, and __is_unbounded_array built-in traits, which were isolated

Re: [PATCH v2 6/8] libstdc++: Optimize std::is_pointer compilation performance

On Thu, Jan 4, 2024 at 2:13 PM Jonathan Wakely wrote: > > On Sat, 23 Dec 2023 at 22:07, Ken Matsui wrote: > > > > This patch optimizes the compilation performance of std::is_pointer > > by dispatching to the new __is_pointer built-in trait. > > > > libstdc++-v3/ChangeLog: > > > > *

Re: [PATCH v2 6/8] libstdc++: Optimize std::is_pointer compilation performance

On Thu, Jan 4, 2024 at 2:16 PM Patrick Palka wrote: > > On Thu, 4 Jan 2024, Patrick Palka wrote: > > > On Sat, 23 Dec 2023, Ken Matsui wrote: > > > > > This patch optimizes the compilation performance of std::is_pointer > > > by dispatching to the new __is_pointer built-in trait. > > > > > >

[Committed V2] RISC-V: Teach liveness computation loop invariant shift amount

1). We not only have vashl_optab,vashr_optab,vlshr_optab which vectorize shift with vector shift amount, that is, vectorization of 'a[i] >> x[i]', the shift amount is loop variant. 2). But also, we have ashl_optab, ashr_optab, lshr_optab which can vectorize shift with scalar shift amount, that

Re: Re: [PATCH] RISC-V: Teach liveness computation loop invariant shift amount[Dynamic LMUL]

Thanks Robin. is_gimple_constant makes more senes. Committed with addressing your comments. juzhe.zh...@rivai.ai From: Robin Dapp Date: 2024-01-05 17:54 To: Juzhe-Zhong; gcc-patches CC: rdapp.gcc; kito.cheng; kito.cheng; jeffreyalaw Subject: Re: [PATCH] RISC-V: Teach liveness computation

[Committed V2] RISC-V: Allow simplification non-vlmax with len = NUNITS reg to reg move

V2: Address comments from Robin. While working on fixing a bug, I notice this following code has redundant move: #include "riscv_vector.h" void f (float x, float y, void *out) { float f[4] = { x, x, x, y }; vfloat32m1_t v = __riscv_vle32_v_f32m1 (f, 4); __riscv_vse32_v_f32m1 (out, v, 4); }

[Bug libstdc++/106308] Consider using statx(2) for std::filesystem

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

Re: [committed] RISC-V: Clean up testsuite for multi-lib testing [NFC]

Hi, kito. This patch causes these following regression FAILs: FAIL: gcc.target/riscv/rvv/autovec/partial/single_rgroup_run-3.c (test for excess errors) FAIL: gcc.target/riscv/rvv/autovec/partial/single_rgroup_run-3.c (test for excess errors) FAIL:

[Bug libstdc++/113250] New: std::filesystem::equivalent("", "/") should throw

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113250 Bug ID: 113250 Summary: std::filesystem::equivalent("", "/") should throw Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug target/113249] New: RISC-V: regression testsuite errors -mtune=generic-ooo

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113249 Bug ID: 113249 Summary: RISC-V: regression testsuite errors -mtune=generic-ooo Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug libstdc++/113246] Behavior of std::filesystem::weakly_canonical with non-existing relative paths

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113246 --- Comment #5 from Davide Pesavento --- (In reply to Jonathan Wakely from comment #2) > > If there are no leading elements of p that exist, should canonical() be > > called with an empty path? or should it not be called at all? > > It makes

[Bug target/113248] New: RISC-V: Invalid vsetvli fusion using -mtune=generic-ooo

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113248 Bug ID: 113248 Summary: RISC-V: Invalid vsetvli fusion using -mtune=generic-ooo Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug libstdc++/113246] Behavior of std::filesystem::weakly_canonical with non-existing relative paths

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113246 --- Comment #4 from Jonathan Wakely --- I think the exception for a deleted pwd is also correct. weakly_canonical uses status(".") to check if the current directory exists. That returns true, even if the directory has been deleted (it still

[Bug libstdc++/113246] Behavior of std::filesystem::weakly_canonical with non-existing relative paths

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113246 --- Comment #3 from Jonathan Wakely --- (In reply to Davide Pesavento from comment #1) > Another interesting(?) behavior, when run from a non-existing (deleted) > working directory: > > weakly_canonical("foo") returns "foo", while

[COMMITTED] Regenerate libgomp/configure for copyright year update

commit a945c346f57ba40fc80c14ac59be0d43624e559d updated libgomp/plugin/configfrag.ac but didn't regenerate/update libgomp/configure which includes that configfrag. libgomp/Changelog: * configure: Regenerate. --- libgomp/configure | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[Bug libstdc++/113246] Behavior of std::filesystem::weakly_canonical with non-existing relative paths

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113246 --- Comment #2 from Jonathan Wakely --- (In reply to Davide Pesavento from comment #0) > note that canonical("") currently throws a filesystem_error) That's clearly correct, as canonical says that !exists(p) is an error. > If there are no

[Bug c/113247] New: RISC-V: Performance bug in SHA256

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113247 Bug ID: 113247 Summary: RISC-V: Performance bug in SHA256 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

Re: Re: [committed] RISC-V: Add crypto vector builtin function.

Thanks Jeff. Yeah, I aggree we are not doing thing terribly wrong but Palmer request revert of the vector-crypto, so I revert it (actually, I asked Li Pan revert it). Actually, Wang Feng has fixed the issue: https://gcc.gnu.org/pipermail/gcc-patches/2024-January/641903.html It's just a pretty

Repost [PATCH 6/6] PowerPC: Add support for 1,024 bit DMR registers.

This patch is a prelimianry patch to add the full 1,024 bit dense math register (DMRs) for -mcpu=future. The MMA 512-bit accumulators map onto the top of the DMR register. This patch only adds the new 1,024 bit register support. It does not add support for any instructions that need 1,024 bit

Repost [PATCH 5/6] PowerPC: Switch to dense math names for all MMA operations.

This patch changes the assembler instruction names for MMA instructions from the original name used in power10 to the new name when used with the dense math system. I.e. xvf64gerpp becomes dmxvf64gerpp. The assembler will emit the same bits for either spelling. The patches have been tested on

Repost [PATCH 4/6] PowerPC: Make MMA insns support DMR registers.

This patch changes the MMA instructions to use either FPR registers (-mcpu=power10) or DMRs (-mcpu=future). In this patch, the existing MMA instruction names are used. A macro (__PPC_DMR__) is defined if the MMA instructions use the DMRs. The patches have been tested on both little and big

Repost [PATCH 3/6] PowerPC: Add support for accumulators in DMR registers.

The MMA subsystem added the notion of accumulator registers as an optional feature of ISA 3.1 (power10). In ISA 3.1, these accumulators overlapped with the traditional floating point registers 0..31, but logically the accumulator registers were separate from the FPR registers. In ISA 3.1, it was

Repost [PATCH 2/6] PowerPC: Make -mcpu=future enable -mblock-ops-vector-pair.

This patch re-enables generating load and store vector pair instructions when doing certain memory copy operations when -mcpu=future is used. During power10 development, it was determined that using store vector pair instructions were problematical in a few cases, so we disabled generating load

Repost [PATCH 1/6] Add -mcpu=future

This patch implements support for a potential future PowerPC cpu. Features added with -mcpu=future, may or may not be added to new PowerPC processors. This patch adds support for the -mcpu=future option. If you use -mcpu=future, the macro __ARCH_PWR_FUTURE__ is defined, and the assembler

[Bug c++/109899] [12/13/14 Regression] ICE in check_noexcept_r, at cp/except.cc:1065

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109899 Roman Lozko changed: What|Removed |Added CC||lozko.roma at gmail dot com --- Comment

Repost [PATCH 0/6] PowerPC Future patches

I posted these patches on October 18th, 2023, and I never receieved any feedback on the changes. What changes do I need to make with these patches to get them into GCC 14? This patch is very preliminary support for a potential new feature to the PowerPC that extends the current power10 MMA

gcc-12-20240105 is now available

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

[Bug tree-optimization/111268] [11/12/13/14 Regression] internal compiler error: in to_constant, at poly-int.h:504

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111268 Andrew Pinski changed: What|Removed |Added Known to work|12.3.0 | Summary|[14 Regression]

[Bug middle-end/113228] [14 Regression] ICE: recalculate_side_effects, at gimplify.cc:3347 since r14-6420

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113228 --- Comment #14 from Andrew Pinski --- (In reply to Jakub Jelinek from comment #12) > The reason why late gimplification/regimplification generally works fine > with SSA_NAMEs is that the > case SSA_NAME: > /* Allow callbacks

[Bug target/113229] [14 Regression] gcc.dg/torture/pr70083.c ICEs when compiled with -march=armv9-a+sve2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113229 --- Comment #7 from Andrew Pinski --- (In reply to avieira from comment #6) > Oh forgot to mention, this is triggering because of the div optimization in: > https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git; >

[PATCH] PR target/112886, Add %S to print_operand for vector pair support

In looking at support for load vector pair and store vector pair for the PowerPC in GCC, I noticed that we were missing a print_operand output modifier if you are dealing with vector pairs to print the 2nd register in the vector pair. If the instruction inside of the asm used the Altivec

[Bug libstdc++/113246] Behavior of std::filesystem::weakly_canonical with non-existing relative paths

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113246 --- Comment #1 from Davide Pesavento --- Another interesting(?) behavior, when run from a non-existing (deleted) working directory: weakly_canonical("foo") returns "foo", while weakly_canonical("./foo") throws: > terminate called after

[Bug sanitizer/113244] Potential thread sanitizer false positive with future exception

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113244 --- Comment #1 from Andrew Pinski --- I suspect this is because libstdc++.so is NOT instrumented for TSAN.

[Bug fortran/96724] Bogus warnings with the repeat intrinsic and the flag -Wconversion-extra

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96724 --- Comment #4 from anlauf at gcc dot gnu.org --- Submitted: https://gcc.gnu.org/pipermail/fortran/2024-January/060090.html

[PATCH] Fortran: bogus warnings with REPEAT intrinsic and -Wconversion-extra [PR96724]

Dear all, the attached patch picks up a submission by Jose that was never reviewed: https://gcc.gnu.org/pipermail/fortran/2020-August/054902.html The original patch was unnecessarily complex, as it could invoke more conversions than necessary. I chose to only convert to the essential - and

[Bug middle-end/79704] [meta-bug] Phoronix Test Suite compiler performance issues

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79704 Bug 79704 depends on bug 109811, which changed state. Bug 109811 Summary: libjxl 0.7 is a lot slower in GCC 13.1 vs Clang 16 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109811 What|Removed |Added

[Bug target/109811] libjxl 0.7 is a lot slower in GCC 13.1 vs Clang 16

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109811 Jan Hubicka changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libstdc++/113246] New: Behavior of std::filesystem::weakly_canonical with non-existing relative paths

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113246 Bug ID: 113246 Summary: Behavior of std::filesystem::weakly_canonical with non-existing relative paths Product: gcc Version: 13.2.0 Status: UNCONFIRMED

[Bug target/113236] WebP benchmark is 20% slower vs. Clang on AMD Zen 4

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

[Bug fortran/96724] Bogus warnings with the repeat intrinsic and the flag -Wconversion-extra

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96724 anlauf at gcc dot gnu.org changed: What|Removed |Added CC||anlauf at gcc dot gnu.org

[Bug target/113235] SMHasher SHA3-256 benchmark is almost 40% slower vs. Clang (not enough complete loop peeling)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113235 --- Comment #6 from Jan Hubicka --- The internal loops are: static const unsigned keccakf_rotc[24] = { 1, 3, 6, 10, 15, 21, 28, 36, 45, 55, 2, 14, 27, 41, 56, 8, 25, 43, 62, 18, 39, 61, 20, 44 }; static const unsigned keccakf_piln[24] = {

[Bug target/113235] SMHasher SHA3-256 benchmark is almost 40% slower vs. Clang (not enough complete loop peeling)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113235 Jan Hubicka changed: What|Removed |Added Summary|SMHasher SHA3-256 benchmark |SMHasher SHA3-256 benchmark

[PATCH] c++: reference variable as default targ [PR101463]

Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for trunk? -- >8 -- Here during default template argument substitution we wrongly consider the (substituted) default arguments v and vt as value-dependent[1] which ultimately leads to deduction failure for the calls. The bogus

[Bug fortran/67972] Substrings of arrays of unicode strings are of type DEFAULT rather than ISO_10646

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67972 anlauf at gcc dot gnu.org changed: What|Removed |Added Resolution|--- |FIXED

[Bug target/113235] SMHasher SHA3-256 benchmark is almost 40% slower vs. Clang

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113235 Jan Hubicka changed: What|Removed |Added CC||hubicka at gcc dot gnu.org --- Comment

[Bug fortran/93948] Surprising option processing of -fdec and -fdec-math in combination with -std

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93948 anlauf at gcc dot gnu.org changed: What|Removed |Added Resolution|--- |FIXED

Re: [PATCH] libgccjit: Add support for setting the comment ident

On Fri, 2024-01-05 at 12:09 -0500, Antoni Boucher wrote: > Hi. > This patch adds support for setting the comment ident (analogous to > #ident "comment" in C). > Thanks for the review. Thanks for the patch. This may sound like a silly question, but what does #ident do and what is it used for?

[Bug fortran/113245] SIZE with optional DIM argument that has the OPTIONAL+VALUE attributes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113245 anlauf at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4 Keywords|

[Bug fortran/113245] New: SIZE with optional DIM argument that has the OPTIONAL+VALUE attributes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113245 Bug ID: 113245 Summary: SIZE with optional DIM argument that has the OPTIONAL+VALUE attributes Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug libstdc++/108976] codecvt for Unicode allows surrogate code points

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976 --- Comment #10 from Jonathan Wakely --- I think it would be good to backport it, what do you think?

[patch] omp_target_is_accessible (was: [patch] libgomp.texi: Document omp_display_env)

Hi all, updated patch attached - which also fixes some additional issues and adds omp_target_is_accessible. On 03.01.24 23:35, Sandra Loosemore wrote: On 1/3/24 11:31, Tobias Burnus wrote: [...] I'm not sure about the usability issues, except I think it's generally easier to change an

[Bug debug/78100] DWARF symbols for an array sometimes missing the array length

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78100 --- Comment #4 from Dima Kogan --- I just tried again, and I see that this bug has been fixed. I'm using gcc (Debian 13.2.0-2) 13.2.0 Should we close this report?

[PATCH v2 2/2] arm: Add support for MVE Tail-Predicated Low Overhead Loops

Respin after comments on first version. diff --git a/gcc/config/arm/arm-protos.h b/gcc/config/arm/arm-protos.h index 2f5ca79ed8d..4f164c54740 100644 --- a/gcc/config/arm/arm-protos.h +++ b/gcc/config/arm/arm-protos.h @@ -65,8 +65,8 @@ extern void arm_emit_speculation_barrier_function (void);

[PATCH v2 1/2] arm: Add define_attr to to create a mapping between MVE predicated and unpredicated insns

Respin of first version to address comments and make it buildable on its own. diff --git a/gcc/config/arm/arm.h b/gcc/config/arm/arm.h index a9c2752c0ea..f0b01b7461f 100644 --- a/gcc/config/arm/arm.h +++ b/gcc/config/arm/arm.h @@ -2375,6 +2375,21 @@ extern int making_const_table; else if

[PATCH v2 0/2] arm: Add support for MVE Tail-Predicated Low Overhead Loops

Hi, Resending series version 2 addression comments on first version, also moved parts of the first patch to the second so it can be built without the second patch. Andre Vieira (2): arm: Add define_attr to to create a mapping between MVE predicated and unpredicated insns arm: Add support

Re: [PATCH] Add a late-combine pass [PR106594]

Jeff Law writes: > On 10/24/23 12:49, Richard Sandiford wrote: >> This patch adds a combine pass that runs late in the pipeline. >> There are two instances: one between combine and split1, and one >> after postreload. > So have you done any investigation on cases caught by your new pass >

[Bug target/113229] [14 Regression] gcc.dg/torture/pr70083.c ICEs when compiled with -march=armv9-a+sve2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113229 --- Comment #6 from avieira at gcc dot gnu.org --- Oh forgot to mention, this is triggering because of the div optimization in: https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=c69db3ef7f7d82a50f46038aa5457b7c8cc2d643 But I suspect that too is

[Bug target/113229] [14 Regression] gcc.dg/torture/pr70083.c ICEs when compiled with -march=armv9-a+sve2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113229 --- Comment #5 from avieira at gcc dot gnu.org --- Oh forgot to mention, this is triggering because of the div optimization in: https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=c69db3ef7f7d82a50f46038aa5457b7c8cc2d643 But I suspect that too is

[Bug target/113229] [14 Regression] gcc.dg/torture/pr70083.c ICEs when compiled with -march=armv9-a+sve2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113229 avieira at gcc dot gnu.org changed: What|Removed |Added Last reconfirmed||2024-01-05 Ever

[PATCH] libgccjit: Add support for setting the comment ident

Hi. This patch adds support for setting the comment ident (analogous to #ident "comment" in C). Thanks for the review. From 1af4e77540001cce8c30e86040c1da785e435810 Mon Sep 17 00:00:00 2001 From: Antoni Boucher Date: Fri, 27 Oct 2023 17:36:03 -0400 Subject: [PATCH] libgccjit: Add support for

Re: No subject

5 Jan 2024 5:00:03 pm LIU Hao : 在 2024/1/5 21:44, Peter0x44 via Gcc 写道: Since you mentioned windows 7 specifically, some of the suggestions aren't really appropriate. I don't believe msys2 supports windows 7 anymore. Nobody mentioned Windows 7... maybe you mistook the question mark? :|

[Bug sanitizer/113244] New: Potential thread sanitizer false positive with future exception

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113244 Bug ID: 113244 Summary: Potential thread sanitizer false positive with future exception Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal

Re: No subject

在 2024/1/5 21:44, Peter0x44 via Gcc 写道: Since you mentioned windows 7 specifically, some of the suggestions aren't really appropriate. I don't believe msys2 supports windows 7 anymore. Nobody mentioned Windows 7... maybe you mistook the question mark? :| MSYS2 itself no longer supports

[Bug c++/113242] g++ rejects-valid template argument of class type containing an lvalue reference

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

[PATCH] c++: address of NTTP object as targ [PR113242]

Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for trunk and perhaps 13? -- >8 -- invalid_tparm_referent_p was rejecting using the address of a class NTTP object as a template argument, but this should be fine. PR c++/113242 gcc/cp/ChangeLog: * pt.cc

[Bug libstdc++/108976] codecvt for Unicode allows surrogate code points

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976 --- Comment #9 from Dimitrij Mijoski --- I believe this bug report should closed as resolved. Are there maybe plans for back-porting?

[Bug tree-optimization/113104] Suboptimal loop-based slp node splicing across iterations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113104 Richard Sandiford changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[PATCH] aarch64: Rework uxtl->zip optimisation [PR113196]

g:f26f92b534f9 implemented unsigned extensions using ZIPs rather than UXTL{,2}, since the former has a higher throughput than the latter on amny cores. The optimisation worked by lowering directly to ZIP during expand, so that the zero input could be hoisted and shared. However, changing to ZIP

[PATCH] Keep track of the FUNCTION_BEG note

function.cc emits a NOTE_FUNCTION_BEG after all arguments have been copied to pseudos. It then records this note in parm_birth_insn. Various other pieces of code use this insn as a convenient place to insert things at the start of the function. However, cfgexpand later changes parm_birth_insn as

[pushed] aarch64: Extend VECT_COMPARE_COSTS to !SVE [PR113104]

When SVE is enabled, we try vectorising with multiple different SVE and Advanced SIMD approaches and use the cost model to pick the best one. Until now, we've not done that for Advanced SIMD, since "the first mode that works should always be the best". The testcase is a counterexample. Each

[Bug tree-optimization/113104] Suboptimal loop-based slp node splicing across iterations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113104 --- Comment #5 from GCC Commits --- The trunk branch has been updated by Richard Sandiford : https://gcc.gnu.org/g:7328faf89e9b4953baaff10e18262c70fbd3e578 commit r14-6961-g7328faf89e9b4953baaff10e18262c70fbd3e578 Author: Richard Sandiford

[Bug tree-optimization/113210] [14 Regression] ICE: tree check: expected integer_cst, have cond_expr in get_len, at tree.h:6481

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

[Bug tree-optimization/113210] [14 Regression] ICE: tree check: expected integer_cst, have cond_expr in get_len, at tree.h:6481

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113210 --- Comment #7 from Jakub Jelinek --- Or maybe just a bug in the PLUS_EXPR folding? The code sets NITERSM1 to (short unsigned int) (a.0_1 + 255) + 1 > 256 ? ~(short unsigned int) (a.0_1 + 255) : 0 and then fold_build2s PLUS_EXPR of that and 1

Re: Update on GCC 14 C type safety changes/warnings as errors

Hello, On Thu, Nov 30 2023, Florian Weimer via Gcc wrote: > The patch series is currently under review: > > [PATCH v3 00/11] : More warnings as errors by default > > > > Jeff as a global reviewer has

Re: [RFA] [V3] new pass for sign/zero extension elimination

On 1/4/24 13:44, Xi Ruoyao wrote: I have successfully bootstrapped and regtested the patch on loongarch64- linux-gnu. The test cases in the patch (intended for RISC-V) also works on LoongArch per my manual testing. I find myself wondering if we should create some kind of target-supports

Re: [committed] RISC-V: Add crypto vector builtin function.

On 1/4/24 20:24, Palmer Dabbelt wrote: On Thu, 04 Jan 2024 19:17:21 PST (-0800), juzhe.zh...@rivai.ai wrote: Hi, Wang Feng. Your patch has some ICEs: FAIL: gcc.target/riscv/rvv/base/zvbc-intrinsic.c (internal compiler error: RTL check: expected code 'const_int', have 'reg' in

[Bug ipa/112616] [11/12/13/14 Regression] wrong code at -O{s, 2, 3} on x86_64-linux-gnu since r10-3311

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112616 Martin Jambor changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jamborm at gcc dot gnu.org

  1   2   >