[r14-2386 Regression] FAIL: gcc.target/i386/pr91681-1.c scan-assembler-not xor on Linux/x86_64

On Linux/x86_64, bdf2737cda53a83332db1a1a021653447b05a7e7 is the first bad commit commit bdf2737cda53a83332db1a1a021653447b05a7e7 Author: Roger Sayle Date: Fri Jul 7 20:39:58 2023 +0100 i386: Improve __int128 argument passing (in ix86_expand_move). caused FAIL: gcc.target/i386/pr82580.c

Add missing dump_file check

Hi, I forgot to check dump_file being non-NULL before writting to it. It is somewhat odd that this does not trigger more often - I will take deeper look tomorrow, but I am checking this in as obvious to avoid ICE. Honza gcc/ChangeLog: PR tree-optimization/110600 * cfgloopmanip.cc

[r14-2383 Regression] FAIL: gcc.dg/unroll-7.c scan-rtl-dump-not loop2_unroll "Invalid sum" on Linux/x86_64

On Linux/x86_64, 768f00e3e84123e8d0f1bf28a3b2e0b7995402f1 is the first bad commit commit 768f00e3e84123e8d0f1bf28a3b2e0b7995402f1 Author: Jan Hubicka Date: Fri Jul 7 19:16:59 2023 +0200 Fix some profile consistency testcases caused FAIL: gcc.dg/pr43864-2.c scan-tree-dump-times pre "if "

Fix profile update in tree-ssa/update-cunroll.c

Fix tree-ssa/update-cunroll.c In this testcase the profile is misupdated before loop has two exits. The first exit is one eliminated by complete unrolling while second exit remains. We remove first exit but forget about fact that the source BB of other exit will then have higher frequency making

Re: [Patch, fortran] Fix default type bugs in gfortran [PR99139, PR99368]

On Sat, Jul 08, 2023 at 03:23:31PM +0100, Paul Richard Thomas wrote: > The attached patch incorporates two of Steve's "Orphaned Patches" - > https://gcc.gnu.org/pipermail/fortran/2023-June/059423.html Thanks Paul for picking up the pieces I left behind. A few nits below. > They have in common th

Re: [Patch, fortran] Fix default type bugs in gfortran [PR99139, PR99368]

Hi Paul, thanks for taking this. I have just a minor comment regards coding style: + if (tmp + && tmp->attr.generic + && (tmp = gfc_find_dt_in_generic (tmp))) + { + if (tmp->attr.flavor == FL_DERIVED)

[Patch, fortran] Fix default type bugs in gfortran [PR99139, PR99368]

The attached patch incorporates two of Steve's "Orphaned Patches" - https://gcc.gnu.org/pipermail/fortran/2023-June/059423.html They have in common that they both involve faults in use of default type and that I was the ultimate cause of the bugs. The patch regtests with the attached testcases.

Re: [PATCH] Fortran: fixes for procedures with ALLOCATABLE,INTENT(OUT) arguments [PR92178]

Hi Mikael, Am 08.07.23 um 14:07 schrieb Mikael Morin: here is what I'm finally coming to.  This patch fixes my example, but is otherwise untested. The patch has grown enough that I'm tempted to fix my example separately, in its own commit. alright. I've interpreted this as a green light for v

[committed] cprop: Change return type of predicate functions from int to bool

Also change some internal variables from int to bool. gcc/ChangeLog: * cprop.cc (reg_available_p): Change return type from int to bool. (reg_not_set_p): Ditto. (try_replace_reg): Ditto. Change "success" variable to bool. (cprop_jump): Change return type from int to void and a

[committed] gcse: Change return type of predicate functions from int to bool

Also change some internal variables and function arguments from int to bool. gcc/ChangeLog: * gcse.cc (expr_equiv_p): Change return type from int to bool. (oprs_unchanged_p): Change return type from int to void and adjust function body accordingly. (oprs_anticipatable_p): Ditto.

Re: [PATCH] Fortran: fixes for procedures with ALLOCATABLE,INTENT(OUT) arguments [PR92178]

Hello, Le 07/07/2023 à 20:23, Harald Anlauf a écrit : Hi Mikael, Am 07.07.23 um 14:21 schrieb Mikael Morin: I'm attaching what I have (lightly) tested so far, which doesn't work. It seems gfc_conv_class_to_class reevaluates part of the original expression, which is not correct after deallocati

Re: [PATCH v4 1/2] c++: implement __is_unsigned built-in trait

Hi, Here is the benchmark result for is_unsigned: https://github.com/ken-matsui/gcc-benches/blob/main/is_unsigned.md#sat-jul--8-041510-am-pdt-2023 Time: -66.908% Peak Memory Usage: -42.5139% Total Memory Usage: -46.3483% Sincerely, Ken Matsui On Sat, Jul 8, 2023 at 4:13 AM Ken Matsui wrote: >

[PATCH v4 2/2] libstdc++: use new built-in trait __is_unsigned

This patch lets libstdc++ use new built-in trait __is_unsigned. libstdc++-v3/ChangeLog: * include/std/type_traits (is_unsigned): Use __is_unsigned built-in trait. (is_unsigned_v): Likewise. Signed-off-by: Ken Matsui --- libstdc++-v3/include/std/type_traits | 13

[PATCH v4 1/2] c++: implement __is_unsigned built-in trait

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

[committed] doc: Fix typos in Warning Options [PR110596]

Pushed as obvious. -- >8 -- gcc/ChangeLog: PR c++/110595 PR c++/110596 * doc/invoke.texi (Warning Options): Fix typos. --- gcc/doc/invoke.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 594b24d0

Re: [PATCH] Fortran: simplification of FINDLOC for constant complex arguments [PR110585]

Hi Harald, This is indeed obvious :-) Thanks for the patch. Paul On Fri, 7 Jul 2023 at 19:32, Harald Anlauf via Fortran wrote: > > Dear all, > > I intend to commit the attached obvious patch within 24h unless > someone objects. gfc_compare_expr() did not handle the case of > complex constants