Re: [PATCH] tree-cfg: Fix misleading error message in verify_gimple_assign_single

On Sun, Dec 10, 2023 at 4:00 PM xndcn wrote: > > Hi, I am a newbie in GCC, and I do not have access to git repo. > > I found some misleading error messages in verify_gimple_assign_single > function of tree-cfg.cc. It prompt error "invalid RHS for gimple memory > store: ", but it checks lhs in

[Bug target/112431] RISC-V GCC-15 feature: Support register overlap on widen RVV instructions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112431 --- Comment #15 from GCC Commits --- The master branch has been updated by Pan Li : https://gcc.gnu.org/g:7e854b58084c131fceca9e8fa9dcc7469972e69d commit r14-6400-g7e854b58084c131fceca9e8fa9dcc7469972e69d Author: Juzhe-Zhong Date: Sat Dec

Re: [PATCH] RISC-V: Recognize stepped series in expand_vec_perm_const.

On 12/11/23 03:09, juzhe.zh...@rivai.ai wrote: > + if (shuffle_series (d)) > + return true; > > > Could you rename it into shuffle_series_patterns ? > > Just to make naming consistent. Done, going to push with that change in a while. Regards Robin

Re: [PATCH] RISC-V: Support highest overlap for wv instructions

LGTM, thanks. Regards Robin

Re: [PATCH] expr: catch more `a*bool` while expanding [PR 112935]

On Sun, Dec 10, 2023 at 10:30 AM Xi Ruoyao wrote: > > On Sun, 2023-12-10 at 01:21 -0800, Andrew Pinski wrote: > > diff --git a/gcc/expr.cc b/gcc/expr.cc > > index 6da51f2aca2..4686cacd22f 100644 > > --- a/gcc/expr.cc > > +++ b/gcc/expr.cc > > @@ -10209,8 +10209,9 @@ expand_expr_real_2 (sepops

Re: [PATCH] expr: catch more `a*bool` while expanding [PR 112935]

On Sun, Dec 10, 2023 at 10:21 AM Andrew Pinski wrote: > > After r14-1655-g52c92fb3f40050 (and the other commits > which touch zero_one_valued_p), we end up with a with > `bool * a` but where the bool is an SSA name that might not > have non-zero bits set on it (to 0x1) even though it > does the

Re: [PATCH 15/21]middle-end: [RFC] conditionally support forcing final edge for debugging

On Sat, 9 Dec 2023, Richard Sandiford wrote: > Tamar Christina writes: > > Hi All, > > > > What do people think about having the ability to force only the latch > > connected > > exit as the exit as a param? I.e. what's in the patch but as a param. > > > > I found this useful when debugging

Re: [PATCH v2] -finline-stringops: check base blksize for memset [PR112778]

On Sat, Dec 9, 2023 at 8:05 AM Alexandre Oliva wrote: > > Scratch the previous one, the "slightly different version" I had before > it was not entirely broken due to unnecessary, suboptimal and incorrect > use of ctz. Here I have yet another implementation of that loop that > should perform

Re: [PATCH] -finline-stringops: avoid too-wide smallest_int_mode_for_size [PR112784]

On Sat, Dec 9, 2023 at 3:25 AM Alexandre Oliva wrote: > > > smallest_int_mode_for_size may abort when the requested mode is not > available. Call int_mode_for_size instead, that signals the > unsatisfiable request in a more graceful way. > > Regstrapped on x86_64-linux-gnu. Ok to install? > > >

Re: [PATCH 0/3] Espressif xtensa chips multilib

Hi Max! Could you please consider to merge patch 1 and patch 3? Along with https://sourceware.org/pipermail/binutils/2023-July/128478.html Regards, Alexey

[Committed] RISC-V: Fix ICE in extract_single_source

This patch fixes the following ICE in VSETVL PASS: bug.c:39:1: internal compiler error: Segmentation fault 39 | } | ^ 0x1ad5a08 crash_signal ../../../../gcc/gcc/toplev.cc:316 0x7f7f55feb90f ??? ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0 0x218d7c7

Re: [PATCH 1/2] c-family: -Waddress-of-packed-member and casts

On Wed, Nov 22, 2023 at 11:45 PM Jason Merrill wrote: > > Tested x86_64-pc-linux-gnu, OK for trunk? OK > -- 8< -- > > -Waddress-of-packed-member, in addition to the documented warning about > taking the address of a packed member, also warns about casting from > a pointer to a TYPE_PACKED type

Re: [PATCH] strub: add note on attribute access

On Sat, Dec 9, 2023 at 3:09 AM Alexandre Oliva wrote: > > On Dec 7, 2023, Alexandre Oliva wrote: > > > Thanks for raising the issue. Maybe there should be at least a comment > > there, and perhaps some asserts to check that pointer and reference > > types don't make to indirect_parms. > >

RE: [PATCH 9/21]middle-end: implement vectorizable_early_exit for codegen of exit code

> > > > > > Hmm, but we're visiting them then? I wonder how you get along > > > without doing adjustmens on the uses if you consider > > > > > > _1 = a < b; > > > _2 = c != d; > > > _3 = _1 | _2; > > > if (_3 != 0) > > > exit loop; > > > > > > thus a combined condition like

[v3 PATCH] Simplify vector ((VCE (a cmp b ? -1 : 0)) < 0) ? c : d to just (VCE ((a cmp b) ? (VCE c) : (VCE d))).

> since you are looking at TYPE_PRECISION below you want > VECTOR_INTIEGER_TYPE_P here as well? The alternative > would be to compare TYPE_SIZE. > > Some of the checks feel redundant but are probably good for > documentation purposes. > > OK with using VECTOR_INTIEGER_TYPE_P Actually, the data

Re: libgcov, fork, and mingw (and other targets without the full POSIX set)

* LIU Hao via Gcc: > 在 2023/12/8 21:59, Florian Weimer via Gcc 写道: >>[PATCH] libgcov: Call __builtin_fork instead of fork >> >> > > May I ask why it's not something like this? > > Even though there may be

PING^2: [PATCH v2] Only allow (int)trunc(x) to (int)x simplification with -ffp-int-builtin-inexact [PR107723]

Ping again. On Fri, 2023-12-01 at 13:44 +0800, Xi Ruoyao wrote: > Ping. > > On Fri, 2023-11-24 at 17:09 +0800, Xi Ruoyao wrote: > > With -fno-fp-int-builtin-inexact, trunc is not allowed to raise > > FE_INEXACT and it should produce an integral result (if the input is not > > NaN or Inf).  Thus

Re: [PATCH] treat argp-based mem as frame related in dse

On 12/10/23 20:07, Jiufu Guo wrote: I'm having a bit of a hard time convincing myself this is correct though. I can't see how rewriting the load to read the source of the prior store is unsafe. If that fixes a problem, then it would seem like we've gone wrong before here -- perhaps failing

Re: [PATCH 2/5] [ifcvt] optimize x=c ? (y shift_op z):y by RISC-V Zicond like insns

On 12/10/23 21:01, Fei Gao wrote: On 2023-12-11 04:43  Jeff Law wrote: On 12/5/23 01:12, Fei Gao wrote: op=[ASHIFT, ASHIFTRT, LSHIFTRT, ROTATE, ROTATERT] Conditional op, if zero rd = (rc == 0) ? (rs1 op rs2) : rs1 --> czero.nez rd, rs2, rc op rd, rs1, rd Conditional op, if non-zero rd

Re: [PATCH] -finline-stringops: don't assume ptr_mode ptr in memset [PR112804]

On 12/10/23 15:38, Alexandre Oliva wrote: On Dec 10, 2023, Jeff Law wrote: On 12/8/23 19:25, Alexandre Oliva wrote: On aarch64 -milp32, and presumably on other such targets, ptr can be in a different mode than ptr_mode in the testcase. Cope with it. Regstrapped on x86_64-linux-gnu, also

Re: [PATCH 5/5] [ifcvt] optimize extension for x=c ? (y op z) : y by RISC-V Zicond like insns

On 12/5/23 01:12, Fei Gao wrote: SIGN_EXTEND, ZERO_EXTEND and SUBREG has been considered to support SImode in 64-bit machine. Co-authored-by: Xiao Zeng gcc/ChangeLog: * ifcvt.cc (noce_cond_zero_binary_op_supported): add support for extension

Re: [PATCH 4/5] [ifcvt] optimize x=c ? (y op const_int) : y by RISC-V Zicond like insns

On 12/5/23 01:12, Fei Gao wrote: op=[PLUS, MINUS, IOR, XOR, ASHIFT, ASHIFTRT, LSHIFTRT, ROTATE, ROTATERT, AND] Co-authored-by: Xiao Zeng gcc/ChangeLog: * ifcvt.cc (noce_cond_zero_shift_op_supported): check if OP is shift like operation

Re: [PATCH V2] RISC-V: XFAIL scan dump fails for autovec PR111311

> diff --git a/gcc/testsuite/g++.dg/tree-ssa/pr83518.C > b/gcc/testsuite/g++.dg/tree-ssa/pr83518.C > index b8a2bd1ebbd..6f2fc56c82c 100644 > --- a/gcc/testsuite/g++.dg/tree-ssa/pr83518.C > +++ b/gcc/testsuite/g++.dg/tree-ssa/pr83518.C > @@ -24,4 +24,4 @@ unsigned test() >return sum; > } > >

Re: Re: [PATCH][v3] RISC-V: Add avail interface into function_group_info

2023-12-11 13:05 Kito Cheng wrote: >I am happy with this change now, however I didn't see any place call avail >function yet? Do I miss something? Are you planning to send follow up >patches to add that? >If so, LGTM. Yes, the crypto vector will determine whether to register the

Re: [PATCH] RISC-V: Remove poly selftest when --preference=fixed-vlmax

LGTM On Mon, Dec 11, 2023 at 1:19 PM Juzhe-Zhong wrote: > > This patch fixes multiple ICEs in full coverage testing: > > cc1: internal compiler error: in riscv_legitimize_poly_move, at > config/riscv/riscv.cc:2456^M > 0x1fd8d78 riscv_legitimize_poly_move^M >

[PATCH] RISC-V: Remove poly selftest when --preference=fixed-vlmax

This patch fixes multiple ICEs in full coverage testing: cc1: internal compiler error: in riscv_legitimize_poly_move, at config/riscv/riscv.cc:2456^M 0x1fd8d78 riscv_legitimize_poly_move^M ../../../../gcc/gcc/config/riscv/riscv.cc:2456^M 0x1fd9518 riscv_legitimize_move(machine_mode,

Re: [PATCH 3/5] [ifcvt] optimize x=c ? (y AND z) : y by RISC-V Zicond like insns

On 12/5/23 01:12, Fei Gao wrote: Take the following case for example. CFLAGS: -march=rv64gc_zbb_zicond -mabi=lp64d -O2 long test_AND_ceqz (long x, long y, long z, long c) { if (c) x = y & z; else x = y; return x; } Before patch: and a2,a1,a2 czero.eqz a0,a2,a3

Re: [PATCH][v3] RISC-V: Add avail interface into function_group_info

I am happy with this change now, however I didn't see any place call avail function yet? Do I miss something? Are you planning to send follow up patches to add that? If so, LGTM.

[Bug target/110606] ICE output_operand: '%&' used without any local dynamic TLS references on powerpc64le-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110606 --- Comment #10 from Jeevitha --- The following instructions [in basic block 4] were removed in sched2 DCE, which makes r3 unused [populated in call_insn 26], but they were not deleted in this pass itself: (insn 28 26 29 4 (set (reg:DI 9 9

Re: Re: [PATCH 2/5] [ifcvt] optimize x=c ? (y shift_op z):y by RISC-V Zicond like insns

On 2023-12-11 04:43  Jeff Law wrote: > > > >On 12/5/23 01:12, Fei Gao wrote: >> op=[ASHIFT, ASHIFTRT, LSHIFTRT, ROTATE, ROTATERT] >> >> Conditional op, if zero >> rd = (rc == 0) ? (rs1 op rs2) : rs1 >> --> >> czero.nez rd, rs2, rc >> op rd, rs1, rd >> >> Conditional op, if non-zero >> rd = (rc !=

[PATCH V4 2/3] Using pli for constant splitting

Hi, For constant building e.g. r120=0x, which does not fit 'li or lis', 'pli' is used to build this constant via 'emit_move_insn'. While for a complicated constant, e.g. 0xULL, when using 'rs6000_emit_set_long_const' to split the constant recursively, it fails to use

[PATCH V4 1/3]rs6000: accurate num_insns_constant_gpr

Hi, Trunk gcc supports more constants to be built via two instructions: e.g. "li/lis; xori/xoris/rldicl/rldicr/rldic". And then num_insns_constant should also be updated. Function "rs6000_emit_set_long_const" is used to build complicated constants; and "num_insns_constant_gpr" is used to compute

Re: [PATCH] treat argp-based mem as frame related in dse

Hi, Thanks again for your kind review! Jeff Law writes: > On 12/8/23 00:18, Jiufu Guo wrote: >> >> Hi, >> >> Jeff Law writes: >> >>> On 12/6/23 02:27, Jiufu Guo wrote: Hi, The issue mentioned in PR112525 would be able to be handled by updating dse.cc to treat

[Patch, rs6000] Clean up pre-checking of expand_block_compare

Hi, This patch cleans up pre-checking of expand_block_compare. It does 1. Assert only P7 above can enter this function as it's already guard by the expand. 2. Return false when optimizing for size. 3. Remove P7 CPU test as only P7 above can enter this function and P7 LE is excluded by

[Bug middle-end/101852] [meta-bug] some standard RTL names are not documented

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101852 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2023-12-11

[Bug middle-end/112951] [14 Regression] cond_copysign, cond_len_copysign optab not documented

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

[Bug fortran/112873] F2023 degree trig functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112873 --- Comment #11 from Steve Kargl --- On Sun, Dec 10, 2023 at 09:45:33PM +, anlauf at gcc dot gnu.org wrote: > > here's a minor update that fully removes the "Extended math intrinsics" node. > Otherwise your patch would not compile here.

[Bug middle-end/112951] New: [14 Regression] cond_copysign, cond_len_copysign optab not documented

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112951 Bug ID: 112951 Summary: [14 Regression] cond_copysign, cond_len_copysign optab not documented Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords:

[Bug middle-end/101852] [meta-bug] some standard RTL names are not documented

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101852 --- Comment #5 from Andrew Pinski --- A new one for GCC 14 even: cond_copysign cond_len_copysign

[Bug target/112950] New: gcc.target/aarch64/sve/acle/general/dupq_5.c fails on aarch64_be-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112950 Bug ID: 112950 Summary: gcc.target/aarch64/sve/acle/general/dupq_5.c fails on aarch64_be-linux-gnu Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords:

[Bug c++/104234] ICE with -fmodules-ts and std::map/_Rb_tree

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104234 --- Comment #2 from GCC Commits --- The master branch has been updated by Nathaniel Shead : https://gcc.gnu.org/g:ab3daffcbf35566d468c3028e48068a481048baf commit r14-6394-gab3daffcbf35566d468c3028e48068a481048baf Author: Nathaniel Shead

[Bug c++/100470] std::is_nothrow_move_constructible incorrect behavior for explicitly defaulted members

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100470 --- Comment #7 from GCC Commits --- The master branch has been updated by Nathaniel Shead : https://gcc.gnu.org/g:4719b6f5ae4d758f193a17bbd5fb6cbacd702a23 commit r14-6395-g4719b6f5ae4d758f193a17bbd5fb6cbacd702a23 Author: Nathaniel Shead

[Bug c++/96090] noexcept operator of potentially-throwing defaulted function gives the wrong result

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96090 --- Comment #3 from GCC Commits --- The master branch has been updated by Nathaniel Shead : https://gcc.gnu.org/g:4719b6f5ae4d758f193a17bbd5fb6cbacd702a23 commit r14-6395-g4719b6f5ae4d758f193a17bbd5fb6cbacd702a23 Author: Nathaniel Shead Date:

[Bug c++/53025] [C++11] noexcept operator depends on copy-elision

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53025 --- Comment #9 from GCC Commits --- The master branch has been updated by Nathaniel Shead : https://gcc.gnu.org/g:4719b6f5ae4d758f193a17bbd5fb6cbacd702a23 commit r14-6395-g4719b6f5ae4d758f193a17bbd5fb6cbacd702a23 Author: Nathaniel Shead Date:

[Bug c++/112580] [14 Regression]: g++.dg/modules/xtreme-header-4_b.C et al; ICE tree check: expected class 'type', have 'declaration'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112580 --- Comment #2 from GCC Commits --- The master branch has been updated by Nathaniel Shead : https://gcc.gnu.org/g:ab3daffcbf35566d468c3028e48068a481048baf commit r14-6394-gab3daffcbf35566d468c3028e48068a481048baf Author: Nathaniel Shead

[Bug target/112929] [14] RISC-V vector: Variable clobbered at runtime

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112929 --- Comment #12 from Li Pan --- (In reply to Patrick O'Neill from comment #0) > Testcase: > int printf(char *, ...); > int a, b, l, i, p, q, t, n, o; > int *volatile c; > static int j; > static struct pack_1_struct d; > long e; > char m = 5; >

Re: [PATCH v26 00/23] Optimize type traits compilation performance

On Sun, Dec 10, 2023 at 10:19 AM Jason Merrill wrote: > > On 12/7/23 00:11, Ken Matsui wrote: > > This patch series optimizes type traits compilation performance by > > implementing built-in type traits and using them in libstdc++. > > > > Changes in v26: > > > > * Rebased on top of trunk.

Re: [PATCH] c++: fix noexcept checking for trivial operations [PR96090]

On 12/10/23 21:04, Nathaniel Shead wrote: On Sat, Dec 09, 2023 at 03:40:44PM -0500, Jason Merrill wrote: On 11/27/23 06:07, Nathaniel Shead wrote: Ping for https://gcc.gnu.org/pipermail/gcc-patches/2023-October/634626.html. I've been made aware since constructing this patch of CWG2820, which

Re: [PATCH] RISC-V: Recognize stepped series in expand_vec_perm_const.

+ if (shuffle_series (d)) + return true; Could you rename it into shuffle_series_patterns ? Just to make naming consistent. juzhe.zh...@rivai.ai From: Robin Dapp Date: 2023-12-09 21:18 To: gcc-patches; palmer; Kito Cheng; jeffreyalaw; juzhe.zh...@rivai.ai CC: rdapp.gcc

Re: [PATCH] c++: fix noexcept checking for trivial operations [PR96090]

On Sat, Dec 09, 2023 at 03:40:44PM -0500, Jason Merrill wrote: > On 11/27/23 06:07, Nathaniel Shead wrote: > > Ping for https://gcc.gnu.org/pipermail/gcc-patches/2023-October/634626.html. > > > > I've been made aware since constructing this patch of CWG2820, which has > > a proposed resolution

[Patch, rs6000] Correct definition of macro of fixed point efficient unaligned

Hi, The patch corrects the definition of TARGET_EFFICIENT_OVERLAPPING_UNALIGNED and change its name to a comprehensible name. Bootstrapped and tested on x86 and powerpc64-linux BE and LE with no regressions. Is this OK for trunk? Thanks Gui Haochen ChangeLog rs6000: Correct definition of

Re: [PATCH] extend.texi: Mark builtin arguments with @var{...}

On 12/4/23 00:36, Jakub Jelinek wrote: On Fri, Dec 01, 2023 at 10:43:57AM -0700, Sandra Loosemore wrote: On 12/1/23 10:33, Jakub Jelinek wrote: Shall we tweak that somehow? If the argument names are unimportant, perhaps it is fine to leave that out, but shouldn't we always use @var{...}

RE: Re: [PATCH] RISC-V: Add vectorized strcmp.

FYI. I have the some failures as juzhe mentioned, with the emulator qemu version qemu-riscv64 version 8.1.93 (v8.2.0-rc3). The entire log may look like below: Executing on host: /home/box/panli/riscv-gnu-toolchain/build-gcc-newlib-stage2/gcc/xgcc

[PATCH][v3] RISC-V: Add avail interface into function_group_info

Patch v3: Fix typo and remove the modification of rvv.exp. Patch v2: Using variadic macro and add the dependency into t-riscv. In order to add other extension about vector,this patch add unsigned int (*avail) (void) into function_group_info to determine whether to register the intrinsic based on

[Bug target/112904] [14 Regression] ICE in extract_insn, at recog.cc:2791 with -mxop since r14-4964-g7eed861e8ca3f5

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

[Bug target/112904] [14 Regression] ICE in extract_insn, at recog.cc:2791 with -mxop since r14-4964-g7eed861e8ca3f5

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112904 --- Comment #3 from GCC Commits --- The master branch has been updated by hongtao Liu : https://gcc.gnu.org/g:2c2df123de432356d28ee7e8a9627dc9e80a399d commit r14-6393-g2c2df123de432356d28ee7e8a9627dc9e80a399d Author: liuhongt Date: Fri Dec

[Bug c/112947] Contradictory indications of extern __thread address NULL or not with UBSAN

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112947 --- Comment #4 from resence at parsoma dot net --- Or rather, static int *nimErrorFlag(void) { /* With this, no always-false warning */ /* printf("BAR1: %p\n", (void*)__system_u4299); */ if (((__system_u4299) == (void *)0)) {

[Bug c/112947] Contradictory indications of extern __thread address NULL or not with UBSAN

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112947 --- Comment #3 from resence at parsoma dot net --- It's not only the null pointer check per se though? Re-add a stdio.h import for convenience, and it still vacillates whether or not that address is NULL or not: BAR2: 0x7f25d843173c BAR3:

[Bug target/112707] [14 regression] gcc 14 outputs invalid assembly on ppc: Error: unrecognized opcode: `fctid'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112707 HaoChen Gui changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug target/112707] [14 regression] gcc 14 outputs invalid assembly on ppc: Error: unrecognized opcode: `fctid'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112707 --- Comment #16 from GCC Commits --- The master branch has been updated by HaoChen Gui : https://gcc.gnu.org/g:ae226cb1ee17d61c416c9d4d8c5a142788b8afff commit r14-6392-gae226cb1ee17d61c416c9d4d8c5a142788b8afff Author: Haochen Gui Date: Mon

[Bug target/112707] [14 regression] gcc 14 outputs invalid assembly on ppc: Error: unrecognized opcode: `fctid'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112707 --- Comment #15 from GCC Commits --- The master branch has been updated by HaoChen Gui : https://gcc.gnu.org/g:46e342b985e6b4058db73875103cced2666e84e2 commit r14-6391-g46e342b985e6b4058db73875103cced2666e84e2 Author: Haochen Gui Date: Mon

[Bug c++/95656] Inconsistent output in compiling an undefined function

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

[Bug c++/95656] Inconsistent output in compiling an undefined function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95656 --- Comment #4 from Andrew Pinski --- * See also PR79265 and PR98109

[Bug c++/95656] Inconsistent output in compiling an undefined function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95656 Andrew Pinski changed: What|Removed |Added CC||resence at parsoma dot net --- Comment

[Bug c/112947] Contradictory indications of extern __thread address NULL or not with UBSAN

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

Re: [PATCH 0/4] v2 of Option handling: add documentation URLs

Hi David, On Fri, Dec 08, 2023 at 06:35:56PM -0500, David Malcolm wrote: > On Tue, 2023-11-21 at 23:43 +, Joseph Myers wrote: > > On Tue, 21 Nov 2023, Tobias Burnus wrote: > > > > > On 21.11.23 14:57, David Malcolm wrote: > > > > On Tue, 2023-11-21 at 02:09 +0100, Hans-Peter Nilsson wrote: >

[Bug c/112947] Contradictory indications of extern __thread address NULL or not with UBSAN

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112947 --- Comment #1 from Andrew Pinski --- This is by design. -fsanitize=undefined turns off -fdelete-null-pointer-checks .

[Bug tree-optimization/112949] evrp produces incorrect range for __builtin_clz

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112949 --- Comment #7 from Andrew Pinski --- Specifically https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32455#c4 .

[Bug tree-optimization/112949] evrp produces incorrect range for __builtin_clz

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

[Bug target/110273] [12/13/14 Regression] i686-w64-mingw32 with -mavx512f generates AVX instructions without stack alignment

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110273 --- Comment #13 from Zeb Figura --- (In reply to Sam James from comment #11) > (In reply to Jens-Hanno Schwalm from comment #10) > > Hi, i think we found a very-similar issue in darktable code, you might look > > at > > > >

[Bug tree-optimization/112949] evrp produces incorrect range for __builtin_clz

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112949 --- Comment #5 from Andrew Pinski --- Oh the definition of __builtin_clz does not have return value so the value is undefined to begin with.

[Bug tree-optimization/112949] evrp produces incorrect range for __builtin_clz

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112949 Andrew Pinski changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED

[Bug tree-optimization/112949] evrp produces incorrect range for __builtin_clz

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112949 --- Comment #3 from Krister Walfridsson --- The C program is obviously UB. But the optimization is done on GIMPLE, and it is not obvious to me that the GIMPLE code is UB -- we have a function called __builtin_clz that calls an internal

Re: [PATCH] -finline-stringops: don't assume ptr_mode ptr in memset [PR112804]

On Sun, Dec 10, 2023 at 2:38 PM Alexandre Oliva wrote: > > On Dec 10, 2023, Jeff Law wrote: > > > On 12/8/23 19:25, Alexandre Oliva wrote: > >> On aarch64 -milp32, and presumably on other such targets, ptr can be > >> in a different mode than ptr_mode in the testcase. Cope with it. > >>

[Bug tree-optimization/112949] evrp produces incorrect range for __builtin_clz

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112949 --- Comment #2 from Andrew Pinski --- defining __builtin_clz makes this code undefined. Especially when it comes to calling itself. That is the ranges here are ok and correct but rather the usage is undefined. gcc.dg/pr100521.c is just

[Bug tree-optimization/112949] evrp produces incorrect range for __builtin_clz

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112949 --- Comment #1 from Andrew Pinski --- I think the testcase is broken rather than anything else.

[Bug tree-optimization/112949] New: evrp produces incorrect range for __builtin_clz

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112949 Bug ID: 112949 Summary: evrp produces incorrect range for __builtin_clz Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug target/112948] New: gcc/config/aarch64/aarch64-early-ra.cc:1953: possible cut'n'paste error ?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112948 Bug ID: 112948 Summary: gcc/config/aarch64/aarch64-early-ra.cc:1953: possible cut'n'paste error ? Product: gcc Version: 14.0 Status: UNCONFIRMED Severity:

Re: [PATCH] -finline-stringops: don't assume ptr_mode ptr in memset [PR112804]

On Dec 10, 2023, Jeff Law wrote: > On 12/8/23 19:25, Alexandre Oliva wrote: >> On aarch64 -milp32, and presumably on other such targets, ptr can be >> in a different mode than ptr_mode in the testcase. Cope with it. >> Regstrapped on x86_64-linux-gnu, also tested the new test on >> aarch64-elf.

gcc-14-20231210 is now available

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

[Bug c/112947] New: Contradictory indications of extern __thread address NULL or not with UBSAN

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112947 Bug ID: 112947 Summary: Contradictory indications of extern __thread address NULL or not with UBSAN Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity:

[Bug fortran/112873] F2023 degree trig functions

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

[Bug fortran/105543] Function returning a class array with contiguous attribute rejected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105543 anlauf at gcc dot gnu.org changed: What|Removed |Added Target Milestone|--- |14.0

[Bug fortran/111503] Issues with POINTER, OPTIONAL, CONTIGUOUS dummy arguments

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111503 anlauf at gcc dot gnu.org changed: What|Removed |Added Target Milestone|--- |14.0 Resolution|---

Re: [PATCH] Add some new DW_IDX_* constants

> "Jakub" == Jakub Jelinek writes: Jakub> LGTM for GCC (but it needs a ChangeLog entry). Oops, yeah -- I am out of the habit of writing those. I'll add one before I push this. Tom

[Bug libstdc++/104928] std::counting_semaphore on Linux can sleep forever

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104928 --- Comment #6 from Jonathan Wakely --- If you can reply on gcc-patches (CCing the libstdc++ list) that would be great, thanks for looking at it!

Re: [PATCH 2/5] [ifcvt] optimize x=c ? (y shift_op z):y by RISC-V Zicond like insns

On 12/5/23 01:12, Fei Gao wrote: op=[ASHIFT, ASHIFTRT, LSHIFTRT, ROTATE, ROTATERT] Conditional op, if zero rd = (rc == 0) ? (rs1 op rs2) : rs1 --> czero.nez rd, rs2, rc op rd, rs1, rd Conditional op, if non-zero rd = (rc != 0) ? (rs1 op rs2) : rs1 --> czero.eqz rd, rs2, rc op rd, rs1, rd

[Bug libstdc++/104928] std::counting_semaphore on Linux can sleep forever

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104928 --- Comment #5 from Nate Eldredge --- Oh wait, disregard that last, I realized that I only applied one of the two patches. Let me try again.

[Bug libstdc++/104928] std::counting_semaphore on Linux can sleep forever

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104928 --- Comment #4 from Nate Eldredge --- @Jonathan: I think that patch set is on the right track, but it has some other serious bugs. For one, __atomic_wait_address calls __detail::__wait_impl with __args._M_old uninitialized (g++ -O3 -Wall

[Bug tree-optimization/112880] ICE: in smallest_mode_for_size, at stor-layout.cc:356 with __builtin_mul_overflow() of _BitInt(1024)

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

[Bug middle-end/112881] ICE: in count_type_elements, at expr.cc:7034 when initializing struct with a _BitInt(64) member

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

[Bug fortran/100651] [11/12/13/14 Regression] Bad handling of optional, allocatable character argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100651 anlauf at gcc dot gnu.org changed: What|Removed |Added Target Milestone|11.5|13.3

[Bug c++/105220] [CWG2589] concept evaluation and friendship

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105220 Jason Merrill changed: What|Removed |Added CC||jason at gcc dot gnu.org

[Bug fortran/93762] Truncation of deferred-length string when passing as optional

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93762 anlauf at gcc dot gnu.org changed: What|Removed |Added Keywords||wrong-code Target

[Bug fortran/100651] [11/12/13/14 Regression] Bad handling of optional, allocatable character argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100651 --- Comment #17 from GCC Commits --- The releases/gcc-13 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:7a2f4af9b1b12d8b1f1b4cf4ddb812f2a48ce9ff commit r13-8142-g7a2f4af9b1b12d8b1f1b4cf4ddb812f2a48ce9ff Author: Harald Anlauf

[Bug fortran/93762] Truncation of deferred-length string when passing as optional

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93762 --- Comment #6 from GCC Commits --- The releases/gcc-13 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:7a2f4af9b1b12d8b1f1b4cf4ddb812f2a48ce9ff commit r13-8142-g7a2f4af9b1b12d8b1f1b4cf4ddb812f2a48ce9ff Author: Harald Anlauf

[Bug modula2/112946] New: Assignment of string to enumeration or set crashes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112946 Bug ID: 112946 Summary: Assignment of string to enumeration or set crashes Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug tree-optimization/111972] [14 regression] missed vectorzation for bool a = j != 1; j = (long int)a;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111972 Andrew Pinski changed: What|Removed |Added Keywords||patch URL|

Re: [PATCH] Add some new DW_IDX_* constants

On Sat, Dec 09, 2023 at 01:56:53PM -0700, Tom Tromey wrote: > I've reimplemented the .debug_names code in GDB -- it was quite far > from being correct, and the new implementation is much closer to what > is specified by DWARF. > > However, the new writer in GDB needs to emit some symbol

[Bug target/110273] [12/13/14 Regression] i686-w64-mingw32 with -mavx512f generates AVX instructions without stack alignment

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110273 --- Comment #12 from Andrew Pinski --- (In reply to Sam James from comment #11) > (In reply to Jens-Hanno Schwalm from comment #10) > > Hi, i think we found a very-similar issue in darktable code, you might look > > at > > > >

  1   2   >