On 6/24/20 4:15 PM, Richard Biener wrote:
On Wed, Jun 24, 2020 at 11:27 AM Martin Liška wrote:
On 6/24/20 11:09 AM, Richard Biener wrote:
On Wed, Jun 24, 2020 at 10:49 AM Martin Liška wrote:
On 6/24/20 9:43 AM, Richard Biener wrote:
Hmm, can you instead use simple_dce_from_worklist and si
Please find attached a proposed legacy extension to allow dimensions to
be omitted when referring to an array element. The declared lower bound
being used by default.
This feature is known to exist in earlier compilers and is believed to
be a DEC extension and is definitely supported by flang
Hi Thomas,
Updated patch – now having submitted the mapping patch,
I can focus on other things, including this patch.
I have now removed the setting of the typespec – and
added an assert to be sure everything is consistent.
At least for the testsuite, it is.
Thanks for insisting on doing it pro
On Thu, Jun 25, 2020 at 2:53 AM Sunil Pandey wrote:
>
> On Wed, Jun 24, 2020 at 12:30 AM Richard Biener
> wrote:
> >
> > On Tue, Jun 23, 2020 at 5:31 PM Sunil K Pandey via Gcc-patches
> > wrote:
> > >
> > > From: Sunil K Pandey
> > >
> > > Default for this hook is NOP. For x86, in 32 bit mode,
On Wed, Jun 24, 2020 at 6:22 PM H.J. Lu wrote:
>
> CLWB isn't supported on Ice Lake client. But Ice Lake server and Tiger
> Lake support it. Move PTA_CLWB to PTA_ICELAKE_SERVER and PTA_TIGERLAKE.
>
> PR target/95874
> * config/i386/i386.h (PTA_ICELAKE_CLIENT): Remove PTA_CLWB.
>
On Wed, Jun 24, 2020 at 09:22:51PM -0400, y2s1982 wrote:
> +#ifndef LIBGOMPD_H
> +#define LIBGOMPD_H 1
> +
> +#define ompd_str1(x) ompd_str2(x)
> +#define ompd_str2(x) #x
I'd call ompd_str1 (the one that should be actually used)
just ompd_str or ompd_stringify.
> --- /dev/null
> +++ b/libgomp/lib
Hi.
The patch is about broken summary merge when gcov-tool is used.
I've just tested the patch and I'm going to push it to master.
Martin
libgcc/ChangeLog:
* libgcov-driver.c (merge_summary): Remove function as its name
is misleading and doing something different.
(dump
Hi Ian, Hi Nick,
Comping the GOLD linker with Clang has started producing this error
message:
In file included from gold/archive.cc:29:
include/libiberty.h:646:25: error: 'register' storage class
specifier is deprecated and incompatible with C++17
[-Werror,-Wdeprecated-reg
Hi Ian, Hi Nick,
Compiling the GOLD linker with Clang has started producing this error
message:
In file included from gold/archive.cc:29:
include/libiberty.h:646:25: error: 'register' storage class
specifier is deprecated and incompatible with C++17
[-Werror,-Wdeprecated-r
This avoids using the original scalar SSA operand when vectorizing
a shift with a vectorized shift operand where we know all vector
components have the same value and thus we can use a vector by
scalar shift. Using the scalar SSA operand causes a possibly
long chain of scalar computation to be ret
This removes a premature check for enough datarefs in a basic-block
before we consider vectorizing it which leaves basic-blocks with
just vectorizable vector constructors unvectorized. The check
is effectively done by the following check for store groups
which then also include constructors.
Boot
Hi Julian!
On 2020-05-22T15:16:06-0700, Julian Brown wrote:
> Since goacc_enter_datum only maps a single data item now, there is no
> need to pass "kinds" as an array. Passing as a scalar allows for some
> simplification in the function's callers.
You'd hope (didn't verify) that the compiler ca
On 25 Jun 2020, Nick Clifton outgrape:
> Hi Ian, Hi Nick,
>
> Comping the GOLD linker with Clang has started producing this error
> message:
>
> In file included from gold/archive.cc:29:
> include/libiberty.h:646:25: error: 'register' storage class
> specifier is deprecated and i
Hi Julian!
Ping, in particular my question about different 'GOMP_MAP_FORCE_FROM' vs.
'GOMP_MAP_FROM' handling.
(I have not yet looked whether 'GOMP_MAP_ALWAYS_FROM' may be generate
nowadays, given your pending front end/middle end patches.)
On 2020-05-19T17:58:16+0200, I wrote:
> On 2019-12-17T2
Hi Nick, Hi Ian,
>> In file included from gold/archive.cc:29:
>> include/libiberty.h:646:25: error: 'register' storage class
>> specifier is deprecated and incompatible with C++17
>> [-Werror,-Wdeprecated-register]
>>
>> So I would like to apply the patch below to fix this.
Hi,
...into bit tests, as done by optimize_range_tests_to_bit_test of the reassoc
pass. The patch is aimed at addressing the following two issues:
1. In order to protect the shift operation from undefinedness, the new bit
test is guarded with a new test, but this new test uses the range of t
On Wed, 2020-06-24 at 16:16 +0200, Richard Biener wrote:
> On Wed, Jun 24, 2020 at 4:14 PM Jonathan Wakely via Gcc-patches
> wrote:
> > On 24/06/20 12:31 +0200, Ilya Leoshkevich wrote:
> > > Bootstrapped and regtested on x86_64-redhat-linux, ppc64le-
> > > redhat-linux
> > > and s390x-redhat-linux
Hi Julian!
On 2020-06-16T15:39:42-0700, Julian Brown wrote:
> This is a fix for the pointer (or array) size inadvertently being used
> for the bias of attach and detach clauses (PR95270)
Thanks for looking into that one, which had caused my some gray hair.
> for C and C++.
That means, there is
With the last vectorizable_shift patch we can now always use the
SLP vector defs to determine the vectorized stmt insertion place,
paving the way for a "verifier" for pending restructuring and
BB vectorization of reductions and other live stmts.
Bootstrapped and tested on x86_64-unknown-linux-gnu,
On 25/06/20 13:29 +0200, Ilya Leoshkevich wrote:
On Wed, 2020-06-24 at 16:16 +0200, Richard Biener wrote:
On Wed, Jun 24, 2020 at 4:14 PM Jonathan Wakely via Gcc-patches
wrote:
> On 24/06/20 12:31 +0200, Ilya Leoshkevich wrote:
> > Bootstrapped and regtested on x86_64-redhat-linux, ppc64le-
> >
On Wed, Jun 24, 2020 at 1:31 AM Ilya Leoshkevich via Gcc-patches
wrote:
>
> Bootstrapped and regtested x86_64-redhat-linux, ppc64le-redhat-linux and
> s390x-redhat-linux. I also ran SPEC 2006 and 2017 on these platforms,
> and the only measurable regression was 3% in 520.omnetpp_r on ppc, which
>
On 6/24/20 2:37 PM, Segher Boessenkool wrote:
> On Wed, Jun 24, 2020 at 02:28:00PM -0500, Peter Bergner via Gcc-patches wrote:
>> The back ports of the MMA patches/commits was straight forward and I'm
>> currently bootstrapping/regtesting the backports on both powerpc64le-linux
>> and powerpc64-lin
On 24/06/2020 6:29 pm, Tobias Burnus wrote:
Hi Kwok,
the TODO is fixed by the attached patch; I would be happy if you could handle
this patch,
e.g. together with your patch – or as follow up.
(Lightly tested only, i.e. it fixes the ICE but I did not
do a full testsuite run. But I regard it as
The test case was giving an ICE as it recursively called itself.
Rather obvious fix.
OK for the trunk?
Tobias
-
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander
Walter
[F
Hi Tobias,
OK – with assert or without?
I don't think the assert is needed - if things go wrong there, then
I am quite sure that we will get all sorts of ICEs downstream if
this is not set correctly somewhere after all, and your testing
indicates that it is not.
Besides, I like the elegance o
Hi Tobias!
On 2020-06-24T15:36:25+0200, Tobias Burnus wrote:
> [...] who knows
> what users are doing...
Indeed. ;-)
> On 6/23/20 9:36 PM, Thomas Schwinge wrote:
>> I don't think I can approve, but seems fine if this works (as you've
>> confirmed) -- it's one incremental step forward!
(Notin
Hi,
The PR points out that the standard does not restrict promise
expressions to methods, but the current implementation does.
The patch factors out the building of a general promise expression,
and then uses it in a fairly mechanical replacement of each case
that we need such an expressions.
Th
On 6/25/20 11:15 AM, Iain Sandoe wrote:
Hi,
The PR points out that the standard does not restrict promise
expressions to methods, but the current implementation does.
The patch factors out the building of a general promise expression,
and then uses it in a fairly mechanical replacement of each
Hi,
This patch fixes an ICE in uda_attribute_p when looking up an unknown
attribute. The target attribute table is not guaranteed to be set by
all backends.
Bootstrapped and regression tested on x86_64-linux-gnu, and committed to
mainline.
Regards
Iain.
---
gcc/d/ChangeLog:
PR d/95173
Hi,
This patch fixes a logic bug in the code-gen for variable declarations.
Declarations initialized with `= void` were being default initialized.
That is not really the intent, and misses the small optimization that
should have been gained from using void initializations.
Bootstrapped and regre
Hi,
This patch merges the D front-end implementation with upstream dmd
4be011355. Fixes self-assignment warnings seen when compiling with
clang.
Bootstrapped and regression tested on x86_64-linux-gnu, and committed to
mainline.
Regards
Iain.
---
gcc/d/ChangeLog:
PR d/95075
* d
Hi,
This patch removes the implicit setting of DECL_DECLARATED_INLINE_P on
member function.
This has been questionable behaviour since it was added, and though it
has no effect on wider discussions around what should be the correct
semantics of pragma(inline) within D modules, doing this tree-lev
Hi,
This patch merges the D front-end implementation with upstream dmd
5fc1806cd. Backports the OutBuffer interface from upstream dmd master,
removing another difference this and the self-hosted D branch that is
purely refactoring, and doesn't introduce any mechanical changes.
Bootstrapped and r
Hi,
This patch merges the D front-end implementation with upstream dmd
4f1046222. Renames OnScopeStatement to ScopeGuardStatement.
Bootstrapped and regression tested on x86_64-linux-gnu, and committed to
mainline.
Regards
Iain.
---
gcc/d/ChangeLog:
* dmd/MERGE: Merge upstream dmd 4f10
Hi,
This patch merges the D front-end implementation with upstream dmd
90450f3ef. Fixes a regression caused by an incomplete backport of
converting the Expression semantic pass to a Visitor.
Bootstrapped and regression tested on x86_64-linux-gnu, and committed to
mainline.
Regards
Iain.
---
gc
Hi Guys,
I am checking in the patch below to fix several failures in the GCC
testsuite for the M32R target. The issue is the movsicc pattern which
is a holdover from when the port from converted from using cc0. The
pattern was written as if a previous instruction had set the CC bits,
w
Hi,
This patch moves d_signed_type and d_unsigned_type to types.cc.
These two functions are not tied to the language-specific part of the
front-end in any way.
Bootstrapped and regression tested on x86_64-linux-gnu, and committed to
mainline.
Regards
Iain.
---
gcc/d/ChangeLog:
* d-lan
Hi,
This patch makes deprecation warnings the default in gdc, fixing both
the library and any tests that are currently using deprecated styles.
This is the default in the upstream reference compiler, and can reduce
some confusion when comparing warning/error messages of gdc and dmd side
by side.
Hi,
This patch removes another dependency on the front-end OutBuffer type.
As the DMD front-end never frees allocated memory, the glue layer
between the DMD front-end and GCC should generally avoid using DMD types
and interfaces if the purpose is internal only.
Bootstrapped and regression tested
On Thu, 2020-06-25 at 16:41 +0100, Nick Clifton via Gcc-patches wrote:
> Hi Guys,
>
> I am checking in the patch below to fix several failures in the GCC
> testsuite for the M32R target. The issue is the movsicc pattern which
> is a holdover from when the port from converted from using cc0.
PING
On Thu, Jun 18, 2020, 13:24 Aldy Hernandez wrote:
> Howdy.
>
> This moves all the simplification code from vr_values into a separate
> class (simplify_using_ranges). In doing so, we get rid of a bunch of
> dependencies on the internals of vr_values. The goal is to (a) remove
> unnecessary
Hello Jakub,
Thank you for the feedback. I can't believe I made some careless mistakes.
I am also very interested in learning some new techniques mentioned. I had
some questions about them.
On Thu, Jun 25, 2020 at 4:28 AM Jakub Jelinek wrote:
>
> > --- /dev/null
> > +++ b/libgomp/libgompd.map
>
>
>
> > --- /dev/null
> > +++ b/libgomp/libgompd.map
> > @@ -0,0 +1,49 @@
> > +OMPD_5.0 {
> > + global:
> > + ompd_dll_locations_valid;
>
> ompd_dll_locations and ompd_dll_locations_valid both need to be exported,
> but not from libgompd.so.1 but from libgomp.so.1, so they need to go into
> li
On Mon, Jun 01, 2020 at 03:53:37PM -0400, Michael Meissner wrote:
> Add tests for -mcpu=future that test the generation of PADDI (and PLI which
> becomes PADDI).
>
> 2020-06-01 Michael Meissner
>
> * gcc.target/powerpc/prefix-add.c: New test.
> * gcc.target/powerpc/prefix-si-consta
Nick Clifton writes:
> Hi Nick, Hi Ian,
>>> In file included from gold/archive.cc:29:
>>> include/libiberty.h:646:25: error: 'register' storage class
>>> specifier is deprecated and incompatible with C++17
>>> [-Werror,-Wdeprecated-register]
>>>
>>> So I would like to apply
On Mon, Jun 01, 2020 at 03:53:38PM -0400, Michael Meissner wrote:
> Add test to make sure prefixed load/store instructions are generated if the
> offset would not fit in the DS/DQ encodings.
>
> 2020-06-01 Michael Meissner
>
> * gcc.target/powerpc/prefix-ds-dq.c: New test.
Okay for trun
On Mon, Jun 01, 2020 at 03:53:39PM -0400, Michael Meissner wrote:
> This test makes sure we do not generate a prefixed instruction with an update
> form.
>
> 2020-06-01 Michael Meissner
>
> * gcc.target/powerpc/prefix-no-update.c: New test.
Okay like 2 and 3. Thanks!
Segher
Hi!
On Thu, Jun 04, 2020 at 01:03:51PM -0400, Michael Meissner wrote:
> [PATCH 5/7, V2] PowerPC tests: Prefixed insn with large offsets
>
> Add tests to make sure for -mcpu=future that prefixed load/store instructions
> are generated if the offset is larger than 16 bits. The only difference
> is
On Thu, Jun 04, 2020 at 01:05:12PM -0400, Michael Meissner wrote:
> [PATCH 6/7, V2] PowerPC tests: Add PC-relative tests.
>
> These tests make sure that PC-relative variant is generated for -mcpu=future
> on
> systems that support PC-relative addressing. The only difference
> is I reworded the c
Hi!
On Mon, Jun 01, 2020 at 03:53:42PM -0400, Michael Meissner wrote:
> Test that stack protection generates prefixed stack instructions if you are
> using large stack frame for -mcpu=future.
>
> 2020-06-01 Michael Meissner
>
> * gcc.target/powerpc/prefix-stack-protect.c: New test.
> +
On Wed, 24 Jun 2020, Asher Gordon via Gcc-patches wrote:
> I see. So perhaps this isn't the best way to go about implementing
> attribute locations. What do you think would be a better way? Perhaps
> using a DECL_MINIMAL for attributes?
In general, too many things in GCC have the static type "tre
On Thu, Jun 25, 2020 at 12:17:05PM -0400, y2s1982 . wrote:
> Ah, so code in env.c gets executed before OMPD gets started?
Not all, but initialize_env is the library constructor (has constructor
attribute) and is invoked during the library initialization.
>
> Include omp-tools.h and plugin-suffix.
On Thu, Jun 25, 2020 at 12:27:32PM -0400, y2s1982 . via Gcc-patches wrote:
> > > --- /dev/null
> > > +++ b/libgomp/libgompd.map
> > > @@ -0,0 +1,49 @@
> > > +OMPD_5.0 {
> > > + global:
> > > + ompd_dll_locations_valid;
> >
> > ompd_dll_locations and ompd_dll_locations_valid both need to be exp
I think both the patches in this discussion (special { 0 } handling and
the new warning option) generally look good. I don't see you in the FSF
copyright assignment list; could you complete
https://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future
(unless you're a
Hi Thomas,
> Thanks for tackling this! I haven't checked, but you are
> probably setting a new record for bug fixes per second now :-)
I'm trying hard, but I definitely cannot outpace Gerhard. Any attempt
in this regard seems futile. |-:
The good thing is that while hunting down things there'
Joseph Myers writes:
> I think both the patches in this discussion (special { 0 } handling
> and the new warning option) generally look good.
I also wrote another small patch, which you might have missed since it's
buried in the discussion here:
https://gcc.gnu.org/pipermail/gcc-patches/2020-Jun
Tag the floating-point calling convention used on m68k-elf (either hard-float
or soft-float) through the GNU assembler attribute. The use of the tag enables
the linker to ensure linked objects use a consistent floating-point ABI and
allows tools like GDB to infer the ABI used from the ELF file. It
This PR is due to a plain NULL pointer that needs to get caught in the right
place.
Regtested on x86_64-pc-linux-gnu.
OK for master / backports where applicable?
Thanks,
Harald
PR fortran/93337 - ICE in gfc_dt_upper_string, at fortran/module.c:441
When declaring a polymorphic variable that i
A simple situation where a NULL pointer dereference occurs during error
recovery.
Regtested on x86_64-pc-linux-gnu.
OK for master / backports?
Thanks,
Harald
PR fortran/93423 - ICE on invalid with argument list for module procedure
When recovering from an error, a NULL pointer dereference co
Hi!
On Thu, Jun 18, 2020 at 03:20:14PM -0700, Carl Love wrote:
> +;; Map UNSPEC_SLDB to "l" and UNSPEC_SRDB to "r".
> +(define_int_attr SLDB_LR [(UNSPEC_SLDB "l")
> + (UNSPEC_SRDB "r")])
Most (all?) other attributes that always result in lower case strings
are written in lo
On Wed, Jun 24, 2020 at 03:52:12PM -0400, Jason Merrill via Gcc-patches wrote:
> On 6/23/20 6:58 PM, Marek Polacek wrote:
> > 95568 complains that CTAD for aggregates doesn't work within
> > requires-clause and it turned out that it doesn't work when we try
> > the deduction in a template. The rea
From: y2s82 <1997371+y2...@users.noreply.github.com>
This patch adds some unit tests for omp-tools.h header. It also adds some simple
functions variables related to OMPD API versions and dll locations.
It also partially defines the OMPD initialization function.
More OMPD configuration is also adde
Hi!
On Thu, Jun 18, 2020 at 03:20:18PM -0700, Carl Love wrote:
> * config/rs6000/altivec.md (UNSPEC_XXSPLTIW, UNSPEC_XXSPLTID,
> UNSPEC_XXSPLTI32DX): New.
> (vxxspltiw_v4si, vxxspltiw_v4sf_inst, vxxspltidp_v2df_inst,
> vxxsplti32dx_v4si_inst, vxxsplti32dx_v4sf_inst): New de
Fixed by r271705.
Tested x86_64-pc-linux-gnu, applying to trunk.
gcc/testsuite/ChangeLog:
PR c++/91104
* g++.dg/cpp1y/lambda-generic-variadic21.C: New test.
---
.../g++.dg/cpp1y/lambda-generic-variadic21.C | 26 +++
1 file changed, 26 insertions(+)
create mode
rs6000: Add support for __builtin_cpu_is ("power10")
Add support for __builtin_cpu_is ("power10"). Also add documentation for
the recently added "arch_3_1" and "mma" __builtin_cpu_supports arguments.
This passed bootstrap and regtesting with no regressions. Ok for trunk?
Peter
gcc/
*
Hi!
On Thu, Jun 25, 2020 at 06:36:51PM -0500, Peter Bergner wrote:
> rs6000: Add support for __builtin_cpu_is ("power10")
>
> Add support for __builtin_cpu_is ("power10"). Also add documentation for
> the recently added "arch_3_1" and "mma" __builtin_cpu_supports arguments.
> gcc/
> * con
On 6/25/20 6:54 PM, Segher Boessenkool wrote:
> Okay for trunk (maybe leave out the comma part). Thanks!
Ok, I pushed the patch without the ',' change. Thanks!
Peter
67 matches
Mail list logo
