[Bug tree-optimization/109639] [14 regression] Internal compiler error: tree check: expected integer_cst, have addr_expr in to_wide, at tree.h:6283 since r14-249-g3c9372dfee0bb8

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109639 Sam James changed: What|Removed |Added Summary|[14 regression] Internal|[14 regression] Internal

[Bug tree-optimization/109639] [14 regression] Internal compiler error: tree check: expected integer_cst, have addr_expr in to_wide, at tree.h:6283

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109639 --- Comment #6 from Sam James --- Created attachment 54933 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54933=edit sam-reduced-clean.i

[Bug tree-optimization/109639] [14 regression] Internal compiler error: tree check: expected integer_cst, have addr_expr in to_wide, at tree.h:6283

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109639 --- Comment #5 from Sam James --- Created attachment 54932 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54932=edit sam-reduced.i

[Bug tree-optimization/109639] [14 regression] Internal compiler error: tree check: expected integer_cst, have addr_expr in to_wide, at tree.h:6283

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109639 Andrew Pinski changed: What|Removed |Added Keywords||needs-bisection, |

[Bug tree-optimization/109639] [14 regression] Internal compiler error: tree check: expected integer_cst, have addr_expr in to_wide, at tree.h:6283

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109639 --- Comment #4 from Andrew Pinski --- Created attachment 54931 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54931=edit One version of the reduced testcase I am not a fan of this reduced testcase so I am trying again.

[PATCH] RISC-V: Add required tls to read thread pointer test

From: Pan Li The read-thread-pointer test may require the gcc configured with --enable-tls. If no, there x4 (aka tp) register will not be presented in the assembly code. This patch requires the tls for the dg checking. It will perform the test checking if --enable-tls and mark the test as

[PATCH v3] RISCV: Add vector psabi checking.

From: Yanzhang Wang This patch adds support to check function's argument or return is vector type and throw warning if yes. gcc/ChangeLog: * config/riscv/riscv.cc: (riscv_scalable_vector_type_p): Determine whether the type is scalable vector. (riscv_arg_has_vector):

[Bug tree-optimization/109639] [14 regression] Internal compiler error: tree check: expected integer_cst, have addr_expr in to_wide, at tree.h:6283

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

[Bug tree-optimization/109639] [14 regression] Internal compiler error: tree check: expected integer_cst, have addr_expr in to_wide, at tree.h:6283

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109639 Andrew Pinski changed: What|Removed |Added Host|aarch64-unknown-linux-gnu | Keywords|

[Bug tree-optimization/109639] [14 regression] Internal compiler error: tree check: expected integer_cst, have addr_expr in to_wide, at tree.h:6283

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109639 --- Comment #2 from Sam James --- (In reply to Sam James from comment #1) > (In reply to Sam James from comment #0) > > gcc (Gentoo 14.0.0. p, commit 7546d8be5a8ae93e81535644c2578807db276ab6) > > 14.0.0 2023042

[Bug tree-optimization/25290] PHI-OPT could be rewritten so that is uses match

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25290 Andrew Pinski changed: What|Removed |Added Attachment #54821|0 |1 is obsolete|

[PATCH v2] RISCV: Add vector psabi checking.

From: Yanzhang Wang This patch adds support to check function's argument or return is vector type and throw warning if yes. gcc/ChangeLog: * config/riscv/riscv.cc: (riscv_scalable_vector_type_p): Determine whether the type is scalable vector. (riscv_arg_has_vector):

[PATCH] libsanitizer: cherry-pick commit 05551c658269 from upstream

cherry-pick: 05551c658269 [sanitizer] Correct alignment of x32 __sanitizer_siginfo * sanitizer_common/sanitizer_platform_limits_posix.h (__sanitizer_siginfo_pad): Use u64 to align x32 __sanitizer_siginfo to 8 bytes. ---

[Bug c/109412] [13/14 Regression] ICE in fold_convert_loc, at fold-const.cc:2627 since r13-2205-g14cfa01755a66a

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109412 Sam James changed: What|Removed |Added CC||sjames at gcc dot gnu.org

[Bug c++/61445] [4.10 Regression][C++11] ice in instantiate_decl at cp/pt.c:19770

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61445 --- Comment #5 from CVS Commits --- The trunk branch has been updated by Jason Merrill : https://gcc.gnu.org/g:95d4c0d2e6318aef88ba0bc607dfc1ec6b7a612f commit r14-283-g95d4c0d2e6318aef88ba0bc607dfc1ec6b7a612f Author: Jason Merrill Date: Thu

[pushed] c++: restore instantiate_decl assert

Tested x86_64-pc-linux-gnu, applying to trunk. -- 8< -- For PR61445 I removed this assert, but PR108242 demonstrated why it's still useful; to avoid regressing the former testcase I check pattern_defined in the assert. This reverts r212524. PR c++/61445 gcc/cp/ChangeLog: *

[Bug fortran/109641] New: Gfortran fails to overload intrinsic operator (*) if operands are complex. It works with real ones.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109641 Bug ID: 109641 Summary: Gfortran fails to overload intrinsic operator (*) if operands are complex. It works with real ones. Product: gcc Version: og10 (devel/omp/gcc-10)

[Bug target/109610] [14 regression] gcc.target/powerpc/dform-3.c fails after r14-172-g0368d169492017

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109610 --- Comment #7 from Hongtao.liu --- (In reply to rsand...@gcc.gnu.org from comment #6) > Please don't do the peephole thing! This seems like a > target-independent problem. > > The costs for r117 look odd. Why is the cost of GENERAL_REGS so

Re: libsanitizer: sync from master

On Wed, Apr 26, 2023 at 4:37 PM H.J. Lu wrote: > > On Wed, Apr 26, 2023 at 1:24 PM Martin Liška wrote: > > > > On 4/26/23 21:23, H.J. Lu wrote: > > > On Wed, Apr 26, 2023 at 6:52 AM Martin Liška wrote: > > >> > > >> On 11/15/22 16:47, Martin Liška wrote: > > >>> Hi. > > >>> > > >>> I've just

Re: libsanitizer: sync from master

On Wed, Apr 26, 2023 at 4:37 PM H.J. Lu wrote: > > On Wed, Apr 26, 2023 at 1:24 PM Martin Liška wrote: > > > > On 4/26/23 21:23, H.J. Lu wrote: > > > On Wed, Apr 26, 2023 at 6:52 AM Martin Liška wrote: > > >> > > >> On 11/15/22 16:47, Martin Liška wrote: > > >>> Hi. > > >>> > > >>> I've just

Re: [committed] libgcc CRIS: Define TARGET_HAS_NO_HW_DIVIDE

> From: Paul Koning > Date: Wed, 26 Apr 2023 21:02:31 -0400 > > On Apr 26, 2023, at 8:05 PM, Hans-Peter Nilsson wrote: > > > > Not many targets define this besides msp430, pdp1, xtensa, > > and arm compared to those that appear to unconditionally > > have a hardware division instruction (also,

Re: [committed] libgcc CRIS: Define TARGET_HAS_NO_HW_DIVIDE

> On Apr 26, 2023, at 8:05 PM, Hans-Peter Nilsson wrote: > > Not many targets define this besides msp430, pdp1, xtensa, > and arm compared to those that appear to unconditionally > have a hardware division instruction (also, pdp11 and > msp430 seem confused and should be empty instead of "1"

[Bug tree-optimization/109639] [14 regression] Internal compiler error: tree check: expected integer_cst, have addr_expr in to_wide, at tree.h:6283

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109639 --- Comment #1 from Sam James --- (In reply to Sam James from comment #0) > gcc (Gentoo 14.0.0. p, commit 7546d8be5a8ae93e81535644c2578807db276ab6) > 14.0.0 20230426 (experimental) This commit is wrong (recorded incorrectly). I'm ch

[committed] libgcc CRIS: Define TARGET_HAS_NO_HW_DIVIDE

Not many targets define this besides msp430, pdp1, xtensa, and arm compared to those that appear to unconditionally have a hardware division instruction (also, pdp11 and msp430 seem confused and should be empty instead of "1" and "(! TARGET_HWMULT)" - and having hardware multiplication doesn't

Re: [PATCH v4 05/10] RISC-V: autovec: Add autovectorization patterns for binary integer operations

Hi Robin and Juzhe, Just took a look and I like the approach. On 4/26/23 19:43, juzhe.zhong wrote: Yeah，Robin stuff is what I want and is making perfect sense for me. Replied Message FromRobin Dapp Date04/27/2023 02:15 To juzhe.zh...@rivai.ai

[Bug c++/109640] Spurious Wdangling-reference for argument to temporary lambda cast to rvalue reference

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109640 --- Comment #2 from Ed Catmur --- Ah, so this is Bug 108165? That's a shame, we use (temporary) lambdas extensively so I think we'd have to disable the warning entirely.

Ping: Re: [PATCH v3] doc: Document order of define_peephole2 scanning

> From: Hans-Peter Nilsson > Date: Wed, 19 Apr 2023 18:59:14 +0200 [...] > So again: Approvers: pdf output reviewed. Ok to commit? > -- >8 -- > I was a bit surprised when my newly-added define_peephole2 didn't > match, but it was because it was expected to partially match the > generated output

[Bug c++/109640] Spurious Wdangling-reference for argument to temporary lambda cast to rvalue reference

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109640 Andrew Pinski changed: What|Removed |Added Keywords||diagnostic --- Comment #1 from Andrew

Re: libsanitizer: sync from master

On Wed, Apr 26, 2023 at 1:24 PM Martin Liška wrote: > > On 4/26/23 21:23, H.J. Lu wrote: > > On Wed, Apr 26, 2023 at 6:52 AM Martin Liška wrote: > >> > >> On 11/15/22 16:47, Martin Liška wrote: > >>> Hi. > >>> > >>> I've just pushed libsanitizer update that was tested on x86_64-linux and > >>>

Re: libsanitizer: sync from master

On Wed, Apr 26, 2023 at 1:24 PM Martin Liška wrote: > > On 4/26/23 21:23, H.J. Lu wrote: > > On Wed, Apr 26, 2023 at 6:52 AM Martin Liška wrote: > >> > >> On 11/15/22 16:47, Martin Liška wrote: > >>> Hi. > >>> > >>> I've just pushed libsanitizer update that was tested on x86_64-linux and > >>>

[Bug c++/109640] New: Spurious Wdangling-reference for argument to temporary lambda cast to rvalue reference

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109640 Bug ID: 109640 Summary: Spurious Wdangling-reference for argument to temporary lambda cast to rvalue reference Product: gcc Version: 13.1.0 Status: UNCONFIRMED

☺ Buildbot (Sourceware): gccrust - build successful (master)

A passing build has been detected on builder gccrust-opensusetw-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/103/builds/1029 Build state: build successful Revision: d2df050bd4392119adf64d0e35670c1a85d6451b Worker: bb1-2

[Bug tree-optimization/109639] New: [14 regression] Internal compiler error: tree check: expected integer_cst, have addr_expr in to_wide, at tree.h:6283

4.0.0./gcc/tree.h:3728 0x83cf9b tree_int_cst_elt_check(tree_node const*, int, char const*, int, char const*) /usr/src/debug/sys-devel/gcc-14.0.0./gcc-14.0.0./gcc/tree.h:6285 [...] ``` ``` gcc (Gentoo 14.0.0. p, commit 7546d8be5a8ae93e81535644c2578807db276ab6) 14.0.0 20230426 (experimenta

[committed] RISC-V: Fix sync.md and riscv.cc whitespace errors

On 4/26/23 14:21, Patrick O'Neill wrote: This patch fixes whitespace errors introduced with https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616807.html 2023-04-26 Patrick O'Neill gcc/ChangeLog: * config/riscv/riscv.cc: Fix whitespace. * config/riscv/sync.md: Fix

[Bug target/109636] [14 Regression] ICE: in paradoxical_subreg_p, at rtl.h:3205 with -O -mcpu=a64fx

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109636 --- Comment #3 from Andrew Pinski --- Oh simplify_gen_subreg should not be used I think. Rather gen_lowpart should be used instead. Especially when it comes to big endian.

gcc-10-20230426 is now available

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

[Bug target/109636] [14 Regression] ICE: in paradoxical_subreg_p, at rtl.h:3205 with -O -mcpu=a64fx

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

GCC/Clang attributes guiding warnings about unused entities

[cross-posting this to both the GCC and Clang communities] I have two specific issues on the subject I would like to discuss below. But first a quick overview: C++ has two attributes dealing with warnings about unused entities: * In one direction (making the compiler suppress warnings it

Re: [PATCH v2] RISC-V: Fix sync.md and riscv.cc whitespace errors

On 4/26/23 14:45, Bernhard Reutner-Fischer wrote: On 26 April 2023 23:21:06 CEST, Patrick O'Neill wrote: This patch fixes whitespace errors introduced with https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616807.html 2023-04-26 Patrick O'Neill gcc/ChangeLog: *

[Bug libstdc++/106376] [LWG3545] The implementation of std::pointer_traits seems wrong

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106376 Jonathan Wakely changed: What|Removed |Added Resolution|--- |WORKSFORME

[PATCH v5 04/10] RISC-V:autovec: Add target vectorization hooks

2023-04-24 Michael Collison Juzhe Zhong * config/riscv/riscv.cc (riscv_estimated_poly_value): Implement TARGET_ESTIMATED_POLY_VALUE. (riscv_preferred_simd_mode): Implement TARGET_VECTORIZE_PREFERRED_SIMD_MODE.

[PATCH v5 07/10] vect: Verify that GET_MODE_NUNITS is a multiple of 2.

While working on autovectorizing for the RISCV port I encountered an issue where can_duplicate_and_interleave_p assumes that GET_MODE_NUNITS is a evenly divisible by two. The RISC-V target has vector modes (e.g. VNx1DImode), where GET_MODE_NUNITS is equal to one. Tested on RISCV and

[PATCH v5 02/10] RISC-V: autovec: Export policy functions to global scope

2023-03-02 Michael Collison Juzhe Zhong * config/riscv/riscv-vector-builtins.cc (get_tail_policy_for_pred): Remove static declaration to to make externally visible. (get_mask_policy_for_pred): Ditto. * config/riscv/riscv-vector-builtins.h

[PATCH v5 10/10] RISC-V: autovec: This patch supports 8 bit auto-vectorization in riscv.

From: Kevin Lee 2023-04-14 Kevin Lee gcc/testsuite/ChangeLog: * config/riscv/riscv.cc (riscv_autovectorize_vector_modes): Add new vector mode * gcc.target/riscv/rvv/autovec/loop-add-rv32.c: Support 8bit type * gcc.target/riscv/rvv/autovec/loop-add.c: Ditto *

[PATCH v5 03/10] RISC-V:autovec: Add auto-vectorization support functions

2023-04-24 Michael Collison Juzhe Zhong * config/riscv/riscv-v.cc (riscv_vector_preferred_simd_mode): New function. (get_mask_policy_no_pred): Ditto. (get_tail_policy_no_pred): Ditto. (riscv_vector_mask_mode_p): Ditto.

[PATCH v5 09/10] RISC-V: autovec: This patch adds a guard for VNx1 vectors that are present in ports like riscv.

From: Kevin Lee Kevin Lee gcc/ChangeLog: * tree-vect-data-refs.cc (vect_grouped_store_supported): Add new condition --- gcc/tree-vect-data-refs.cc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/gcc/tree-vect-data-refs.cc b/gcc/tree-vect-data-refs.cc index

[PATCH v5 08/10] RISC-V:autovec: Add autovectorization tests for binary integer

2023-04-05 Michael Collison * gcc.target/riscv/rvv/autovec/loop-and-rv32.c: New test to verify code generation of vector "and" on rv32. * gcc.target/riscv/rvv/autovec/loop-and.c: New test to verify code generation of vector "and" on rv64. *

Re: [PATCH v2] RISC-V: Fix sync.md and riscv.cc whitespace errors

On 26 April 2023 23:21:06 CEST, Patrick O'Neill wrote: >This patch fixes whitespace errors introduced with >https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616807.html > >2023-04-26 Patrick O'Neill > >gcc/ChangeLog: > > * config/riscv/riscv.cc: Fix whitespace. > *

[PATCH v5 00/10] RISC-V: autovec: Add autovec support

This series of patches adds foundational support for RISC-V auto-vectorization support. These patches are based on the current upstream rvv vector intrinsic support and is not a new implementation. Most of the implementation consists of adding the new vector cost model, the autovectorization

[PATCH v5 06/10] RISC-V:autovec: Add autovectorization tests for add & sub

2023-03-02 Michael Collison Vineet Gupta * gcc.target/riscv/rvv/autovec: New directory for autovectorization tests. * gcc.target/riscv/rvv/autovec/loop-add-rv32.c: New test to verify code generation of vector add on rv32. *

[PATCH v5 05/10] RISC-V:autovec: Add autovectorization patterns for binary integer & len_load/store

2023-04-25 Michael Collison Juzhe Zhong * config/riscv/riscv.md (riscv_vector_preferred_simd_mode): Include vector-iterators.md. * config/riscv/vector-auto.md: New file containing autovectorization patterns. * config/riscv/vector.md: Remove

[PATCH v5 01/10] RISC-V: autovec: Add new predicates and function prototypes

2023-04-24 Michael Collison Juzhe Zhong * config/riscv/riscv-protos.h (riscv_vector_preferred_simd_mode): New. (riscv_vector_mask_mode_p): Ditto. (riscv_vector_get_mask_mode): Ditto. (emit_vlmax_vsetvl): Ditto.

Re: [PATCH] RISC-V: Fix sync.md and riscv.cc whitespace errors

On 26 April 2023 23:10:01 CEST, Andreas Schwab wrote: >On Apr 26 2023, Patrick O'Neill wrote: > >> @@ -290,10 +290,10 @@ >>[(set (match_operand:GPR 0 "register_operand" "=") >> (match_operand:GPR 1 "memory_operand" "+A")) >> (set (match_dup 1) >> -(unspec_volatile:GPR

[PATCH v2] RISC-V: Fix sync.md and riscv.cc whitespace errors

This patch fixes whitespace errors introduced with https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616807.html 2023-04-26 Patrick O'Neill gcc/ChangeLog: * config/riscv/riscv.cc: Fix whitespace. * config/riscv/sync.md: Fix whitespace. Signed-off-by: Patrick O'Neill ---

[Bug c++/109241] [13 Regression] ICE Segmentation fault for statement expression with a local type inside inside a generic lambda inside a generic lambda since r13-6722-gb323f52ccf966800

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109241 --- Comment #4 from CVS Commits --- The trunk branch has been updated by Jason Merrill : https://gcc.gnu.org/g:d60cbbfaa9a3ad3bd1f613be95add939c16fc9a1 commit r14-278-gd60cbbfaa9a3ad3bd1f613be95add939c16fc9a1 Author: Jason Merrill Date:

[Bug c++/69836] compilation error with constexpr in template types with redeclared methods

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69836 --- Comment #6 from CVS Commits --- The trunk branch has been updated by Jason Merrill : https://gcc.gnu.org/g:1e27e7e0985e055b3d4ec92e93976b709fdbe425 commit r14-277-g1e27e7e0985e055b3d4ec92e93976b709fdbe425 Author: Jason Merrill Date: Wed

[pushed] c++: remove nsdmi_inst hashtable

Tested x86_64-pc-linux-gnu, applying to trunk. -- 8< -- It occurred to me that we have a perfectly good DECL_INITIAL field to put the instantiated DMI into, we don't need a separate hash table. gcc/cp/ChangeLog: * init.cc (nsdmi_inst): Remove. (maybe_instantiate_nsdmi_init):

[pushed] c++: local class in nested generic lambda [PR109241]

Tested x86_64-pc-linux-gnu, applying to trunk. -- 8< -- The earlier fix for PR109241 avoided the crash by handling a type with no TREE_BINFO. But we want to move toward doing the partial substitution of classes in generic lambdas, so let's take a step in that direction. PR c++/109241

[pushed] c++: unique friend shenanigans [PR69836]

Tested x86_64-pc-linux-gnu, applying to trunk. -- 8< -- Normally we re-instantiate a function declaration when we start to instantiate the body in case of multiple declarations. In this wacky testcase, this causes a problem because the type of the w_counter parameter depends on its declaration

Re: [PATCH] RISC-V: Fix sync.md and riscv.cc whitespace errors

On Apr 26 2023, Patrick O'Neill wrote: > @@ -290,10 +290,10 @@ >[(set (match_operand:GPR 0 "register_operand" "=") > (match_operand:GPR 1 "memory_operand" "+A")) > (set (match_dup 1) > - (unspec_volatile:GPR [(match_operand:GPR 2 "reg_or_0_operand" "rJ") > -

[Bug tree-optimization/109638] unsigned > 1 ? 0 : n is not optimized to n == 1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109638 --- Comment #1 from Andrew Pinski --- This should do it, I think: (simplify (cond (lt @1 integer_onep@2) integer_zerop @1) (if (TYPE_UNSIGNED (type)) (convert (eq @1 @2

[Bug tree-optimization/109638] New: unsigned > 1 ? 0 : n is not optimized to n == 1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109638 Bug ID: 109638 Summary: unsigned > 1 ? 0 : n is not optimized to n == 1 Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: missed-optimization Severity:

[PATCH] RISC-V: Fix sync.md and riscv.cc whitespace errors

This patch fixes whitespace errors introduced with https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616807.html 2023-04-26 Patrick O'Neill gcc/ChangeLog: * config/riscv/riscv.cc: Fix whitespace. * config/riscv/sync.md: Fix whitespace. Signed-off-by: Patrick O'Neill ---

[Bug c++/109625] [14 regression] 'error: use of built-in trait ‘__type_pack_element’ in function signature; use library traits instead' when building folly

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109625 Sam James changed: What|Removed |Added Resolution|--- |MOVED Status|UNCONFIRMED

Re: libsanitizer: sync from master

On 4/26/23 20:31, Florian Weimer wrote: > * Martin Liška: > >> On 11/15/22 16:47, Martin Liška wrote: >>> Hi. >>> >>> I've just pushed libsanitizer update that was tested on x86_64-linux and >>> ppc64le-linux systems. >>> Moreover, I run bootstrap on x86_64-linux and checked ABI difference with

Re: libsanitizer: sync from master

On 4/26/23 20:31, Florian Weimer wrote: > * Martin Liška: > >> On 11/15/22 16:47, Martin Liška wrote: >>> Hi. >>> >>> I've just pushed libsanitizer update that was tested on x86_64-linux and >>> ppc64le-linux systems. >>> Moreover, I run bootstrap on x86_64-linux and checked ABI difference with

Re: libsanitizer: sync from master

On 4/26/23 21:23, H.J. Lu wrote: > On Wed, Apr 26, 2023 at 6:52 AM Martin Liška wrote: >> >> On 11/15/22 16:47, Martin Liška wrote: >>> Hi. >>> >>> I've just pushed libsanitizer update that was tested on x86_64-linux and >>> ppc64le-linux systems. >>> Moreover, I run bootstrap on x86_64-linux

Re: libsanitizer: sync from master

On 4/26/23 21:23, H.J. Lu wrote: > On Wed, Apr 26, 2023 at 6:52 AM Martin Liška wrote: >> >> On 11/15/22 16:47, Martin Liška wrote: >>> Hi. >>> >>> I've just pushed libsanitizer update that was tested on x86_64-linux and >>> ppc64le-linux systems. >>> Moreover, I run bootstrap on x86_64-linux

Re: libsanitizer: sync from master

On 26 April 2023 20:31:10 CEST, Florian Weimer via Fortran wrote: >* Martin Liška: > >> On 11/15/22 16:47, Martin Liška wrote: >>> Hi. >>> >>> I've just pushed libsanitizer update that was tested on x86_64-linux and >>> ppc64le-linux systems. >>> Moreover, I run bootstrap on x86_64-linux and

Re: libsanitizer: sync from master

On 26 April 2023 20:31:10 CEST, Florian Weimer via Fortran wrote: >* Martin Liška: > >> On 11/15/22 16:47, Martin Liška wrote: >>> Hi. >>> >>> I've just pushed libsanitizer update that was tested on x86_64-linux and >>> ppc64le-linux systems. >>> Moreover, I run bootstrap on x86_64-linux and

Re: [PATCH] c++: Micro-optimize most_specialized_partial_spec

On Thu, Sep 1, 2022 at 2:40 PM Jason Merrill wrote: > > On 8/31/22 17:15, Patrick Palka wrote: > > This introduces an early exit test to most_specialized_partial_spec for > > the common case where we have no partial specializations, which allows > > us to avoid some unnecessary work. In passing,

[COMMITTED 4/5] Rename ssa_global_cache to ssa_cache and add has_range

The original ssa_global_cache was intended to simply be the global cache for ranger, but uses of it have since percolated such that it is really just a range acche for a list of ssa-names. This patch renames it from "ssa_global_cache" to "ssa_cache". It also adds a method called "has_range"

[COMMITTED 5/5] PR tree-optimization/108697 - Create a lazy ssa_cache.

Sparsely used ssa caches can benefit from using a bitmap to determine if a name already has an entry.  The path_query class was already managing something like this internally, but there is benefit to making it generally available. ssa_lazy_cache inherits from ssa_cache and adds management of

[COMMITTED 3/5] Add sbr_lazy_vector and adjust (e)vrp sparse cache

This implements a sparse vector class for rangers cache and uses it bey default except when the CFG is very small, in qhich case the original full vectors are faster.  It works like a normal vector cache (in fact it inherits from it), but uses a sparse bitmap to determine whether a vector

[COMMITTED 2/5] Quicker relation check.

If either of the SSA names in a comparison do not have any equivalences or relations, we can short-circuit the check slightly and be a bit faster. Bootstrapped on x86_64-pc-linux-gnu with no regressions.  Pushed. Andrew From ee03aca78fb5739f4cd76cb30332f8aff2c5243a Mon Sep 17 00:00:00 2001

[COMMITTED 1/5] PR tree-optimization/109417 - Don't save ssa-name pointer in dependency cache.

On 4/25/23 22:34, Jeff Law wrote: On 4/24/23 07:51, Andrew MacLeod wrote: Its not a real cache..  its merely a statement shortcut in dependency analysis to avoid re-parsing statements every time we look at them for dependency analysis It is not suppose to be used for anything other

[Bug tree-optimization/108697] constructing a path-range-query is expensive

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108697 --- Comment #7 from CVS Commits --- The master branch has been updated by Andrew Macleod : https://gcc.gnu.org/g:0a38f677463ff8a4fb61b049263aa596ef6471a7 commit r14-275-g0a38f677463ff8a4fb61b049263aa596ef6471a7 Author: Andrew MacLeod Date:

[Bug tree-optimization/109417] [13 Regression] ICE on valid code at -O3 on x86_64-linux-gnu: Segmentation fault since r13-6945

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109417 --- Comment #5 from CVS Commits --- The master branch has been updated by Andrew Macleod : https://gcc.gnu.org/g:40c7f943e882e8c5eccf45fc28146559f446764d commit r14-271-g40c7f943e882e8c5eccf45fc28146559f446764d Author: Andrew MacLeod Date:

Re: libsanitizer: sync from master

On Wed, Apr 26, 2023 at 6:52 AM Martin Liška wrote: > > On 11/15/22 16:47, Martin Liška wrote: > > Hi. > > > > I've just pushed libsanitizer update that was tested on x86_64-linux and > > ppc64le-linux systems. > > Moreover, I run bootstrap on x86_64-linux and checked ABI difference with > >

Re: libsanitizer: sync from master

On Wed, Apr 26, 2023 at 6:52 AM Martin Liška wrote: > > On 11/15/22 16:47, Martin Liška wrote: > > Hi. > > > > I've just pushed libsanitizer update that was tested on x86_64-linux and > > ppc64le-linux systems. > > Moreover, I run bootstrap on x86_64-linux and checked ABI difference with > >

[Bug tree-optimization/109637] unnecessary range check in complete switch on bitfield

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109637 --- Comment #5 from Andrew Macleod --- Perhaps switch conv just needs to look at it...

Re: [PATCH] GCC-13/changes: Add note about iostream usage

On Wed, Apr 26, 2023 at 12:07 PM Jonathan Wakely via Gcc-patches wrote: > > On 26/04/23 09:53 -0700, Andrew Pinski wrote: > >This adds a note about iostream usage so it does not catch others > >in surpise like it has already. > > > >OK? > > Thanks, I agree we should add something, but have some

[Bug target/109636] [14 Regression] ICE: in paradoxical_subreg_p, at rtl.h:3205 with -O -mcpu=a64fx

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109636 Andrew Pinski changed: What|Removed |Added Known to work|13.0|

Re: [PATCH] GCC-13/changes: Add note about iostream usage

On 26/04/23 09:53 -0700, Andrew Pinski wrote: This adds a note about iostream usage so it does not catch others in surpise like it has already. OK? Thanks, I agree we should add something, but have some comments below. --- htdocs/gcc-13/changes.html | 5 + 1 file changed, 5 insertions(+)

[Bug tree-optimization/109637] unnecessary range check in complete switch on bitfield

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109637 --- Comment #4 from Andrew Pinski --- (In reply to Andrew Macleod from comment #3) > we know the range of _2 is [0, 3].. wonder why we don't know that about > _1... having a look I assume the range of _1 is [-INF, +INF] (aka [0, 3] aka

[Bug tree-optimization/109637] unnecessary range check in complete switch on bitfield

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109637 --- Comment #3 from Andrew Macleod --- Just to add: 040.evrp: _2 : [irange] int [0, 3] NONZERO 0x3 _3 : [irange] int [0, 3] NONZERO 0x3 : _1 = s_5(D)->x; _2 = (int) _1; switch (_1) [INV], case 1: [INV], case 2: [INV], case 3:

[Bug tree-optimization/109637] unnecessary range check in complete switch on bitfield

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109637 Andrew Macleod changed: What|Removed |Added CC||amacleod at redhat dot com ---

Re: libsanitizer: sync from master

* Martin Liška: > On 11/15/22 16:47, Martin Liška wrote: >> Hi. >> >> I've just pushed libsanitizer update that was tested on x86_64-linux and >> ppc64le-linux systems. >> Moreover, I run bootstrap on x86_64-linux and checked ABI difference with >> abidiff. > > Hello. > > And I've done the

Re: libsanitizer: sync from master

* Martin Liška: > On 11/15/22 16:47, Martin Liška wrote: >> Hi. >> >> I've just pushed libsanitizer update that was tested on x86_64-linux and >> ppc64le-linux systems. >> Moreover, I run bootstrap on x86_64-linux and checked ABI difference with >> abidiff. > > Hello. > > And I've done the

[Bug tree-optimization/109637] unnecessary range check in complete switch on bitfield

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

[Bug middle-end/109637] unnecessary range check in complete switch on bitfield

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109637 Andrew Pinski changed: What|Removed |Added Keywords||missed-optimization

[Bug middle-end/109637] New: unnecessary range check in complete switch on bitfield

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109637 Bug ID: 109637 Summary: unnecessary range check in complete switch on bitfield Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug libstdc++/108969] [13/14 Regression] Initializing iostreams in the library needs a GLIBCXX_3.4.31 versioned symbol

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108969 Xi Ruoyao changed: What|Removed |Added CC||bremende55 at gmail dot com --- Comment

[Bug c++/109633] segfault using cout after set with simple prog from cppreference.com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109633 Xi Ruoyao changed: What|Removed |Added Resolution|INVALID |DUPLICATE CC|

Re: [PATCH v4 05/10] RISC-V:autovec: Add autovectorization patterns for binary integer operations

Hi Michael, I have the diff below for the binops in my tree locally. Maybe something like this works for you? Untested but compiles and the expander helpers would need to be fortified obviously. Regards Robin -- gcc/ChangeLog: * config/riscv/autovec.md (3): New binops expander.

☺ Buildbot (Sourceware): gccrust - build successful (master)

A passing build has been detected on builder gccrust-debian-testing-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/146/builds/949 Build state: build successful Revision: 419e1cff1102eb89c2e4a22b6251cce382bcbe61 Worker: bbo1-1

[Bug target/109636] New: [14 Regression] ICE: in paradoxical_subreg_p, at rtl.h:3205 with -O -mcpu=a64fx

n/aarch64-unknown-linux-gnu-as --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-r14-268-20230426091040-ge02f68df385-checking-yes-rtl-df-extra-aarch64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 14.0.0 20230426 (experimental) (GCC)

☺ Buildbot (Sourceware): gccrust - build successful (master)

A passing build has been detected on builder gccrust-rawhide-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/132/builds/954 Build state: build successful Revision: 727056301b2124649daacc29a23bb4b357a25173 Worker: bb1-2 Build

[Bug c++/109633] segfault using cout after set with simple prog from cppreference.com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109633 --- Comment #4 from Jo --- good idea, thank you

[committed] RISCV: Inline subword atomic ops

Committed - I had to reformat the changelog so it would push and resolve a trivial merge conflict in riscv.opt. --- RISC-V has no support for subword atomic operations; code currently generates libatomic library calls. This patch changes the default behavior to inline subword atomic calls

  1   2   3   4   >