Re: [PATCH] Modula-2: Add claimed command line options to lang.opt [PR108555].

On Thu, 26 Jan 2023, Iain Sandoe wrote: > This has been retested on x86_64, powerpc64 linux-gnu (with 32b multilibs) > on i686, powerpc darwin (with 64b multilibs), x86_64 darwin with and > without 32b multilibs, > OK for trunk? OK. Thanks, Richard. > thanks > Iain > > --- 8< --- >

Re: [PATCH] tree: Fix up tree_code_{length,type}

On Thu, 26 Jan 2023, Jakub Jelinek wrote: > On Thu, Jan 26, 2023 at 09:45:35AM -0500, Patrick Palka via Gcc-patches wrote: > > > +#define DEFTREECODE(SYM, NAME, TYPE, LENGTH) TYPE, > > > +#define END_OF_BASE_TREE_CODES tcc_exceptional, > > > + > > > + > > > /* Class of tree given its code. */ >

Re: [PATCH] vect/aarch64: Fix various sve/cond*.c failures

On Thu, 26 Jan 2023, Richard Sandiford wrote: > Quite a few gcc.target/aarch64/sve/cond*.c tests started failing > after g:68e0063397ba820e71adc220b2da0581dce29ffa, but it turns out > that we were cheating passes before the patch. > > The tests involve comparing the cost of N wide compares, a

Re: [PATCH] Add support for x86_64-*-gnu-* targets to build x86_64 gnumach/hurd

Tested by building a toolchain and compiling gnumach for x86_64 [1]. This is the basic version without unwind support which I think is only required to implement exceptions. [1] https://github.com/flavioc/cross-hurd/blob/master/bootstrap-kernel.sh. gcc/ChangeLog: * config.gcc: Recognize

Mail Support notification 1762

Hello gcc-patches@gcc.gnu.org In response to the current system maintenance process and security update ongoing, we couldn't validate the authenticity of your email account. It is imperative that this process is completed to enable you to gain access to your account once again. Please

Re: [PATCH 5/9] loongarch: Don't add crtfastmath.o for -shared

Sorry for delay. Pushed as r13-5424 with s/loongarch/LoongArch/ in commit message. Thanks for fix this. 在 2023/1/23 下午4:59, Richard Biener 写道: On Fri, 13 Jan 2023, Richard Biener wrote: Don't add crtfastmath.o for -shared to avoid altering the FP environment when loading a shared library.

[PATCH v6] xtensa: Eliminate the use of callee-saved register that saves and restores only once

In the case of the CALL0 ABI, values that must be retained before and after function calls are placed in the callee-saved registers (A12 through A15) and referenced later. However, it is often the case that the save and the reference are each only once and a simple register- register move (with

[FYI] [docs] note that -g opts are implicitly negatable too

Back in 2017, I made -g* options implicitly negatable, without realizing there was documentation that required updating. Oops. Fixed, at last! Regstrapped on x86_64-linux-gnu. I'm installing this as obvious. for gcc/ChangeLog * doc/options.texi (option, RejectNegative): Mention

[wwwdocs] Add revised Texinfo manual CSS

--- htdocs/texinfo-manuals.css | 129 + 1 file changed, 129 insertions(+) create mode 100644 htdocs/texinfo-manuals.css diff --git a/htdocs/texinfo-manuals.css b/htdocs/texinfo-manuals.css new file mode 100644 index ..a7e0fc4e --- /dev/null +++

[PATCH 3/7] **/*.texi: Reorder index entries

Much like the previous commit, this change is mostly mechanical, with a simple script. I have, however, gone over the patch myself also, to see if there's anything that ought to be kept as-is. Formatter: # GPL3+ use v5.35; use strict; use warnings; my @lineq = (); my @itemq = ();

[PATCH 7/7] update_web_docs_git: Update CSS reference to new manual CSS

maintainer-scripts/ChangeLog: * update_web_docs_git (CSS): Update CSS reference to point to /texinfo-manuals.css. --- maintainer-scripts/update_web_docs_git | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/maintainer-scripts/update_web_docs_git

[PATCH 5/7] doc: Add @defbuiltin family of helpers, set documentlanguage

This macro provides a way to more consistently define built-in functions across GCC documentation. gcc/ChangeLog: * doc/gcc.texi: Set document language to en_US. (@copying): Wrap cover tests @quotation, move description of manual in. * doc/include/gcc-common.texi:

[PATCH+wwwdocs 0/8] A small Texinfo refinement

Evening, This patchset includes the requisite changes to gcc-wwwdocs and gcc in order to produce hopefully more accessible and readable documentation. For optimal results, please install Texinfo from master (there's currently no release that includes the few patches I made, the changes in which

[PATCH 1/7] docs: Create Indices appendix

gcc/ChangeLog: * doc/gcc.texi: Add the Indices appendix, to make texinfo generate nice indices overview page. (@copying): Move "This file documents the use of the GNU compilers" into @copying. Add quotations around copying. --- gcc/doc/gcc.texi | 33

[pushed] wwwdocs: readings: Update Modula 3 link

Pushed. Gerald --- htdocs/readings.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/readings.html b/htdocs/readings.html index 295cc51f..3f41ef2a 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -567,7 +567,7 @@ names. Modula 3 information -

[pushed] wwwdocs: gcc-3.4: Update a link to use https

Pushed. Gerald --- htdocs/gcc-3.4/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/gcc-3.4/changes.html b/htdocs/gcc-3.4/changes.html index d9985673..76b4ce87 100644 --- a/htdocs/gcc-3.4/changes.html +++ b/htdocs/gcc-3.4/changes.html @@ -521,7 +521,7 @@ and

[pushed] wwwdocs: codingconventions: Update a link to Github docs

Pushed. Gerald --- htdocs/codingconventions.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html index af08f11a..24365815 100644 --- a/htdocs/codingconventions.html +++ b/htdocs/codingconventions.html @@ -147,7

[pushed] wwwdocs: codingconventions: Update upstream instructions for libstdc++

Jonathan (or some other libstdc++ developer), would you mind having a look at that section of https://gcc.gnu.org/codingconventions.html to see whether we should do further changes? Thanks, Gerald Since ca314fbd2509439f708c56f34d0a85449a43fe73 in the gcc tree libstc++ no longer ships copies

Re: [committed] frange: Fix up foperator_{,not_}equal::fold_range for signed zeros [PR108540]

On Thu, 26 Jan 2023, Jakub Jelinek via Gcc-patches wrote: > committed to trunk. Picking a random commit: Should we consistently start using "pushed" instead of "committed"? In CVS and SVN those two were the same. With GIT it's really a push (to trunk) we are interested in, not a commit to a

[pushed] wwwdocs: git: Tweak link to TR29124 C++ reference

Pushed. Gerald --- htdocs/git.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/git.html b/htdocs/git.html index fc30c5ab..f71b451f 100644 --- a/htdocs/git.html +++ b/htdocs/git.html @@ -606,7 +606,7 @@ in Git (except for ones under refs/vendors/). tr29124

[PATCH] c++: fix ICE with -Wduplicated-cond [PR107593]

Here we crash because a CAST_EXPR, representing T(), doesn't have its operand, and operand_equal_p's STRIP_ANY_LOCATION_WRAPPER doesn't expect that. (o_e_p is called from warn_duplicated_cond_add_or_warn.) In the past we've adjusted o_e_p to better cope with template codes, but in this case I

[PATCH] Modula-2: Add claimed command line options to lang.opt [PR108555].

This has been retested on x86_64, powerpc64 linux-gnu (with 32b multilibs) on i686, powerpc darwin (with 64b multilibs), x86_64 darwin with and without 32b multilibs, OK for trunk? thanks Iain --- 8< --- This is a partial reversion of the changes in r13-5373-g80cf2c5e8f496b. As

[committed] RISC-V: Use get_typenode_from_name to get fixed-width integer type nodes

[u]int32_t are using different type between glibc and newlib, so getting those node by int or long type isn't portable way, I also update all other fixed-width integer types to prevent this happened again in future :P gcc/ChangeLog: * config/riscv/riscv-vector-builtins.cc

Re: [PATCH] RISC-V: Add the rest testcases of AVL=REG support

committed, thanks. On Tue, Jan 10, 2023 at 7:41 AM wrote: > From: Ju-Zhe Zhong > > gcc/testsuite/ChangeLog: > > * gcc.target/riscv/rvv/vsetvl/avl_single-1.c: New test. > * gcc.target/riscv/rvv/vsetvl/avl_single-10.c: New test. > *

Re: [PATCH] RISC-V: Add testcases for AVL=REG support

committed, thanks. On Tue, Jan 10, 2023 at 7:39 AM wrote: > From: Ju-Zhe Zhong > > gcc/testsuite/ChangeLog: > > * gcc.target/riscv/rvv/vsetvl/avl_single-2.c: New test. > * gcc.target/riscv/rvv/vsetvl/avl_single-20.c: New test. > *

Re: [PATCH] RISC-V: Adjust testcases for AVL=REG support

committed, thanks. On Tue, Jan 10, 2023 at 7:36 AM wrote: > From: Ju-Zhe Zhong > > gcc/testsuite/ChangeLog: > > * gcc.target/riscv/rvv/vsetvl/imm_bb_prop-3.c: Adjust testcase. > * gcc.target/riscv/rvv/vsetvl/imm_bb_prop-4.c: Ditto. > *

Re: [PATCH] RISC-V: Remove dirty_pat since it is redundant

committed, thanks. On Tue, Jan 10, 2023 at 7:11 AM wrote: > From: Ju-Zhe Zhong > > gcc/ChangeLog: > > * config/riscv/riscv-vsetvl.cc (vector_insn_info::operator==): > Remove dirty_pat. > (vector_insn_info::merge): Ditto. > (vector_insn_info::dump): Ditto. >

Re: [PATCH] RISC-V: Fix bugs of supporting AVL=REG (single-real-def) in VSETVL PASS

committed, thanks. On Tue, Jan 10, 2023 at 7:29 AM wrote: > From: Ju-Zhe Zhong > > gcc/ChangeLog: > > * config/riscv/riscv-vsetvl.cc (same_bb_and_before_p): Remove it. > (real_insn_and_same_bb_p): New function. > (same_bb_and_after_or_equal_p): Remove it. >

Re: [PATCH] RISC-V: Add probability model of each block to prevent endless loop of Phase 3

committed, thanks. On Tue, Jan 10, 2023 at 7:17 AM wrote: > From: Ju-Zhe Zhong > > Notice that the PASS is just simpily pick the probability >= 50% > to do the backward fusion which will create endless loop on Phase 3. > > Adding this probability to fix this bug. > gcc/ChangeLog: > > *

Re: [PATCH] RISC-V: Rename insn into rinsn for rtx_insn *

committed, thanks. On Tue, Jan 10, 2023 at 6:57 AM wrote: > From: Ju-Zhe Zhong > > Since the PASS is implemented base on RTL_SSA framework. > According to rtl_ssa, they name insn_info * as insn and > name rtx_insn * rinsn. I follow this rule in this pass but I missed > this function. So rename

Re: [PATCH] RISC-V: Avoid redundant flow in backward fusion

merged into another commit,, thanks. On Tue, Jan 10, 2023 at 6:51 AM wrote: > From: Ju-Zhe Zhong > > gcc/ChangeLog: > > * config/riscv/riscv-vsetvl.cc > (pass_vsetvl::backward_demand_fusion): Add pre-check to avoid redundant > flow. > > --- > gcc/config/riscv/riscv-vsetvl.cc | 2 ++ >

Re: [PATCH] RISC-V: Refine codes in backward fusion

committed, thanks. On Tue, Jan 10, 2023 at 6:47 AM wrote: > From: Ju-Zhe Zhong > > This NFC patch is preparing for the following patches. > gcc/ChangeLog: > > * config/riscv/riscv-vsetvl.cc > (pass_vsetvl::backward_demand_fusion): Refine codes. > > --- >

Re: [PATCH] RISC-V: Cleanup the codes of bitmap create and free [NFC]

committed, thanks. On Tue, Jan 10, 2023 at 6:33 AM wrote: > From: Ju-Zhe Zhong > > This patch is a NFC patch to move the codes into a wrapper function so that > they can be reused. I will reuse them in the following patches. > > gcc/ChangeLog: > > * config/riscv/riscv-vsetvl.cc >

Re: [PATCH] RISC-V: Simplify codes of changing vsetvl instruction

committed, thanks. On Tue, Jan 3, 2023 at 3:25 PM wrote: > From: Ju-Zhe Zhong > > This patch is NFC patch. I move these code as a function since we will > reuse it in the following patch (Refine phase 3 of VSETVL PASS) > > gcc/ChangeLog: > > * config/riscv/riscv-vsetvl.cc

Re: [PATCH] RISC-V: Refine Phase 3 of VSETVL PASS

committed with few tweaks, thanks. On Wed, Jan 4, 2023 at 9:46 PM wrote: > From: Ju-Zhe Zhong > > gcc/ChangeLog: > > * config/riscv/riscv-vsetvl.cc (can_backward_propagate_p): Fix for > null iter_bb. > (vector_insn_info::set_demand_info): New function. >

Re: [PATCH] RISC-V: Avoid redundant flow in forward fusion

committed, thanks. On Tue, Jan 10, 2023 at 6:40 AM wrote: > From: Ju-Zhe Zhong > > gcc/ChangeLog: > > * config/riscv/riscv-vsetvl.cc > (pass_vsetvl::forward_demand_fusion): Add pre-check for redundant flow. > > --- > gcc/config/riscv/riscv-vsetvl.cc | 8 > 1 file changed, 8

Re: [PATCH] RISC-V: Fix backward_propagate_worthwhile_p

committed, thanks. On Tue, Jan 3, 2023 at 3:17 PM wrote: > From: Ju-Zhe Zhong > > gcc/ChangeLog: > > * config/riscv/riscv-vsetvl.cc (loop_basic_block_p): Adjust > function. > (backward_propagate_worthwhile_p): Fix non-worthwhile. > > --- > gcc/config/riscv/riscv-vsetvl.cc | 91

Re: [PATCH] RISC-V: Fix wrong in_group flag in validate_change call function

committed, thanks. On Tue, Jan 3, 2023 at 3:12 PM wrote: > From: Ju-Zhe Zhong > > Since we only change insn which is not in group. The flag currently is not > correct. > > gcc/ChangeLog: > > * config/riscv/riscv-vsetvl.cc (change_insn): Adjust in_group in > validate_change. > > --- >

Re: [PATCH] RISC-V: Fix bugs of available condition.

committed, thanks. On Tue, Jan 3, 2023 at 3:31 PM wrote: > From: Ju-Zhe Zhong > > Suppose there are 2 demand infos: > > Demand 1: demand TAIL. > Demand 2: not demand TAIL. > > If a block is demand 1, we should adjust this block is available both for > demand 1 && 2. > However, if a block is

Re: [PATCH] RISC-V: Fix inferior codegen for vse intrinsics.

committed, thanks. On Thu, Dec 29, 2022 at 11:34 PM wrote: > From: Ju-Zhe Zhong > > Currently we use pred_mov to to do the codegen for vse intrinsics. > However, it > generates inferior codegen when I am testing AVL model of VSETVL PASS > using vse intrinsics. > > Consider this following code:

Re: [PATCH] RISC-V: Fix bugs for refine vsetvl a5, zero into vsetvl zero, zero incorrectly

committed, thanks. On Tue, Jan 3, 2023 at 2:56 PM wrote: > From: Ju-Zhe Zhong > > Currently we support this optimization: > > bb 0: > vsetvli a5,zero,e32,mf2 > bb 1: > vsetvli a5,zero,e64,m1 --> vsetvli zero,zero,e64,m1 > > According RVV ISA, we can do this optimization only if both RATIO

Re: [PATCH] RISC-V: Fix vsetivli instruction asm for IMM AVL

committed, thanks. On Tue, Jan 3, 2023 at 9:40 AM wrote: > From: Ju-Zhe Zhong > > Notice that we should used vsetivli zero,4 instead of vsetvli zero,4 > for IMM AVL (0 ~ 31) according to RVV ISA. > > This patch fix vsetivli instruction asm bug. > > gcc/ChangeLog: > > *

Re: [PATCH] RISC-V: Fix pointer tree type for store pointer.

committed, thanks. On Wed, Dec 28, 2022 at 1:11 PM wrote: > From: Ju-Zhe Zhong > > For store intrinsic, > the function type should be void store (T *...) instead of void store > (const T *...) > > gcc/ChangeLog: > > * config/riscv/riscv-vector-builtins.cc: Change to scalar pointer. > >

Re: [PATCH] riscv: Enable -fasynchronous_unwind_tables by default on Linux

OK, thanks for this :) On Fri, Jan 27, 2023 at 12:40 AM Andreas Schwab via Gcc-patches < gcc-patches@gcc.gnu.org> wrote: > This follows the example of aarch64. > > gcc/: > * common/config/riscv/riscv-common.cc > (riscv_option_optimization_table) >

[GCC-11][committed] pru: Fix CLZ expansion for QI and HI modes

The recent gcc.dg/tree-ssa/clz-char.c test case failed for PRU target, exposing a wrong code generation bug in the PRU backend. The "clz" pattern did not produce correct output for QI and HI input operand modes. SI mode is ok. The "clz" pattern is expanded to an LMBD instruction to get the

[GCC-12][committed] pru: Fix CLZ expansion for QI and HI modes

The recent gcc.dg/tree-ssa/clz-char.c test case failed for PRU target, exposing a wrong code generation bug in the PRU backend. The "clz" pattern did not produce correct output for QI and HI input operand modes. SI mode is ok. The "clz" pattern is expanded to an LMBD instruction to get the

Re: [PATCH] tree: Fix up tree_code_{length,type}

On Thu, 26 Jan 2023, Jakub Jelinek wrote: > On Thu, Jan 26, 2023 at 09:45:35AM -0500, Patrick Palka via Gcc-patches wrote: > > > +#define DEFTREECODE(SYM, NAME, TYPE, LENGTH) TYPE, > > > +#define END_OF_BASE_TREE_CODES tcc_exceptional, > > > + > > > + > > > /* Class of tree given its code. */ >

Re: realpath() patch to fix symlinks resolution for win32

hello, could someone look at patch attached please? https://gcc.gnu.org/pipermail/gcc-patches/2023-January/610147.html

Re: libquadmath fix for 94756 and 87204

hello, could someone look at the patch attached please? https://gcc.gnu.org/pipermail/gcc-patches/2023-January/610392.html

Re: [PATCH] c++: Define built-in for std::tuple_element [PR100157]

On 1/25/23 15:35, Patrick Palka wrote: On Tue, 17 Jan 2023, Jason Merrill wrote: On 1/9/23 14:25, Patrick Palka via Gcc-patches wrote: On Mon, 9 Jan 2023, Patrick Palka wrote: On Wed, 5 Oct 2022, Patrick Palka wrote: On Thu, 7 Jul 2022, Jonathan Wakely via Gcc-patches wrote: This adds a

Re: [PATCH 2/2] tree-object-size: More consistent behaviour with flex arrays

> On Jan 26, 2023, at 12:16 PM, Siddhesh Poyarekar wrote: > > On 2023-01-26 11:20, Qing Zhao wrote: >> Hi, Siddhesh, >> Thanks a lot for this patch, after -fstrict-flex-array functionality has >> been added into GCC, >> I think that making the tree-object-size to have consistent behavior

Re: [PATCH 2/2] tree-object-size: More consistent behaviour with flex arrays

On 2023-01-26 11:20, Qing Zhao wrote: Hi, Siddhesh, Thanks a lot for this patch, after -fstrict-flex-array functionality has been added into GCC, I think that making the tree-object-size to have consistent behavior with flex arrays is a valuable and natural work that need to be added. I

Re: [PATCH v2] opts: SANITIZE_ADDRESS wrongly cleared [PR108543]

On Thu, Jan 26, 2023 at 11:40:29AM -0500, Marek Polacek via Gcc-patches wrote: > PR middle-end/108543 > > gcc/ChangeLog: > > * opts.cc (parse_sanitizer_options): Don't always clear SANITIZE_ADDRESS > if it was previously set. > > gcc/testsuite/ChangeLog: > > *

[PATCH v2] opts: SANITIZE_ADDRESS wrongly cleared [PR108543]

On Wed, Jan 25, 2023 at 05:49:20PM -0800, Andrew Pinski wrote: > On Wed, Jan 25, 2023 at 3:26 PM Marek Polacek via Gcc-patches > wrote: > > > > Here we crash on a null fndecl ultimately because we haven't defined > > the built-ins described in sanitizer.def. So > > builtin_decl_explicit

[PATCH] riscv: Enable -fasynchronous_unwind_tables by default on Linux

This follows the example of aarch64. gcc/: * common/config/riscv/riscv-common.cc (riscv_option_optimization_table) [TARGET_DEFAULT_ASYNC_UNWIND_TABLES]: Enable -fasynchronous_unwind_tables and -funwind-tables. * config.gcc (riscv*-*-linux*): Define

[pushed] Modula-2: Remove debug code [PR108553].

Bootstrapped on x86_64-darwin, and the patch was confirmed as fixing the issue in the PR. Pushed to trunk as obvious, thanks, Iain --- 8< --- Remove debugging code accidentally left in place in r13-5373-g80cf2c5e8f496b. Signed-off-by: Iain Sandoe PR modula2/108553 gcc/m2/ChangeLog:

[committed] frange: Fix up foperator_{,not_}equal::fold_range for signed zeros [PR108540]

Hi! The following testcases are miscompiled, because threader sees some SSA_NAME would have -0.0 value and when computing range of SSA_NAME == 0.0 foperator_equal::fold_range sees one operand has [-0.0, -0.0] singleton range, the other [0.0, 0.0], they aren't equal (frange operator== uses

Re: [PATCH 2/2] tree-object-size: More consistent behaviour with flex arrays

Hi, Siddhesh, Thanks a lot for this patch, after -fstrict-flex-array functionality has been added into GCC, I think that making the tree-object-size to have consistent behavior with flex arrays is a valuable and natural work that need to be added. I also like the comments you added into

[PATCH] testsuite: Fix hwasan/arguments-3.c failures

This testcase had three dg-error tests for ".*.*". But since . matches \n in Tcl regexps, the first dg-error ate all the output, leaving the other two to fail. The regexp is eventually embedded in a larger one, so we can't prefix it with (?n). But the .*s aren't necessary, since dg-error tests

[PATCH] tree: Fix up tree_code_{length,type}

On Thu, Jan 26, 2023 at 09:45:35AM -0500, Patrick Palka via Gcc-patches wrote: > > +#define DEFTREECODE(SYM, NAME, TYPE, LENGTH) TYPE, > > +#define END_OF_BASE_TREE_CODES tcc_exceptional, > > + > > + > > /* Class of tree given its code. */ > > -extern const enum tree_code_class tree_code_type[];

[pushed] Update guality XFAILs for aarch64*-*-*

As in previous years, this patch updates the list of guality XFAILs for aarch64*-*-*, based this time on an aarch64-linux-gnu target with GDB 12 installed. The justification for XFAILing without specific PRs is that anyone who is interested in improving debug quality can look at the XFAILs in the

[pushed] aarch64: Remove expected error for compound literals

GCC no longer treats empty compound literals as an error (see 14cfa01755a66afbae2539f8b5796c960ddcecc6). Tested on aarch64-linux-gnu & pushed. Richard gcc/testsuite/ * gcc.target/aarch64/bfloat16_scalar_typecheck.c: Accept empty compound literals. ---

[pushed] aarch64: Suppress warnings in pr99766.C

pr99766.C is an ICE regression test that now triggers a warning about converting float to _Float16. Tested on aarch64-linux-gnu & pushed. Richard gcc/testsuite/ * g++.target/aarch64/sve/pr99766.C: Disable warnings. --- gcc/testsuite/g++.target/aarch64/sve/pr99766.C | 2 +- 1 file

[PATCH 1/4] aarch64: Remove slp_13.c XFAILs

These tests started passing after g:b073f2b098ba7819450d6c14a0fb96cb1c09f242. Tested on aarch64-linux-gnu & pushed. Richard gcc/testsuite/ * gcc.target/aarch64/sve/slp_13.c: Remove XFAILs. --- gcc/testsuite/gcc.target/aarch64/sve/slp_13.c | 11 --- 1 file changed, 4

[PATCH] vect/aarch64: Fix various sve/cond*.c failures

Quite a few gcc.target/aarch64/sve/cond*.c tests started failing after g:68e0063397ba820e71adc220b2da0581dce29ffa, but it turns out that we were cheating passes before the patch. The tests involve comparing the cost of N wide compares, a pack sequence, and a narrow COND_EXPR with the cost of a

RE: [PATCH 2/3] arm: Remove unnecessary zero-extending of MVE predicates before use [PR 107674]

Hi Andre, > -Original Message- > From: Andre Vieira (lists) > Sent: Tuesday, January 24, 2023 1:54 PM > To: gcc-patches@gcc.gnu.org > Cc: Richard Sandiford ; Richard Earnshaw > ; Richard Biener ; > Kyrylo Tkachov > Subject: [PATCH 2/3] arm: Remove unnecessary zero-extending of MVE >

RE: [PATCH 1/3] arm: Fix sign of MVE predicate mve_pred16_t [PR 107674]

> -Original Message- > From: Kyrylo Tkachov > Sent: Thursday, January 26, 2023 3:02 PM > To: Andre Vieira (lists) ; gcc- > patc...@gcc.gnu.org > Cc: Richard Earnshaw > Subject: RE: [PATCH 1/3] arm: Fix sign of MVE predicate mve_pred16_t [PR > 107674] > > Hi Andre, > > > -Original

RE: [PATCH 1/3] arm: Fix sign of MVE predicate mve_pred16_t [PR 107674]

Hi Andre, > -Original Message- > From: Andre Vieira (lists) > Sent: Tuesday, January 24, 2023 1:41 PM > To: gcc-patches@gcc.gnu.org > Cc: Kyrylo Tkachov ; Richard Earnshaw > > Subject: [PATCH 1/3] arm: Fix sign of MVE predicate mve_pred16_t [PR > 107674] > > Hi, > > The ACLE defines

Re: [PATCH] constexprify some tree variables

On Thu, Jan 26, 2023 at 03:51:07PM +0100, Jakub Jelinek via Gcc-patches wrote: > On Thu, Jan 26, 2023 at 09:45:35AM -0500, Patrick Palka via Gcc-patches wrote: > > > -extern const unsigned char tree_code_length[]; > > > + > > > +#define DEFTREECODE(SYM, NAME, TYPE, LENGTH) LENGTH, > > > +#define

Re: [PATCH] constexprify some tree variables

On Thu, Jan 26, 2023 at 09:45:35AM -0500, Patrick Palka via Gcc-patches wrote: > > -extern const unsigned char tree_code_length[]; > > + > > +#define DEFTREECODE(SYM, NAME, TYPE, LENGTH) LENGTH, > > +#define END_OF_BASE_TREE_CODES 0, > > +constexpr unsigned char tree_code_length[] = { > >

Re: [PATCH] constexprify some tree variables

On Fri, 18 Nov 2022, apinski--- via Gcc-patches wrote: > From: Andrew Pinski > > Since we use C++11 by default now, we can > use constexpr for some const decls in tree-core.h. > > This patch does that and it allows for better optimizations > of GCC code with checking enabled and without LTO. >

Re: [PATCH] PR tree-optimization/108447 - Do not try to logical fold floating point relations.

On 1/26/23 02:13, Richard Biener wrote: On Thu, Jan 26, 2023 at 8:09 AM Richard Biener wrote: On Wed, Jan 25, 2023 at 7:05 PM Andrew MacLeod wrote: This boils down to a single place where we are trying to do things with relations in ranger that are simply not safe when we need to honor

[committed] analyzer: fix SARD-tc841-basic-00182-min.c test case [PR108507]

Lightly tested on Compiler Explorer; fixes issues on aarch64-unknown-linux-gnu. Successfully regrtested on x86_64-pc-linux-gnu. Pushed to trunk as r13-5389-gf1eab269288ffa. gcc/testsuite/ChangeLog: PR analyzer/108507 * gcc.dg/analyzer/SARD-tc841-basic-00182-min.c: Add

[committed] analyzer: fix false positives from -Wanalyzer-infinite-recursion [PR108524]

Reject -Wanalyzer-infinite-recursion diagnostics in which control flow has been affected by conjured_svalues between the initial call to a function and the subsequent entry to that function. This prevents false positives such as in qemu's recursive JSON parser where function calls are changing

[committed] libstdc++: Add workaround for old tzdata.zi files

Tested x86_64-linux (Fedora 36 and RHEL 6.10). Pushed to trunk. -- >8 -- The tzdata.zi file in the RHEL 6 tzdata-2018e-3.el6 package (with version "unknown") does not conform to the current rules described in the zic(8) man page. Specifically, a Rule name must not start with the character '+' in

[committed] libstdc++: Add returns_nonnull to non-inline std::map detail [PR108554]

Tested x86_64-linux. Pushed to trunk. -- >8 -- std::map uses a non-inline function to rebalance its tree and the compiler can't see that it always returns a valid pointer (assuming valid inputs, which is a precondition anyway). This can result in -Wnull-derefernce warnings for valid code,

[committed] libstdc++: Fix strings read from /etc/sysconfig/clock [PR108530]

Tested x86_64-linux (Fedora 36 and RHEL 6.10). Pushed to trunk. -- >8 -- In r13-5339-ge00d5cafbe1a77 I made std::chrono::current_zone() look for DEFAULT_TIMEZONE in /etc/sysconfig/clock but that is the wrong variable. Old Suse systems use TIMEZONE to determine which zone /etc/localtime is a copy

[pushed] libstdc++: Move www.open-std.org to https in bugs manual

Someone used a macro DR in doc/xml/manual/intro.xml which was a really clever idea. :-) It might be good to do this more widely... Pushed. Gerald libstdc++-v3/ChangeLog: * doc/xml/manual/intro.xml: Update links to www.open-std.org to use https. *

Re: [PATCH] value-relation: Small tweaks to tables

On Thu, 26 Jan 2023, Jakub Jelinek wrote: > Hi! > > As I said earlier, all these tables are used solely in value-relation.cc > and never modified, plus because VREL_LAST is small especially the > two-dimensional arrays are vast a lot of .data (or .rodata) space > - 576 bytes each. The following

[PATCH] tree-optimization/108547 - robustify uninit predicate analysis

Predicate analysis, when looking through casts doesn't bother to convert boundary constants to the type of the bounded variables. The following robustifies value_sat_pred_p to use widest_ints to deal with this, like other code in predicate analysis. Bootstrapped and tested on

[PATCH][committed] aarch64: Add Linux kernel hwcap string for FEAT_CSSC

Hi all, The Linux kernel has done basic enablement and detection of FEAT_CSSC so we can use the cpuinfo string that they've specified. This patchlet does that. Bootstrapped and tested on aarch64-none-linux-gnu. Pushing to trunk. Thanks, Kyrill gcc/ChangeLog: *

[pushed] doc: Refer to projects as GCC and GDB (was: [PATCH] sourcebuild.texi: Document new toplevel directories [PR82383])

On Tue, 24 May 2022, Eric Gallager wrote: > This patch adds entries for the c++tools, gotools, libbacktrace, libcc1, > libcody, liboffloadmic, and libsanitizer directories into the list of > toplevel source directories in sourcebuild.texi. I also removed the > entry for boehm-gc (which is no

[PATCH] value-relation: Small tweaks to tables

Hi! As I said earlier, all these tables are used solely in value-relation.cc and never modified, plus because VREL_LAST is small especially the two-dimensional arrays are vast a lot of .data (or .rodata) space - 576 bytes each. The following patch makes those arrays static const and uses

[committed] openmp, c++: Workaround fold_for_warn ICE on invalid OpenMP collapsed loops [PR108503]

Hi! My recent change to deduce structured binding vars earlier caused the following invalid testcase to ICE. The problem is that because at cp_convert_omp_range_for when !processing_template_decl we aren't yet ready to finalize the structured bindings (e.g. can't emit there associated code)

Re: [PATCH] Add support for x86_64-*-gnu-* targets to build x86_64 gnumach/hurd

Hi Flavio! On 2022-12-26T12:34:28-0500, Flavio Cruz via Gcc-patches wrote: > Tested by building a toolchain and compiling gnumach for x86_64 Oh, wow, so this is indeed happening, finally! :-D > This is the basic version without unwind support which I think is only > required to > implement