Re: [PATCH] Check sorting of MAINTAINERS

Hi! On 2022-01-10T17:14:00+0100, Martin Liška wrote: > The script is capable of checking if MAINTAINER names are sorted > alphabetically. Irrespective of the pre-existing issue that a concept of a first and a last name doesn't exist in all cultures, and thus sorting by the latter is questionable

[PATCH] Enhance vec_pack_trunc for integral mode mask.

For testcase in PR, the patch supports QI:4 -> HI:16 pack with multi steps(first pack QI:4 -> QI:8 through vec_pack_sbool_trunc_qi, then pack QI:8 -> HI:16 through vec_pack_trunc_hi). Similar for QI:2 -> HI:16 which is test4 in mask-pack-prefer-128.c. Bootstrapped both with and w/o '--with-arch=na

Re: [PATCH] Fix tree-optimization/101941: IPA splitting out function with error attribute

On Mon, Jan 17, 2022 at 10:36 AM Jakub Jelinek via Gcc-patches wrote: > > On Fri, Jan 14, 2022 at 09:41:35AM +0100, Jan Hubicka via Gcc-patches wrote: > > > > > > > --- a/gcc/ipa-split.c > > > > > > > +++ b/gcc/ipa-split.c > > > > > > > @@ -873,7 +873,7 @@ visit_bb (basic_block bb, basic_block >

Re: [PATCH] Fix for GCC '-MF' option cannot deal with long paths in Windows

On Mon, Jan 17, 2022 at 8:35 AM Sundeep KOKKONDA via Gcc-patches wrote: > > Hello, > > > > The '-MF' option cannot deal with path size >256 characters in Windows. This > patch is to fix this long path issue with -MF option. > > Let me know is it ok to commit? I don't think this is the right place

Re: [PATCH 2/6] libstdc++: Import the fast_float library

> From: Patrick Palka via Gcc-patches > Date: Sun, 16 Jan 2022 19:06:48 +0100 > We're going to use the fast_float library in our (compiled-in) > floating-point std::from_chars implementation for faster and more > portable parsing of binary32/64 decimal strings. > > The single file fast_float.h

[PATCH] testsuite: Adjust possibly fragile slp-perm-9.c [PR104015]

Hi, As discussed in PR104015, the test case slp-perm-9.c can be fragile when vectorizer tries to use different vectorisation strategies. As Richard suggested, this patch tries to make the check not sensitive on the re-trying times by removing the times checking. To still retain the test coverage

Re: [PATCH] [i386]Adjust testcase for --target_board='unix{-m64\ -march=cascadelake}'

On Tue, Jan 18, 2022 at 10:57 AM liuhongt via Gcc-patches wrote: > > Change scan-assembler from "\tucomisd" to "\t\[v\]?ucomisd". It's an obvious "fix", Pushed to trunk. > > refer to https://gcc.gnu.org/pipermail/gcc-regression/2022-January/076241.html > > gcc/testsuite/ChangeLog: > > * g+

[PATCH] [i386]Adjust testcase for --target_board='unix{-m64\ -march=cascadelake}'

Change scan-assembler from "\tucomisd" to "\t\[v\]?ucomisd". refer to https://gcc.gnu.org/pipermail/gcc-regression/2022-January/076241.html gcc/testsuite/ChangeLog: * g++.target/i386/pr103973-1.C: Change scan-assembler from "\tucomisd" to "\t\[v\]?ucomisd". * g++.target/i

[PATCH, rs6000] Enable absolute jump table for PPC Linux

Hi, This patch enables absolute jump table on PPC Linux. When PIC is set, the absolute jump tables are placed in RELRO section. Otherwise, they're placed in rodata section. Bootstrapped and tested on powerpc64-linux BE and LE with no regressions. Is this okay for trunk? Any recommendations

[PATCH] RISC-V: Change default ISA version into 20191213

Bump default ISA spec to newer version 20191213, current default ISA spec is 2.2, but it's already out of date for a long time, sync with binutils ISA version, convention in toolchain use. gcc/ChangeLog: * config.gcc: Modify default isa_spec version. --- gcc/config.gcc | 8 1 f

[PATCH] libgccjit: Add option to hide stderr logs [PR104073]

Hi. This option will be useful for rustc_codegen_gcc to hide the error about unsupported 128-bit integer types. David, if you know of a better way to check if these types are supported than creating such a type and checking if it causes an error, I will not need this patch. Thanks for the reviews

Re: [PATCH] libgccjit: Add support for register variables [PR104072]

I missed the comment about the new define, so here's the updated patch. Le lundi 17 janvier 2022 à 19:24 -0500, Antoni Boucher via Jit a écrit : > Hi. > This patch add supports for register variables in libgccjit. > > It passes the JIT tests, but since I added a function in reginfo.c, I > wonder

Re: [PATCH] libgccjit: Add support for bitcasts [PR104071]

I was missing the define, so I added it. Here's the new patch with it. Le lundi 17 janvier 2022 à 17:18 -0500, Antoni Boucher via Jit a écrit : > Hi. > This patch add support for bitcasts in libgccjit. > > It passes the JIT tests, but since I added a function in tree.c, I > wonder if I should run

[PATCH] libgccjit: Add support for register variables [PR104072]

Hi. This patch add supports for register variables in libgccjit. It passes the JIT tests, but since I added a function in reginfo.c, I wonder if I should run the whole testsuite. Thanks for the review. From 328eca2be438c4a05c21942b4b2c3650ff7de0eb Mon Sep 17 00:00:00 2001 From: Antoni Boucher Da

Re: [PATCH] c++: error message for dependent template members [PR70417]

On Sat, Jan 15, 2022 at 3:28 AM Anthony Sharp wrote: > Hi Jason, > > Hope you are well. Apologies, I've not had time to sit down and look at > this since last month I quit my old job, then I had family around for the > whole of the Christmas period, and then even more recently I've had to > start

Re: [PATCH] PR fortran/103692 - [11/12 Regression] ICE in add_init_expr_to_sym, at fortran/decl.c:2062

Hi Harald, after lengthy debugging of this PR it became obvious that we killed the typespec while trying to expand an empty array constructor. Bad idea, but easy to fix. Regtested on x86_64-pc-linux-gnu. OK for mainline and 11-branch? OK. Thanks for the patch! Best regards Thomas

[PATCH] libgccjit: Add support for bitcasts [PR104071]

Hi. This patch add support for bitcasts in libgccjit. It passes the JIT tests, but since I added a function in tree.c, I wonder if I should run the whole testsuite. David, you can now disregard my question in my email about 128-bit integers regarding my issue with initialize_sizetypes being calle

[PATCH] PR fortran/103692 - [11/12 Regression] ICE in add_init_expr_to_sym, at fortran/decl.c:2062

Dear Fortranners, after lengthy debugging of this PR it became obvious that we killed the typespec while trying to expand an empty array constructor. Bad idea, but easy to fix. Regtested on x86_64-pc-linux-gnu. OK for mainline and 11-branch? Thanks, Harald From b9be44b422063c6c1f7a4bb50245ba4

Re: [ANNOUNCEMENT] Mass rename of C++ .c files to .cc suffix is going to happen on Jan 17 evening UTC TZ

On 1/13/22 12:01, Martin Liška wrote: Hello. Based on the discussion with release managers, the change is going to happen after stage4 begins. Martin Hi. The renaming patches have been just installed and I've built a few target compilers so far. I'll be online in ~10 hours from now so I can

Re: [PATCH] git-backport: support renamed .cc files in commit message.

On 1/12/22 16:54, Martin Liška wrote: There's a patch that enhances git-backport so that it updates commit messages for files which name ends now with .cc and is still .c on a branch. The patch has been installed as I've made the renaming now. Cheers, Martin

Re: [PATCH 6/6] libstdc++: Import MSVC floating-point std::from_chars testcases

On Mon, Jan 17, 2022 at 5:54 AM Jonathan Wakely wrote: > > > > On Sun, 16 Jan 2022 at 18:17, Patrick Palka via Libstdc++ > wrote: >> >> libstdc++-v3/ChangeLog: >> >> * testsuite/20_util/from_chars/double.cc: New test, consisting >> of testcases extracted from the MSVC STL testsui

Re: [PATCH] rs6000: Fix cpu selection w/ isel (PR100108)

Hi! On Mon, Jan 17, 2022 at 09:06:25PM +0100, Sebastian Huber wrote: > On 11/01/2022 09:10, Sebastian Huber wrote: > >On 20/04/2021 17:00, Segher Boessenkool wrote: > >>There are various non-IBM CPUs with isel as well, so it is easiest if we > >>just don't consider that flag here (it is not needed

Re: [PATCH] rs6000: Fix cpu selection w/ isel (PR100108)

On 11/01/2022 09:10, Sebastian Huber wrote: Hello Segher, On 20/04/2021 17:00, Segher Boessenkool wrote: There are various non-IBM CPUs with isel as well, so it is easiest if we just don't consider that flag here (it is not needed). 2021-04-20  Segher Boessenkool PR target/100108 * co

Re: [PATCH 4/6] libstdc++: Adjust fast_float's over/underflow behavior for conformnace

On Mon, Jan 17, 2022 at 5:49 AM Jonathan Wakely wrote: > > > > On Sun, 16 Jan 2022 at 18:12, Patrick Palka via Libstdc++ > wrote: >> >> This makes fast_float handle the situation where std::from_chars is >> specified to return result_out_of_range, i.e. when the parsed value >> is outside the rep

[PATCH] Make `-Werror` optional in libatomic/libbacktrace/libgomp/libitm/libsanitizer

* `-Werror` can cause issues when a more recent version of GCC compiles an older version: - https://bugs.gentoo.org/229059 - https://bugs.gentoo.org/475350 - https://bugs.gentoo.org/667104 --- libatomic/configure.ac| 6 -- libbacktrace/configure.ac | 7 -

[PATCH] tree-optimization/104038 - Limit the number of relations registered per basic block.

As mentioned in the PR, this demonstrates the potentially quadratic performance behaviour of adding transitive relations over a series of cascading calculations. As the lookup in a basic block is also linear in nature, I think for this release it makes sense to simply limit the number of relat

Re: [PATCH v3] c++: designated init of char array by string constant [PR55227]

Attached (the cut n paste looks like it removed some whitespace formatting) 0001-c-designated-init-of-char-array-by-string-constant-P.patch Description: Binary data

Re: PING^5 [PATCH v4 0/2] Implement indirect external access

Ping, could a global maintainer take a look at this? On Mon, Jan 03, 2022 at 07:32:25PM -0800, H.J. Lu via Gcc-patches wrote: > On Sat, Dec 11, 2021 at 10:44 AM H.J. Lu wrote: > > > > On Thu, Nov 25, 2021 at 9:54 AM H.J. Lu wrote: > > > > > > On Mon, Nov 1, 2021 at 7:02 AM H.J. Lu wrote: > > >

[PATCH v3] c++: designated init of char array by string constant [PR55227]

V3 addresses Jason's review point - it.undoes unnecessary variable renames (back from arr_init to str_init) Also address "FIXME: this code is duplicated from reshape_init" in cp_complete_array_type by always calling reshape_init on init-list. PR c++/55227 gcc/cp/ChangeLog: * decl.c (reshape_in

[r12-6637 Regression] FAIL: g++.target/i386/pr103973-9.C scan-assembler-times \tcomisd 2 on Linux/x86_64

On Linux/x86_64, 463d9108766dcbb6a1051985e6c840a46897fe10 is the first bad commit commit 463d9108766dcbb6a1051985e6c840a46897fe10 Author: Jakub Jelinek Date: Mon Jan 17 13:39:05 2022 +0100 widening_mul, i386: Improve spaceship expansion on x86 [PR103973] caused FAIL: gcc.target/i386/pr10

Re: PING 4 [PATCH v2 2/2] add -Wdangling-pointer [PR #63272]

On 1/17/22 06:46, Stephan Bergmann wrote: On 10/01/2022 22:51, Martin Sebor via Gcc-patches wrote: Last ping for this stage 1 feature before stage 3 ends: https://gcc.gnu.org/pipermail/gcc-patches/2021-November/585819.html This hits somewhat unexpectedly at (test case reduced from a hit in Li

Re: [PATCH] c++: ICE with noexcept and canonical types [PR101715]

On 1/14/22 19:22, Marek Polacek wrote: This is a "canonical types differ for identical types" ICE, which started with r11-4682. It's a bit tricky to explain. Consider: template struct S { S bar() noexcept(T::value); // #1 S foo() noexcept(T::value); // #2 }; template S

Re: [PATCH] Fix tree-optimization/101941: IPA splitting out function with error attribute

On Fri, Jan 14, 2022 at 09:41:35AM +0100, Jan Hubicka via Gcc-patches wrote: > > > > > > --- a/gcc/ipa-split.c > > > > > > +++ b/gcc/ipa-split.c > > > > > > @@ -873,7 +873,7 @@ visit_bb (basic_block bb, basic_block return_bb, > > > > > > gimple *stmt = gsi_stmt (bsi); > > > > > > tr

Re: Ping Re: [PATCH] middle-end: move initialization of stack_limit_rtx [PR103163]

On 1/17/22 1:29 AM, Richard Biener wrote: On Mon, Jan 17, 2022 at 4:15 AM Sandra Loosemore wrote: On 1/8/22 9:24 PM, Sandra Loosemore wrote: This patch fixes the ICE I reported in PR103163. We were initializing stack_limit_rtx before the register properties it depends on were getting set. I

Re: [PATCH] middle-end/101292 - invalid memory access with warning control

On 1/17/22 07:32, Richard Biener via Gcc-patches wrote: The warning control falls into the C++ trap of using a reference to old hashtable contents for a put operation which can end up re-allocating that before reading from the old freed referenced to source. Fixed by introducing a temporary. I

Re: [Patch][V5][Patch 2/2]Enable -Wuninitialized + -ftrivial-auto-var-init for address taken variables.

Thanks. I just committed the patch to gcc12 as: https://gcc.gnu.org/pipermail/gcc-cvs/2022-January/359400.html Qing > On Jan 17, 2022, at 5:36 AM, Richard Biener > wrote: > > On Sat, Jan 15, 2022 at 5:49 PM Qing Zhao wrote: >> >> Hi, Richard, >> >> This is the updated version for the chang

Re: [PATCH] c++: Fix cp_genericize_target_expr for TARGET_EXPRs created for global initialization [PR104031]

On 1/17/22 03:56, Jakub Jelinek wrote: Hi! The following patch is miscompiled, cp_genericize_target_expr expects that for the constant part split_nonconstant_init will emit an INIT_EXPR that will initialize it, but that doesn't happen and instead we get DECL_INITIAL on the TARGET_EXPR_SLOT that

[PATCH] Fix for GCC '-MF' option cannot deal with long paths in Windows

Hello, The '-MF' option cannot deal with path size >256 characters in Windows. This patch is to fix this long path issue with -MF option. Let me know is it ok to commit? -- Thanks, Sundeep K. c-opts.patch Description: Binary data

Re: [PATCH, OpenMP] PR103642 - Fix omp-low ICE for indirect references based off component access

Ping. On 2022/1/3 10:15 PM, Chung-Lin Tang wrote: This issue was triggered after the patch extending syntax for component access in map clauses (https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=0ab29cf0bb68960c) In gimplify_scan_omp_clauses, the case for handling indirect accesses (which creates

[PATCH] middle-end/101292 - invalid memory access with warning control

The warning control falls into the C++ trap of using a reference to old hashtable contents for a put operation which can end up re-allocating that before reading from the old freed referenced to source. Fixed by introducing a temporary. Bootstrap & regtest running on x86_64-unknown-linux-gnu. 20

[Committed] Change kind of integer literal to fix a testcase.

As Thomas reported in https://gcc.gnu.org/pipermail/gcc-patches/2022-January/588448.html a test added in my recent allocate clause patch fails on m32. It was due to default kind for integer matching c_intptr_t for m32. I have now changed it to 0_1 so that always integer with kind=1 is used. gcc/te

Re: [PATCH] disable aggressive_loop_optimizations until niter ready

Richard Biener writes: > On Fri, 14 Jan 2022, Jiufu Guo wrote: > >> Richard Biener writes: >> >> > On Thu, 13 Jan 2022, guojiufu wrote: >> > >> >> On 2022-01-03 22:30, Richard Biener wrote: >> >> > On Wed, 22 Dec 2021, Jiufu Guo wrote: >> >> > >> >> >> Hi, >> >> >> ... >> >> >> >> >> >> Boots

Re: [PATCH] [gfortran] Add support for allocate clause (OpenMP 5.0).

On 14/01/2022 12:20, Tobias Burnus wrote: > On 14.01.22 12:55, Jakub Jelinek via Fortran wrote: >> If we want to check intptr_t, we should guard the dg-error with >> "" { target { lp64 || llp64 } } >> or so. > > Well, if we want to use intptr_t, we could use be explicitly as with: > >   use iso_c

Re: PING 4 [PATCH v2 2/2] add -Wdangling-pointer [PR #63272]

On 10/01/2022 22:51, Martin Sebor via Gcc-patches wrote: Last ping for this stage 1 feature before stage 3 ends: https://gcc.gnu.org/pipermail/gcc-patches/2021-November/585819.html This hits somewhat unexpectedly at (test case reduced from a hit in LibreOffice) $ cat test.cc #include struc

Re: [PATCH] widening_mul, i386, v2: Improve spaceship expansion on x86 [PR103973]

On Mon, Jan 17, 2022 at 01:04:40PM +0100, Richard Biener wrote: > > I guess it depends, for code that can only be called during the expand pass > > dropping it should be just fine, for code that can be called also (or only) > > later I think adding JUMP_LABEL and correct LABEL_NUSES is needed becau

[PATCH][www][pushed] Clarify GCC versioning, esp. the DEV-PHASE.

--- htdocs/develop.html | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/htdocs/develop.html b/htdocs/develop.html index 263cbc79..1ac48b09 100644 --- a/htdocs/develop.html +++ b/htdocs/develop.html @@ -266,8 +266,10 @@ way and on the following timeline: VersionDEV

[committed] libstdc++: Define header for C++23

Tested x86_64-linux, pushed to trunk. Add the header and a new libstdc++_libbacktrace.a library that provides the implementation. For now, the new library is only built if --enable-libstdcxx-backtrace=yes is used. As with the Filesystem TS, the new library is only provided as a static archive.

GCC 12.0.1 Status Report (2022-01-17), Stage 4 starts now

Status == The GCC master branch is now in regression and documentation fixing mode (Stage 4) in preparation for the release of GCC 13. Re-opening of general development will happen once we reach zero P1 regressions which is when we branch for the release. Time wise history projects that to

[committed] libstdc++: Document final option names for enabling C++20

Pushed to trunk. libstdc++-v3/ChangeLog: * doc/xml/manual/status_cxx2020.xml: Use final C++20 option names. * doc/html/manual/status.html: Regenerate. --- libstdc++-v3/doc/html/manual/status.html | 4 ++-- libstdc++-v3/doc/xml/manual/status_cxx2020.xml | 4 ++-- 2

[committed] libstdc++: Rename non-reserved macros in config header [PR103650]

Tested x86_64-linux, pushed to trunk. libstdc++-v3/ChangeLog: PR libstdc++/103650 * include/Makefile.am: Rename LT_OBJDIR and STDC_HEADERS. * include/Makefile.in: Regenerate. * testsuite/17_intro/headers/c++1998/103650.cc: New test. --- libstdc++-v3/include/Makef

Re: [PATCH] widening_mul, i386, v2: Improve spaceship expansion on x86 [PR103973]

On Sat, 15 Jan 2022, Jakub Jelinek wrote: > On Sat, Jan 15, 2022 at 11:42:55AM +0100, Uros Bizjak wrote: > > Yes, that would be nice. XFmode is used for long double, and not obsolete. > > Ok, that seems to work. Compared to the incremental patch I've posted, I > also had to add handling of the c

[Patch, fortran] PR64290 - [F03] No finalization at deallocation of LHS

Hi All, Strictly speaking, the attached patch is branching out into a more generalised attack on PR37336(Finalization) - [F03] Finish derived-type finalization but most of it fixes PR64290. I started work on this patch almost a year ago but had to drop it due daytime work pressure and only picked

Re: [Patch][V5][Patch 2/2]Enable -Wuninitialized + -ftrivial-auto-var-init for address taken variables.

On Sat, Jan 15, 2022 at 5:49 PM Qing Zhao wrote: > > Hi, Richard, > > This is the updated version for the change of "Enable -Wuninitialized + > -ftrivial-auto-var-init for address taken variables”. > > Compared to the previous patch, I mainly made the following change: > > Delete the 4th paramet

[PATCH][pushed] Include tests that are not executed

The following tests are not executed because they have a bad filename extension. Fixed and pushed to master. MartinFrom 803813918d6e6e02d4ebae6cb72cd8bb69c6133a Mon Sep 17 00:00:00 2001 From: Martin Liska Date: Fri, 14 Jan 2022 13:52:50 +0100 Subject: [PATCH 2/2] Make the tests working. --- g

[PATCH] vect.exp: Rename .cc files in the folder to .C.

Hi. I would like to unify filenames in testsuite and one of the biggest offenders are vectorizer tests under g++.dg. Patch can bootstrap on x86_64-linux-gnu and survives regression tests. Ready to be installed? Thanks, Martin gcc/testsuite/ChangeLog: * g++.dg/vect/param-max-aliased-pr

Re: [PATCH 6/6] libstdc++: Import MSVC floating-point std::from_chars testcases

On Sun, 16 Jan 2022 at 18:17, Patrick Palka via Libstdc++ < libstd...@gcc.gnu.org> wrote: > libstdc++-v3/ChangeLog: > > * testsuite/20_util/from_chars/double.cc: New test, consisting > of testcases extracted from the MSVC STL testsuite. > * testsuite/20_util/from_chars/floa

[pushed 4/3] Fortran: Ignore KIND argument of a few more intrinsics. [PR103789]

I managed to break a working patch by splitting it. Now fixed. From d7a44809924297a2ff26b6b1d040c72c22f07346 Mon Sep 17 00:00:00 2001 From: Mikael Morin Date: Mon, 17 Jan 2022 11:45:46 +0100 Subject: [PATCH] Fortran: Ignore KIND argument of a few more intrinsics. [PR103789] After PR97896 for wh

Re: [PATCH 5/6] libstdc++: Use fast_float in std::from_chars for binary32/64

On Sun, 16 Jan 2022 at 18:09, Patrick Palka via Libstdc++ < libstd...@gcc.gnu.org> wrote: > This makes our std::from_chars implementation use fast_float for parsing > chars_format::scientific/fixed/general parsing into binary32/64 values. > For other floating-point formats we still use the fallbac

Re: [PATCH 4/6] libstdc++: Adjust fast_float's over/underflow behavior for conformnace

On Sun, 16 Jan 2022 at 18:12, Patrick Palka via Libstdc++ < libstd...@gcc.gnu.org> wrote: > This makes fast_float handle the situation where std::from_chars is > specified to return result_out_of_range, i.e. when the parsed value > is outside the representable range of the floating-point type. > >

Re: [PATCH 3/6] libstdc++: Apply modifications to our local copy of fast_float

On Sun, 16 Jan 2022 at 18:07, Patrick Palka via Libstdc++ < libstd...@gcc.gnu.org> wrote: > This performs the following modifications to our local copy of fast_float > in order to make it more readily usable in our std::from_chars > implementation: > > * Remove system #includes > * Replace str

Re: [PATCH 2/6] libstdc++: Import the fast_float library

On Sun, 16 Jan 2022 at 18:13, Patrick Palka via Libstdc++ < libstd...@gcc.gnu.org> wrote: > We're going to use the fast_float library in our (compiled-in) > floating-point std::from_chars implementation for faster and more > portable parsing of binary32/64 decimal strings. > > The single file fast

Re: [PATCH 1/6 v2] libstdc++: Directly implement hexfloat std::from_chars for binary32/64

On Sun, 16 Jan 2022 at 18:07, Patrick Palka via Libstdc++ < libstd...@gcc.gnu.org> wrote: > Series tested on x86_64, i686, ppc64, ppc64le, aarch64, does it look OK for > trunk? > OK, thanks. > libstdc++-v3/ChangeLog: > > * src/c++17/floating_from_chars.cc: Include . > (ascii_to_

[PATCH][pushed] Add check_effective_target_pytest3.

Hi. The patch is about factoring out a function similar to check_effective_target_python3. Cheers, Martin gcc/testsuite/ChangeLog: * lib/gcov.exp: Use check_effective_target_pytest3. * lib/target-supports.exp: Add check_effective_target_pytest3. --- gcc/testsuite/lib/gcov.exp

Re: [PATCH] libstdc++: Don't fail if math_errhandling is not defined

On Mon, 17 Jan 2022 at 10:22, Matthias Kretz wrote: > Tested on x86_64-linux and powerpc64le-linux. This fixes the > powerpc64le-linux > failure Jonathan reported. OK for trunk? > OK, thanks. > > Older glibc does not define math_errhandling with -ffast-math, in which > case floating-point exc

Re: [PATCH] Start using check-MAINTAINERS.py instead of legacy maintainers-verify.sh.

On 1/14/22 10:28, Martin Liška wrote: Ready to be installed? There's no reply, I'm going to push it. The current script is broken anyway. Cheers, Martin

[PATCH] libstdc++: Don't fail if math_errhandling is not defined

Tested on x86_64-linux and powerpc64le-linux. This fixes the powerpc64le-linux failure Jonathan reported. OK for trunk? Older glibc does not define math_errhandling with -ffast-math, in which case floating-point exceptions are not used. Signed-off-by: Matthias Kretz libstdc++-v3/ChangeLog:

Re: [r12-6585 Regression] FAIL: c-c++-common/Walloca-larger-than.c -Wc++-compat (test for excess errors) on Linux/x86_64

On 1/15/22 14:15, sunil.k.pandey wrote: On Linux/x86_64, d8b64476138671f3d89cd66f224a9b59e465631b is the first bad commit commit d8b64476138671f3d89cd66f224a9b59e465631b Author: Martin Liska Date: Fri Jan 14 15:04:33 2022 +0100 testsuite: rename files in c-c++-common. caused FAIL: c-c

[PATCH][pushed] Fix test warnings.

PR testsuite/104035 gcc/testsuite/ChangeLog: * g++.dg/torture/pr57993-2.C: Fix warnings. --- gcc/testsuite/g++.dg/torture/pr57993-2.C | 22 -- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/gcc/testsuite/g++.dg/torture/pr57993-2.C b/gcc/test

[PATCH][pushed] Fix test warnings.

PR testsuite/104035 gcc/testsuite/ChangeLog: * g++.dg/torture/pr57993-2.C: Fix warnings. --- gcc/testsuite/g++.dg/torture/pr57993-2.C | 22 -- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/gcc/testsuite/g++.dg/torture/pr57993-2.C b/gcc/test

Re: [PATCH] libstdc++: Implement C++20 atomic and atomic

On Mon, 17 Jan 2022 at 09:39, Stephan Bergmann wrote: > On 1/17/22 01:12, Jonathan Wakely via Libstdc++ wrote: > > Here's the finished version of that patch, which is all inline in the > > header, and performs faster too. > > > > Tested powerpc64le-linux and x86_64-linux. > > Pushed to trunk. > >

Re: [PATCH] libstdc++: Implement C++20 atomic and atomic

On 1/17/22 01:12, Jonathan Wakely via Libstdc++ wrote: Here's the finished version of that patch, which is all inline in the header, and performs faster too. Tested powerpc64le-linux and x86_64-linux. Pushed to trunk. FYI, recent Clang still requires typename in two places to compile with -s

[PATCH] c++: Fix cp_genericize_target_expr for TARGET_EXPRs created for global initialization [PR104031]

Hi! The following patch is miscompiled, cp_genericize_target_expr expects that for the constant part split_nonconstant_init will emit an INIT_EXPR that will initialize it, but that doesn't happen and instead we get DECL_INITIAL on the TARGET_EXPR_SLOT that isn't initialized anywhere in the IL. Th

Re: Ping Re: [PATCH] middle-end: move initialization of stack_limit_rtx [PR103163]

On Mon, Jan 17, 2022 at 4:15 AM Sandra Loosemore wrote: > > On 1/8/22 9:24 PM, Sandra Loosemore wrote: > > This patch fixes the ICE I reported in PR103163. We were initializing > > stack_limit_rtx before the register properties it depends on were > > getting set. I moved it to the same function

Re: [PATCH 3/3] tree-cfg: check placement of returns_twice calls

On Fri, Jan 14, 2022 at 7:21 PM Alexander Monakov wrote: > > When a returns_twice call has an associated abnormal edge, the edge > corresponds to the "second return" from the call. It wouldn't make sense > if any executable statements appeared between the call and the > destination of the edge (th

Re: [PATCH 2/3] tree-cfg: do not duplicate returns_twice calls

On Fri, Jan 14, 2022 at 7:21 PM Alexander Monakov wrote: > > A returns_twice call may have associated abnormal edges that correspond > to the "second return" from the call. If the call is duplicated, the > copies of those edges also need to be abnormal, but e.g. tracer does not > enforce that. Jus

Extend test cases for references in OpenACC 'private' clauses (was: Test cases for references in OpenACC 'private' clauses)

Hi! On 2022-01-17T09:01:54+0100, I wrote: > I've now pushed to master branch in > commit fbb438808e9b53a6e6b179a5787d609443acaad6 > "Test cases for references in OpenACC 'private' clauses", see attached. ... extended by commit b75aab194e3fe40b594d9a70eb7068dc9950bcf0 "Extend test cases for refere

Test cases for references in OpenACC 'private' clauses

Hi! On 2019-09-20T14:17:33-0700, Julian Brown wrote: > This patch ['Handle references in OpenACC "private" clauses'] [...] ..., and its prerequisite changes, in particular... > [...] is intended as a somewhat temporary solution: it works for the > newly-included tests, but is not very elegant.