[PATCH PR94969]Add unit distant vector to DDR in case of invariant access functions

Hi, As analyzed in PR94969, data dependence analysis now misses dependence vector for specific case in which DRs in DDR have the same invariant access functions. This simple patch fixes the issue by also covering invariant cases. Bootstrap and test on x86_64, is it OK? Thanks, bin

Re: [RFC c-common PATCH] PR c++/40752 - useless -Wconversion with short +=.

On 1/10/20, Jason Merrill wrote: > Back in 2009 Manuel sent a patch to avoid useless -Wconversion warnings > on compound assignment of types that get promoted to int: > > https://gcc.gnu.org/ml/gcc-patches/2009-08/msg00582.html > > Joseph argued that those warnings are sometimes useful, and that

Re: Fix Debug mode Undefined Behavior

I just committed this patch. François On 03/03/20 10:11 pm, François Dumont wrote: After the fix of PR 91910 I tried to consider other possible race condition and I think we still have a problem. Like stated in the PR when a container is destroyed all associated iterators are made singular.

New German PO file for 'gcc' (version 10.1.0)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'gcc' has been submitted by the German team of translators. The file is available at: https://translationproject.org/latest/gcc/de.po (This file, 'gcc-10.1.0.de.po', has

Re: [PATCH] make minmax detection work with FMIN/FMAX IFNs

On Sun, 10 May 2020, Uros Bizjak wrote: > So, I found [1], that tries to explain this issue. > > [1] https://2pi.dk/2016/05/ieee-min-max I would also recommend reading this report that covers a few more architectures and issues with IEEE754 definitions:

Re: [PATCH] make minmax detection work with FMIN/FMAX IFNs

On Fri, May 8, 2020 at 4:38 PM Richard Biener wrote: > > On May 8, 2020 4:28:24 PM GMT+02:00, Alexander Monakov > wrote: > >On Fri, 8 May 2020, Uros Bizjak wrote: > > > >> > Am I missing something? > >> > >> Is the above enough to declare min/max as IEEE compliant? > > > >No. SSE min/max

New Swedish PO file for 'gcc' (version 10.1.0)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'gcc' has been submitted by the Swedish team of translators. The file is available at: https://translationproject.org/latest/gcc/sv.po (This file, 'gcc-10.1.0.sv.po', has

[PATCH] rs6000: Add vec_extracth and vec_extractl

From: Kelvin Nilsen Add new insns vextdu[bhw]vlx, vextddvlx, vextdu[bhw]vhx, and vextddvhx, along with built-in access and overloaded built-in access to these insns. Bootstrapped and tested on powerpc64le-unknown-linux-gnu with no regressions, using a Power9 configuration. Is this okay for

[committed] wwwdocs: Move refspecs.linuxbase.org to https.

Pushed. Gerald --- htdocs/readings.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/htdocs/readings.html b/htdocs/readings.html index 0dd27368..086baaa1 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -313,8 +313,8 @@ names. Manufacturer: IBM

Ping: [PATCH] libiberty: Update D symbol demangling for latest ABI spec.

Ping On 03/05/2020 09:37, Iain Buclaw via Gcc-patches wrote: > Ping. > > There is a new mangle string "Nm" in the abi to denote the @live attribute, > however will add support in a follow up patch. > > > On 15 April 2020 12:04:29 CEST, Iain Buclaw via Gcc-patches > wrote: >> Ping. >> >> On

Re: [Patch] PR fortran/93499 - ICE on division by zero in declaration statements

Hi Harald, the attached should be mostly self-explaining. Division by zero handling appeared to be incomplete. It was not dealt with properly when occurring in declaration statements. We now try to handle this. OK for mainline? OK. Thanks for the patch! Regards Thomas

Re: [Patch] (general Fortran + OpenMP) [Fortran] Fix/modify present() handling for assumed-shape optional (PR 94672)

Hi Tobias, For assumed shape, gfortran generates an "arg.0 = arg->data" artificial variable – and with optional one has something like if (arg != NULL && arg->data != NULL)   {     arg.0 = arg->data;     lbound.0 = ...   } And an "if (present(arg))" becomes "if (arg != NULL && arg->data