Sυbmіtting Μanuѕcripts to a Multidisciplinary Scientific Јournаl

If you no longer wish to receive ҽmαils from us, please ᴄlіᴄk here to unѕubѕсribe. Рαper Invіtatіon Main Reasons for Рαper Publіcatіоn with the Јournаl 1. Fast Schedule Overview: 1. Sυbmіt a ραρer 2. Pre-rеᴠiеwed result sent within 1-2 weekdays 3.

[Bug target/81357] Extra mov for zero extend of add

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81357 Andrew Pinski changed: What|Removed |Added Status|ASSIGNED|NEW Severity|normal

[PATCHv2] [aarch64] Fix target/95969: __builtin_aarch64_im_lane_boundsi interferes with gimple

From: Andrew Pinski This patch adds simple folding of __builtin_aarch64_im_lane_boundsi where we are not going to error out. It fixes the problem by the removal of the function from the IR. OK? Bootstrapped and tested on aarch64-linux-gnu with no regressions. gcc/ChangeLog: PR

[Bug target/82139] unnecessary movapd with _mm_castsi128_pd to use BLENDPD on __m128i results

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82139 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2021-09-04 Keywords|

[Bug target/81085] inefficient union with long double argument on 32-bit x86

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81085 Andrew Pinski changed: What|Removed |Added Severity|normal |enhancement Blocks|

[Bug middle-end/57485] memcpy in aggregate return not eliminated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57485 Andrew Pinski changed: What|Removed |Added Last reconfirmed|2017-06-01 00:00:00 |2021-9-3 Severity|normal

[Bug middle-end/102162] Byte-wise access optimized away at -O1 and above

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102162 --- Comment #32 from deller at gmx dot de --- Fixed in Linux kernel by declaring the extern int32 as char: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c42813b71a06a2ff4a155aa87ac609feeab76cf3

Re: [PATCH] [aarch64] Fix target/95969: __builtin_aarch64_im_lane_boundsi interferes with gimple

On Fri, Sep 3, 2021 at 2:42 AM Richard Sandiford via Gcc-patches wrote: > > apinski--- via Gcc-patches writes: > > From: Andrew Pinski > > > > This patch adds simple folding of __builtin_aarch64_im_lane_boundsi where > > we are not going to error out. It fixes the problem by the removal > > of

gcc-10-20210903 is now available

Snapshot gcc-10-20210903 is now available on https://gcc.gnu.org/pub/gcc/snapshots/10-20210903/ 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 tree-optimization/102196] -Wmaybe-uninitialized: Maybe generate helpful hints?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102196 Martin Sebor changed: What|Removed |Added Status|WAITING |NEW Blocks|

[Bug c++/102198] New: Unused and nonsensical template instantiations used for return type inference end up in the output

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102198 Bug ID: 102198 Summary: Unused and nonsensical template instantiations used for return type inference end up in the output Product: gcc Version: unknown Status:

Re: Ping ^ 2: [PATCH] rs6000: Expand fmod and remainder when built with fast-math [PR97142]

Hi! On Fri, Sep 03, 2021 at 10:31:24AM +0800, Xionghu Luo wrote: > fmod/fmodf and remainder/remainderf could be expanded instead of library > call when fast-math build, which is much faster. Thank you very much for this patch. Some trivial comments if you haven't commmitted it yet: >

[Bug tree-optimization/102196] -Wmaybe-uninitialized: Maybe generate helpful hints?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102196 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org ---

[Bug target/102107] protocol register (r12) corrupted before a tail call

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102107 --- Comment #16 from Segher Boessenkool --- (Hopefully) fixed on trunk, but it needs backports.

[PATCH] rs6000: Don't use r12 for CR save on ELFv2 (PR102107)

CR is saved and/or restored on some paths where GPR12 is already live since it has a meaning in the calling convention in the ELFv2 ABI. It is not completely clear to me that we can always use r11 here, but it does seem save, there is checking code (to detect conflicts here), and it is stage 1.

[Bug target/102107] protocol register (r12) corrupted before a tail call

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102107 --- Comment #15 from CVS Commits --- The master branch has been updated by Segher Boessenkool : https://gcc.gnu.org/g:2484f7a4b0f52e6ed04754be336f1fa6fde47f6b commit r12-3353-g2484f7a4b0f52e6ed04754be336f1fa6fde47f6b Author: Segher

[Bug tree-optimization/102196] -Wmaybe-uninitialized: Maybe generate helpful hints?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102196 --- Comment #3 from Andrew Pinski --- tc-microblaze.c case: if (exp.X_op != O_constant) as_warn (_("Symbol used as immediate for shift instruction")); else { output = frag_more (isize); immed =

[Bug c++/99215] coroutines: debugging with gdb

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215 --- Comment #12 from Iain Sandoe --- also : https://gcc.gnu.org/pipermail/gcc-cvs/2021-September/352947.html https://gcc.gnu.org/pipermail/gcc-cvs/2021-September/352948.html https://gcc.gnu.org/pipermail/gcc-cvs/2021-September/352949.html

[Bug tree-optimization/102196] -Wmaybe-uninitialized: Maybe generate helpful hints?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102196 --- Comment #2 from Jan-Benedict Glaw --- Declaration and possibly uninitialized usage are shown. Ie for said Binutils, I get these messages: microblaze-{elf,linux} [all 2021-09-03 18:17:30] depbase=`echo

[Bug tree-optimization/102188] Over widening detection doesn't work when no range information

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102188 Andrew Pinski changed: What|Removed |Added Severity|normal |enhancement Ever confirmed|0

[Bug target/101933] Unloaded dll with global std::mutex causes exe to crash on exit #38

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101933 --- Comment #3 from Paul Jackson --- Maybe I'm missing something, but even this dll crashes for me now. So it seems like it has nothing to do with global variables or static storage. That sucks, it means that I just can't use C++ in dlls. Or is

[Bug target/102197] New: ABI to pass and return 32-bit FP vectors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102197 Bug ID: 102197 Summary: ABI to pass and return 32-bit FP vectors Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target

[Bug tree-optimization/102196] -Wmaybe-uninitialized: Maybe generate helpful hints?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102196 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Component|middle-end

[Bug target/101933] Unloaded dll with global std::mutex causes exe to crash on exit #38

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101933 --- Comment #2 from Paul Jackson --- I tried to work around the problem, and it's even worse than I expected. You can replace dll.cc with the following and observe the same crash. That means that even if I want to do manual memory management

[Bug driver/102193] DLL linking with a external referenced DLL

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102193 --- Comment #2 from Ricardo Santos Pereira --- thanks BW Em sex., 3 de set. de 2021 às 16:02, pinskia at gcc dot gnu.org < gcc-bugzi...@gcc.gnu.org> escreveu: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102193 > > Andrew Pinski changed:

[Bug debug/102195] Missing DW_TAG_typedef when using qualified variable of typedef'd array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102195 --- Comment #2 from Indu Bhagat --- (In reply to Andrew Pinski from comment #1) > I think this is a dup of bug 8354. Possible. It looks like two distinct symptoms, but seem to be originating from the same underlying issue. I don't have enough

[Bug middle-end/102196] New: -Wmaybe-uninitialized: Maybe generate helpful hints?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102196 Bug ID: 102196 Summary: -Wmaybe-uninitialized: Maybe generate helpful hints? Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug fortran/101349] ICE in gfc_get_descriptor_field, at fortran/trans-array.c:140

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101349 --- Comment #6 from CVS Commits --- The releases/gcc-11 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:f826c257b6fb64868fd12a52291d1b6f85e1689a commit r11-8958-gf826c257b6fb64868fd12a52291d1b6f85e1689a Author: Harald Anlauf

Re: [PATCH 1/13] v2 [PATCH 1/13] Add support for per-location warning groups (PR 74765)

Hi! Martin, thanks for your review. Now need someone to formally approve the third patch. On 2021-09-01T18:14:46-0600, Martin Sebor wrote: > On 9/1/21 1:35 PM, Thomas Schwinge wrote: >> On 2021-06-23T13:47:08-0600, Martin Sebor via Gcc-patches >> wrote: >>> On 6/22/21 5:28 PM, David Malcolm

[Bug fortran/102113] parsing error in assigned goto

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102113 --- Comment #6 from CVS Commits --- The releases/gcc-11 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:95553bfcc3a69afc2a2bc02aeafac6e92d3dea1e commit r11-8957-g95553bfcc3a69afc2a2bc02aeafac6e92d3dea1e Author: Harald Anlauf

[Bug driver/102189] error: unrecognized command-line option '-fno-[...]'; did you mean '-ftree-[...]'?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102189 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Keywords|

[Bug debug/102195] Missing DW_TAG_typedef when using qualified variable of typedef'd array

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

Re: [r12-3321 Regression] FAIL: gfortran.dg/PR100914.f90 -Os (test for excess errors) on Linux/x86_64

On Fri, Sep 3, 2021 at 10:25 AM Sandra Loosemore wrote: > > On 9/2/21 11:37 PM, Sandra Loosemore wrote: > > On 9/2/21 10:18 PM, sunil.k.pandey wrote: > >> On Linux/x86_64, > >> > >> 93b6b2f614eb692d1d8126ec6cb946984a9d01d7 is the first bad commit > >> commit

[Bug debug/102195] New: Missing DW_TAG_typedef when using qualified variable of typedef'd array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102195 Bug ID: 102195 Summary: Missing DW_TAG_typedef when using qualified variable of typedef'd array Product: gcc Version: 12.0 Status: UNCONFIRMED Severity:

[Bug driver/102193] DLL linking with a external referenced DLL

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102193 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2021-09-03 Ever confirmed|0

[Bug c++/64867] split warning for passing non-POD to varargs function from -Wconditionally-supported into new warning flag, -Wnon-pod-varargs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64867 David Binderman changed: What|Removed |Added CC||dcb314 at hotmail dot com --- Comment

Re: [committed] analyzer: support "bifurcation"; reimplement realloc [PR99260]

On Mon, 30 Aug 2021, David Malcolm via Gcc-patches wrote: > gcc/analyzer/ChangeLog: > PR analyzer/99260 > * analyzer.h (class custom_edge_info): New class, adapted from > exploded_edge::custom_info_t. Make member functions const. > Make update_model return bool, converting

[Bug c++/102194] New: Incorrect explicit instantiation of constexpr variable accepted

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102194 Bug ID: 102194 Summary: Incorrect explicit instantiation of constexpr variable accepted Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal

Re: [r12-3321 Regression] FAIL: gfortran.dg/PR100914.f90 -Os (test for excess errors) on Linux/x86_64

On 9/2/21 11:37 PM, Sandra Loosemore wrote: On 9/2/21 10:18 PM, sunil.k.pandey wrote: On Linux/x86_64, 93b6b2f614eb692d1d8126ec6cb946984a9d01d7 is the first bad commit commit 93b6b2f614eb692d1d8126ec6cb946984a9d01d7 Author: Sandra Loosemore Date:   Wed Aug 18 07:22:03 2021 -0700

Re: [PATCH v3, Fortran] TS 29113 testsuite

On 9/3/21 3:14 AM, Tobias Burnus wrote: If I read https://gcc.gnu.org/onlinedocs/gcc/Floating-Types.html correctly, we should use _Float128 for the following errors "The _Float128 type is supported on all systems where __float128 is supported or where long double has the IEEE binary128

[Bug target/94630] General bug for changes needed to switch the powerpc64le-linux long double default

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94630 --- Comment #10 from CVS Commits --- The releases/gcc-11 branch has been updated by Michael Meissner : https://gcc.gnu.org/g:d9f215aa59cca00c862a14d3ee90e0b0ee4ed56f commit r11-8954-gd9f215aa59cca00c862a14d3ee90e0b0ee4ed56f Author: Michael

[Bug libstdc++/101960] std::tuple with an array element is rejected as a named return type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101960 康桓瑋 changed: What|Removed |Added CC||hewillk at gmail dot com --- Comment #5 from 康桓瑋

[Bug target/102173] [12 Regression] ICEs gcc.target/aarch64/sve/acle/general-c/type_redef_1.c after recent error recovery patch

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102173 Andrew Pinski changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

Re: [PATCH] Implement POINTER_DIFF_EXPR entry in range-op.

Patches welcome :-). On Fri, Sep 3, 2021, 18:42 Martin Sebor wrote: > On 9/3/21 8:41 AM, Aldy Hernandez via Gcc-patches wrote: > > [Andrew, do you see any problem with using the minus relational code > > here? It seems like everything matches up.] > > > > I've seen cases in the upcoming jump

[Bug c/102193] New: DLL linking with a external referenced DLL

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102193 Bug ID: 102193 Summary: DLL linking with a external referenced DLL Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

Re: [PATCH] Implement POINTER_DIFF_EXPR entry in range-op.

On 9/3/21 8:41 AM, Aldy Hernandez via Gcc-patches wrote: [Andrew, do you see any problem with using the minus relational code here? It seems like everything matches up.] I've seen cases in the upcoming jump threader enhancements where we see a difference of two pointers that are known to be

Re: [PATCH] Implement POINTER_DIFF_EXPR entry in range-op.

On 9/3/21 5:41 PM, Jakub Jelinek wrote: On Fri, Sep 03, 2021 at 09:09:59AM -0600, Jeff Law via Gcc-patches wrote: On 9/3/2021 9:05 AM, Andrew MacLeod via Gcc-patches wrote: On 9/3/21 10:41 AM, Aldy Hernandez wrote: [Andrew, do you see any problem with using the minus relational code

Re: [Committed] [PATCH 2/4] (v4) On-demand locations within string-literals

Hi! On 2021-09-02T21:09:54+0200, I wrote: > On 2021-09-02T15:59:14+0200, I wrote: >> On 2016-08-05T14:16:58-0400, David Malcolm wrote: >>> Committed to trunk as r239175; I'm attaching the final version of the >>> patch for reference. >> >> David, you've added here 'gcc/input.h:struct

[Bug debug/101947] [12 Regression] Broken LTO bootstrap in get_base_type_offset, at dwarf2out.c:4330

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101947 --- Comment #7 from Eric Botcazou --- It's the DW_AT_byte_size expression in: (gdb) p debug_dwarf_die (die) DIE 1041: DW_TAG_structure_type (0x739f06e0) abbrev id: 51 offset: 1041 mark: 1 DW_AT_name: "exp_dist__rpc_target"

Re: [PATCH v3] rs6000: Add load density heuristic

Hi Kewen, Sorry that we lost track of this patch!  The heuristic approach looks good.  It is limited in scope and won't kick in often, and the case you're trying to account for is important. At the time you submitted this, I think reliable P10 testing wasn't possible.  Now that it is, could

Re: [PATCH] Implement POINTER_DIFF_EXPR entry in range-op.

On Fri, Sep 03, 2021 at 09:09:59AM -0600, Jeff Law via Gcc-patches wrote: > > > On 9/3/2021 9:05 AM, Andrew MacLeod via Gcc-patches wrote: > > On 9/3/21 10:41 AM, Aldy Hernandez wrote: > > > [Andrew, do you see any problem with using the minus relational code > > > here?  It seems like

Re: [PATCH] Implement POINTER_DIFF_EXPR entry in range-op.

On 9/3/21 5:05 PM, Andrew MacLeod wrote: On 9/3/21 10:41 AM, Aldy Hernandez wrote: [Andrew, do you see any problem with using the minus relational code here?  It seems like everything matches up.] I've seen cases in the upcoming jump threader enhancements where we see a difference of two

Re: [PATCH] c++: shortcut bad convs during overload resolution [PR101904]

On Thu, 2 Sep 2021, Jason Merrill wrote: > On 8/31/21 3:15 PM, Patrick Palka wrote: > > On Mon, 30 Aug 2021, Patrick Palka wrote: > > > > > In the context of overload resolution we have the notion of a "bad" > > > argument conversion, which is a conversion that "would be a permitted > > > with a

[Bug c++/101904] Wrong result of decltype during instantiation of std::result_of

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101904 --- Comment #6 from CVS Commits --- The master branch has been updated by Patrick Palka : https://gcc.gnu.org/g:47543e5f9d1fc502be79f91c87cbeb6eda17e641 commit r12-3346-g47543e5f9d1fc502be79f91c87cbeb6eda17e641 Author: Patrick Palka Date:

Re: [PATCH V3 0/6] Initial support for AVX512FP16

> On 3 Sep 2021, at 08:51, Iain Sandoe wrote: > > >> On 2 Sep 2021, at 21:03, Joseph Myers wrote: >> >> On Thu, 2 Sep 2021, Iain Sandoe via Gcc-patches wrote: >> >>> diff --git a/libgcc/soft-fp/eqdf2.c b/libgcc/soft-fp/eqdf2.c >>> index 2a44ee377ce..a3bb664f5f1 100644 >>> ---

Re: [PATCH] Do not assume loop header threading in backward threader.

On 9/3/21 5:04 PM, Jeff Law wrote: On 9/3/2021 7:57 AM, Aldy Hernandez wrote: The registry's thread_through_all_blocks() has a may_peel_loop_headers argument.  When refactoring the backward threader code, I removed this argument for the local passthru method because it was always TRUE. 

[pushed] c++: Avoid bogus -Wunused with recent change

My change to make limit_bad_template_recursion avoid instantiating members of erroneous classes produced a bogus "used but not defined" warning for 23_containers/unordered_set/instantiation_neg.cc; it's not defined because we decided not to instantiate it. So we need to suppress that warning.

Re: [PATCH] Implement POINTER_DIFF_EXPR entry in range-op.

On 9/3/2021 9:05 AM, Andrew MacLeod via Gcc-patches wrote: On 9/3/21 10:41 AM, Aldy Hernandez wrote: [Andrew, do you see any problem with using the minus relational code here?  It seems like everything matches up.] I've seen cases in the upcoming jump threader enhancements where we see a

Re: [PATCH 2/2] Get rid of all float-int special cases in validate_subreg.

On Sep 02 2021, Segher Boessenkool wrote: > On Tue, Aug 31, 2021 at 07:17:49PM +0800, liuhongt via Gcc-patches wrote: >> * emit-rtl.c (validate_subreg): Get rid of all float-int >> special cases. > > This caused various regressions on powerpc. Please revert this until > this can be

Re: [PATCH] Implement POINTER_DIFF_EXPR entry in range-op.

On 9/3/21 10:41 AM, Aldy Hernandez wrote: [Andrew, do you see any problem with using the minus relational code here? It seems like everything matches up.] I've seen cases in the upcoming jump threader enhancements where we see a difference of two pointers that are known to be equivalent, and

Re: [PATCH] Do not assume loop header threading in backward threader.

On 9/3/2021 7:57 AM, Aldy Hernandez wrote: The registry's thread_through_all_blocks() has a may_peel_loop_headers argument. When refactoring the backward threader code, I removed this argument for the local passthru method because it was always TRUE. This may not necessarily be true in the

Re: [PATCH] Abstract PHI and forwarder block checks in jump threader.

On 9/3/2021 7:56 AM, Aldy Hernandez wrote: This patch abstracts out a couple common idioms in the forward threader that I found useful while navigating the code base. Tested on x86-64 Linux. OK? gcc/ChangeLog: * tree-ssa-threadedge.c (has_phis_p): New. (forwarder_block_p):

Re: [PATCH] Improve backwards threader debugging dumps.

On 9/3/2021 7:56 AM, Aldy Hernandez wrote: This patch adds debugging helpers to the backwards threader. I have also noticed that profitable_path_p() can bail early on paths that crosses loops and leave the dump of blocks incomplete. Fixed as well. Unfortunately the new methods cannot be

[Bug tree-optimization/102192] New: Curious '-O2'-only '-Wmaybe-uninitialized' diagnostics for 'libgomp.oacc-fortran/routine-10.f90'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102192 Bug ID: 102192 Summary: Curious '-O2'-only '-Wmaybe-uninitialized' diagnostics for 'libgomp.oacc-fortran/routine-10.f90' Product: gcc Version: 12.0 Status: UNCONFIRMED

[Bug c++/102191] New: Can't return prvalue with potentially-throwing destructor during constant evaluation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102191 Bug ID: 102191 Summary: Can't return prvalue with potentially-throwing destructor during constant evaluation Product: gcc Version: 12.0 Status: UNCONFIRMED

Re: [PATCH] Dump reason why threads are being cancelled and abstract code.

On 9/3/2021 7:55 AM, Aldy Hernandez wrote: We are inconsistent on dumping out reasons why a thread was canceled. This makes debugging jump threading problems harder because paths can be canceled with no reason given. This patch abstracts out the thread canceling code and adds a reason for

[Bug middle-end/101157] [12 regression] ICE compiling gcc.target/powerpc/stack-limit.c after r12-1702

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101157 Peter Bergner changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

Re: Ping ^ 2: [PATCH] rs6000: Expand fmod and remainder when built with fast-math [PR97142]

On Thu, Sep 2, 2021 at 10:31 PM Xionghu Luo wrote: > > Resend the patch that addressed Will's comments. > > > fmod/fmodf and remainder/remainderf could be expanded instead of library > call when fast-math build, which is much faster. > > fmodf: > fdivs f0,f1,f2 > frizf0,f0 >

[Bug fortran/102190] New: Syntax error reported in associate construct

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102190 Bug ID: 102190 Summary: Syntax error reported in associate construct Product: gcc Version: 11.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

Re: Ping ^ 2: [PATCH] rs6000: Expand fmod and remainder when built with fast-math [PR97142]

Hi Xionghu, This looks okay to me.  Recommend maintainers approve. Thanks! Bill On 9/2/21 9:31 PM, Xionghu Luo wrote: Resend the patch that addressed Will's comments. fmod/fmodf and remainder/remainderf could be expanded instead of library call when fast-math build, which is much faster.

Re: [patch][version 8]add -ftrivial-auto-var-init and variable attribute "uninitialized" to gcc

Ping. Qing > On Aug 21, 2021, at 3:07 PM, Qing Zhao via Gcc-patches > wrote: > > Hi, > > This is the 8th version of the patch for the new security feature for GCC. > I have tested it with bootstrap on both x86 and aarch64, regression testing > on both x86 and aarch64. > Also tested it with

[PATCH] Implement POINTER_DIFF_EXPR entry in range-op.

[Andrew, do you see any problem with using the minus relational code here? It seems like everything matches up.] I've seen cases in the upcoming jump threader enhancements where we see a difference of two pointers that are known to be equivalent, and yet we fail to return 0 for the range. This

[PATCH] Abstract PHI and forwarder block checks in jump threader.

This patch abstracts out a couple common idioms in the forward threader that I found useful while navigating the code base. Tested on x86-64 Linux. OK? gcc/ChangeLog: * tree-ssa-threadedge.c (has_phis_p): New. (forwarder_block_p): New. (potentially_threadable_block):

[Bug driver/102189] New: error: unrecognized command-line option '-fno-[...]'; did you mean '-ftree-[...]'?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102189 Bug ID: 102189 Summary: error: unrecognized command-line option '-fno-[...]'; did you mean '-ftree-[...]'? Product: gcc Version: 12.0 Status: UNCONFIRMED

Re: [PATCH 8/8] coroutines: Make the continue handle visible to debug.

On 9/1/21 6:56 AM, Iain Sandoe wrote: When we have a suspend method that returns a coroutine handle we transfer (hopefully symmetrically, i.e. with a tailcall) to that new coroutine instead of returning to our resumer. This adds the variable to the outer block for the actor function which

Re: [PATCH 7/8] coroutines: Make proxy vars for the function arg copies.

> On 3 Sep 2021, at 15:07, Jason Merrill via Gcc-patches > wrote: > > On 9/1/21 6:56 AM, Iain Sandoe wrote: >> This adds top level proxy variables for the coroutine frame >> copies of the original function args. These are then available >> in the debugger to refer to the frame copies. We

Re: [PATCH 6/8] coroutines: Convert implementation variables to debug-friendly form.

> On 3 Sep 2021, at 15:12, Jason Merrill wrote: > > On 9/3/21 9:56 AM, Iain Sandoe wrote: >>> On 3 Sep 2021, at 14:52, Jason Merrill wrote: >>> >>> On 9/1/21 6:55 AM, Iain Sandoe wrote: The user might well wish to inspect some of the state that represents the implementation of the

Re: [PATCH 6/8] coroutines: Convert implementation variables to debug-friendly form.

On 9/3/21 9:56 AM, Iain Sandoe wrote: On 3 Sep 2021, at 14:52, Jason Merrill wrote: On 9/1/21 6:55 AM, Iain Sandoe wrote: The user might well wish to inspect some of the state that represents the implementation of the coroutine machine. In particular: The promise object. The function

Re: [PATCH 7/8] coroutines: Make proxy vars for the function arg copies.

On 9/1/21 6:56 AM, Iain Sandoe wrote: This adds top level proxy variables for the coroutine frame copies of the original function args. These are then available in the debugger to refer to the frame copies. We rewrite the function body to use the copies, since the original parms will no

[PATCH] Abstract PHI and forwarder block checks in jump threader.

This patch abstracts out a couple common idioms in the forward threader that I found useful while navigating the code base. Tested on x86-64 Linux. OK? gcc/ChangeLog: * tree-ssa-threadedge.c (has_phis_p): New. (forwarder_block_p): New. (potentially_threadable_block):

[PATCH] Do not assume loop header threading in backward threader.

The registry's thread_through_all_blocks() has a may_peel_loop_headers argument. When refactoring the backward threader code, I removed this argument for the local passthru method because it was always TRUE. This may not necessarily be true in the future, if the backward threader is called from

Re: [PATCH 6/8] coroutines: Convert implementation variables to debug-friendly form.

> On 3 Sep 2021, at 14:52, Jason Merrill wrote: > > On 9/1/21 6:55 AM, Iain Sandoe wrote: >> The user might well wish to inspect some of the state that represents >> the implementation of the coroutine machine. >> In particular: >> The promise object. >> The function pointers for the

[PATCH] Improve backwards threader debugging dumps.

This patch adds debugging helpers to the backwards threader. I have also noticed that profitable_path_p() can bail early on paths that crosses loops and leave the dump of blocks incomplete. Fixed as well. Unfortunately the new methods cannot be marked const, because we call the solver's dump

[PATCH] Dump reason why threads are being cancelled and abstract code.

We are inconsistent on dumping out reasons why a thread was canceled. This makes debugging jump threading problems harder because paths can be canceled with no reason given. This patch abstracts out the thread canceling code and adds a reason for every cancellation. Tested on x86-64 Linux. OK?

Re: [PATCH 6/8] coroutines: Convert implementation variables to debug-friendly form.

On 9/1/21 6:55 AM, Iain Sandoe wrote: The user might well wish to inspect some of the state that represents the implementation of the coroutine machine. In particular: The promise object. The function pointers for the resumer and destroyer. The current resume index (suspend point).

[COMMITTED] Avoid using unavailable objects in jt_state.

[Jeff: I'm going to go out on a limb here and commit this under the obvious rule. If I am overstepping my obvious powers, please let me know.] The jump threading state is about to get more interesting, and it may get with a ranger or with the const_copies/etc helpers. This patch makes sure we

Re: [PATCH 5/8] coroutines: Define and populate accessors for debug state.

On 9/3/21 9:42 AM, Iain Sandoe wrote: On 3 Sep 2021, at 14:39, Jason Merrill wrote: On 9/1/21 6:54 AM, Iain Sandoe wrote: This is an efficiency measure and repeats the pattern used for other identifiers used in the coroutine implementation. In support of debugging, the user might well need

[COMMITTED] Do not release state location until after path registry.

We are popping state and then calling the registry code. This causes the registry to have incorrect information. This isn't visible in current trunk, but will be an issue when I submit further enhancements to the threading code. However, it is a cleanup on its own so I am pushing it now.

Re: [PATCH 5/8] coroutines: Define and populate accessors for debug state.

> On 3 Sep 2021, at 14:39, Jason Merrill wrote: > > On 9/1/21 6:54 AM, Iain Sandoe wrote: >> This is an efficiency measure and repeats the pattern used for >> other identifiers used in the coroutine implementation. >> In support of debugging, the user might well need to look at some >> of the

Re: [PATCH 5/8] coroutines: Define and populate accessors for debug state.

> On 3 Sep 2021, at 14:39, Jason Merrill wrote: > > On 9/1/21 6:54 AM, Iain Sandoe wrote: >> This is an efficiency measure and repeats the pattern used for >> other identifiers used in the coroutine implementation. >> In support of debugging, the user might well need to look at some >> of the

Re: [PATCH 5/8] coroutines: Define and populate accessors for debug state.

On 9/1/21 6:54 AM, Iain Sandoe wrote: This is an efficiency measure and repeats the pattern used for other identifiers used in the coroutine implementation. In support of debugging, the user might well need to look at some of the variables that the implementation manipulates in lowering the

[COMMITTED] Add debug helper for jump thread paths.

Committed as obvious. Tested on x86-64 Linux. gcc/ChangeLog: * tree-ssa-threadupdate.c (debug): New. --- gcc/tree-ssa-threadupdate.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/gcc/tree-ssa-threadupdate.c b/gcc/tree-ssa-threadupdate.c index d08e7d30d8d..1d32a0230fb 100644

Re: [PATCH 4/8] coroutines: Make some of the artificial names more debugger-friendly.

On 9/1/21 6:54 AM, Iain Sandoe wrote: Some of the compiler-generated entries are of interest to a user debugging - keep variables in the implementation namespace but avoid using periods as separators (which is not compatible with visible symbols for some assemblers). Partial improvement to

Re: PATCH 3/8] coroutines: Support for debugging implementation state.

On 9/1/21 6:53 AM, Iain Sandoe wrote: Some of the state that is associated with the implementation is of interest to a user debugging a coroutine. In particular items such as the suspend point, promise object, and current suspend point. These variables live in the coroutine frame, but we can

[COMMITTED] Add function name when dumping ranger contents.

These are minor cleanups to the dumping code. Tested on x86-64 Linux. gcc/ChangeLog: * gimple-range-trace.cc (debug_seed_ranger): Remove static. (dump_ranger): Dump function name. --- gcc/gimple-range-trace.cc | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff

[COMMITTED] Use non-null knowledge in path_range_query.

[Jeff, I'm CCing you to keep you in the loop on changes that will impact jump threading. Since we're using one engine, any changes to the either ranger or the path solver, is likely to improve jump threading.] This patch improves ranges for pointers we are interested in a path, by using the

[committed] libgomp.*/error-1.{c,f90}: Fix dg-output newline pattern

Fixes the testcase for \r\n line breaks → r12-3327-g4ce90454c2c81246be993d997cab12e21bc0be68 Tobias - Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf;

[Bug bootstrap/100832] s390x-linux-gnu: wrong number of alternatives in the output template

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100832 Jan-Benedict Glaw changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[COMMITTED] Improve path_range_query dumps.

Tested on x86-64 Linux. gcc/ChangeLog: * gimple-range-path.cc (path_range_query::dump): Dump path length. (path_range_query::precompute_ranges): Dump entire path. --- gcc/gimple-range-path.cc | 14 -- 1 file changed, 12 insertions(+), 2 deletions(-) diff

[COMMITTED] Implement relation_oracle::debug.

Tested on x86-64 Linux. gcc/ChangeLog: * value-relation.cc (relation_oracle::debug): New. * value-relation.h (relation_oracle::debug): New. --- gcc/value-relation.cc | 6 ++ gcc/value-relation.h | 1 + 2 files changed, 7 insertions(+) diff --git a/gcc/value-relation.cc

  1   2   >