On Mon, 11 May 2020, Uros Bizjak wrote:
> Attached patch implements V2SFmode FMA insn patterns. Patched compiler
> vectorizes FMA, FMS and FNMA instructions, but for some reason fails
> to vectorize FNMS.
>
> I have double checked that the insn pattern is correct, and now I'm
> all out of ideas
Documents operand modifiers which are available in asm stmt but
missing in document.
| Modifier | Description | Available in asm stmt | Existed in documentation |
| --- | --- | --- | - |
| L,W,B,Q,S,T | print the opcode suffix for specified size of
operand. | Available | Not |
| C |
On Mon, May 11, 2020 at 09:31:41PM -0500, Bill Schmidt wrote:
> On 5/11/20 7:16 AM, Segher Boessenkool wrote:
> >>* config/rs6000/rs6000-c.c (altivec_resolve_overloaded_builtin):
> >>Change fourth operand for vec_ternarylogic to require
> >>compatibility with unsigned SImode rather
On 5/11/20 9:48 AM, David Edelsohn wrote:
On Sun, May 10, 2020 at 9:14 AM Bill Schmidt wrote:
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
On 5/11/20 7:16 AM, Segher Boessenkool wrote:
Hi!
On Sat, May 09, 2020 at 08:08:34PM -0500, Bill Schmidt wrote:
I should have noticed this patch before submitting Kelvin's earlier
related patches, sorry. I think it should still be fine to apply
the patches in order, but if you'd like me to
Hi,
> -Original Message-
> From: Richard Sandiford [mailto:richard.sandif...@arm.com]
> Sent: Monday, May 11, 2020 10:27 PM
> To: Yangfei (Felix)
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH PR94991] aarch64: ICE: Segmentation fault with option -
> mgeneral-regs-only
>
> LGTM.
Attn: HR Dept. (GCC GNU ORG)
Dear Sir/Ma'am,
We (S.A.Z Universal Links) are a dedicated ‘Recruitment and Staffing’ Company
in the sense that we can staff for a range of different industries. We work in
a strategically processed manner to help industries attain potential
candidates. We
This libgo patch by Eric Fang fixes TestCallersNilPointerPanic when
using GoLLVM. The expected result of TestCallersNilPointerPanic has
changed in GoLLVM. This change makes some elements of the expected
result optional so that this test passes in both gccgo and GoLLVM.
Bootstrapped and ran Go
This libgo patch changes some tests in the syscall package to append
to the environment in tests rather than clobbering the environment.
In particular, this preserves LD_LIBRARY_PATH.
This is a partial backport of https://golang.org/cl/233318 from the
master sources. It's only a partial backport
This patch to the Go frontend uses const string references in a couple
of places that were using plain std::string. This will save some
std::string copying. This fixes GCC PR 94766. Bootstrapped and ran
Go testsuite on x86_64-pc-linux-gnu. Committed to master.
Ian
diff --git
I forgot to set DECL_HAS_DEPENDENT_EXPLICIT_SPEC_P when merging two
function declarations and as a sad consequence, we never tsubsted
the dependent explicit-specifier in tsubst_function_decl, leading to
disregarding the explicit-specifier altogether, and wrongly accepting
this test.
In the testcase below we're prematurely folding away the
requires-expression to 'true' after substituting in the function's
template arguments, but before substituting in the lambda's deduced
template arguments.
This happens because during the first tsubst_requires_expr,
processing_template_decl
On 5/11/20 5:21 AM, Segher Boessenkool wrote:
Hi!
On Sat, May 09, 2020 at 12:05:08PM -0500, Bill Schmidt wrote:
From: Carl Love
Add support for xxgenpcv[dw]m, along with individual and overloaded
built-in functions for access.
(xxgenpcvm_): New insn.
(xxgenpcvm): New
This commit is for the benefit of GDB, but as the binutils-gdb
repository shares the contrib/ directory with gcc, this commit must
first be applied to gcc then copied back to binutils-gdb.
This commit extends the two scripts contrib/dg-extract-results.{py,sh}
to handle some new, GDB specific test
I *think* I have addressed everything in the attached patch.
commit 24a989d2bf2158bdbe2511310d0583d0c6226f71
Author: Thomas Rodgers
Date: Mon Apr 6 17:58:47 2020 -0700
Add C++2a synchronization support
Add support for -
atomic wait/notify_one/notify_all
On Fri, 8 May 2020, Richard Biener wrote:
> The IFNs are supposed to match fmin and fmax from the C standard which
> IIRC have IEEE semantics.
fmin and fmax have IEEE (2008) semantics (where an sNaN operand results in
a qNaN result with "invalid" raised", but a quiet NaN results in the other
On Sun, Apr 05, 2020 at 09:46:09PM -0400, Jason Merrill wrote:
> On 4/4/20 7:30 PM, Marek Polacek wrote:
> > This patch implements DR 2237 which says that a simple-template-id is
> > no longer valid as the declarator-id of a constructor or destructor;
> > see
While looking at 92583/92654 it occurred to me that typename types needed
the same fix. So extract_locals_r also needs to see the TYPE_CONTEXT of a
TYPENAME_TYPE. But it must not look through a typedef.
Most tree walking in the front end wants to walk through the syntactic form
of a type of
The resolution of comment CA104 clarifies that we need to do direct
substitution of constraints in order to determine which member template
corresponds to an explicit specialization.
Tested x86_64-pc-linux-gnu, applying to trunk.
gcc/cp/ChangeLog
2020-05-11 Jason Merrill
Resolve
Attached patch implements V2SFmode FMA insn patterns. Patched compiler
vectorizes FMA, FMS and FNMA instructions, but for some reason fails
to vectorize FNMS.
I have double checked that the insn pattern is correct, and now I'm
all out of ideas what could be wrong with the pattern, still ignored
This improves the diagnostic from
error: could not convert ‘((A<>*)(void)0)->A<>::e’ from
‘’ to ‘bool’
to
error: cannot convert ‘A<>::e’ from type ‘void (A<>::)()’ to type ‘bool’
Tested x86_64-pc-linux-gnu, applying to trunk.
gcc/cp/ChangeLog
2020-05-11 Jason Merrill
*
We were incorrectly accepting the use of 'this' at parse time and then
crashing when we tried to instantiate it. It is invalid because 'this' is
not in scope until after the function-cv-quals. So let's hoist setting
current_class_ptr up from cp_parser_late_return_type_opt into
Committed as obvious.
Sorry for the breakage.
PR fortran/95053 - ICE in gfc_divide(): Bad basic type
The fix for PR 93499 introduced a too strict check in gfc_divide
that could trigger errors in the early parsing phase. Relax the
check and defer to a later stage.
We walk the lambda captures in cp_walk_subtrees, so we don't also need to
walk them here.
Tested x86_64-pc-linux-gnu, applying to trunk.
gcc/cp/ChangeLog
2020-05-11 Jason Merrill
* pt.c (find_parameter_packs_r) [LAMBDA_EXPR]: Remove redundant
walking of capture list.
---
If a program has no other dependencies on libstdc++, we shouldn't require it
just for __cxa_pure_virtual, which is only there to give a prettier
diagnostic before crashing the program; resolving the reference to NULL will
also crash, just without the diagnostic.
Tested x86_64-pc-linux-gnu,
We weren't printing the condition and message of a STATIC_ASSERT.
It's also unnecessary to duplicate the code for instantiating a
STATIC_ASSERT between tsubst_expr and instantiate_class_template_1.
Tested x86_64-pc-linux-gnu, applying to trunk.
gcc/cp/ChangeLog
2020-05-11 Jason Merrill
This flag is redundant with the explicit_targs field in the overload
candidate information.
Tested x86_64-pc-linux-gnu, applying to trunk.
gcc/cp/ChangeLog
2020-05-11 Jason Merrill
* cp-tree.h (LOOKUP_EXPLICIT_TMPL_ARGS): Remove.
* call.c (build_new_function_call): Don't set
There's no need to warn that a deprecated function uses a deprecated type,
that just adds noise. We were preventing that in start_decl, but that
didn't help member declarations that go through grokfield. So handle it in
grokdeclarator instead, which is shared between them.
Tested
If we put the SAVE_EXPR for a VLA size inside the MINUS_EXPR rather than
outside, it will work better with constant folding.
The equivalent change was made in the C front-end in 2004, in commit
r0-64535-g8b0b9aefd29dfe6398857bcf5628662e2f0e21f6
Tested x86_64-pc-linux-gnu, applying to trunk.
On May 11, 2020 6:41:58 PM GMT+02:00, Richard Sandiford
wrote:
>This third patch of three actually fixes the PR. We were using
>8-bit BIT_FIELD_REFs to access single-bit elements, and multiplying
>the vector index by 8 bits rather than 1 bit.
>
>Tested individually on aarch64-linux-gnu and as a
On May 11, 2020 6:35:58 PM GMT+02:00, Richard Sandiford
wrote:
>A lot of code that wants to know the number of bits in a vector
>element gets that information from the element's TYPE_SIZE,
>which is always equal to TYPE_SIZE_UNIT * BITS_PER_UNIT.
>This doesn't work for SVE and AVX512-style
On May 11, 2020 6:37:43 PM GMT+02:00, Richard Sandiford
wrote:
>This patch makes build_replicated_const take the number of bits
>in VALUE rather than calculating the width from the element type.
>The callers can then use vector_element_bits to calculate the
>correct element size from the vector
gcc/ChangeLog:
2020-05-11 Uroš Bizjak
PR target/95046
* config/i386/mmx.md (sqrtv2sf2): New insn pattern.
testsuite/ChangeLog:
2020-05-11 Uroš Bizjak
PR target/95046
* gcc.target/i386/pr95046-1.c (test_sqrt): Add.
Bootstrapped and regression tested on x86_64-linux-gnu
Reportedly mingw-w64-gcc has mmap and getpagesize but does not provide
a declaration of getpagesize in any header files. Check for a
getpagesize declaration, and declare it if necessary. This is for PR
95012. Bootstrapped and ran libbacktrace tests on
x86_64-pc-linux-gnu. Committed to master.
On 11/05/20 08:43 -0700, Thomas Rodgers wrote:
Jonathan Wakely writes:
On 09/05/20 17:01 -0700, Thomas Rodgers via Libstdc++ wrote:
+#include
shouldn't be here (it adds runtime cost, as well as
compile-time).
Oversight, not removed after debugging it.
Can't this just be __old
On 5/8/20 6:51 PM, Segher Boessenkool wrote:
On Fri, May 08, 2020 at 08:17:18AM -0500, Bill Schmidt wrote:
From: Kelvin Nilsen
Add support for new scalar instructions for counting leading or
trailing zeros under control of a bitmask.
Bootstrapped and tested on powerpc64le-unknown-linux-gnu
This third patch of three actually fixes the PR. We were using
8-bit BIT_FIELD_REFs to access single-bit elements, and multiplying
the vector index by 8 bits rather than 1 bit.
Tested individually on aarch64-linux-gnu and as a series on
x86_64-linux-gnu. OK to install?
I'm not sure what to do
This patch makes build_replicated_const take the number of bits
in VALUE rather than calculating the width from the element type.
The callers can then use vector_element_bits to calculate the
correct element size from the vector type.
Tested individually on aarch64-linux-gnu and as a series on
A lot of code that wants to know the number of bits in a vector
element gets that information from the element's TYPE_SIZE,
which is always equal to TYPE_SIZE_UNIT * BITS_PER_UNIT.
This doesn't work for SVE and AVX512-style packed boolean vectors,
where several elements can occupy a single byte.
This rejects lattice changes from one constant to another.
Bootstrapped / tested on x86_64-unknown-linux-gnu, applied on trunk sofar.
2020-05-11 Richard Biener
PR tree-optimization/95049
* tree-ssa-sccvn.c (set_ssa_val_to): Reject lattice transition
between different
Jonathan Wakely writes:
> On 09/05/20 17:01 -0700, Thomas Rodgers via Libstdc++ wrote:
>>+#include
>
> shouldn't be here (it adds runtime cost, as well as
> compile-time).
>
Oversight, not removed after debugging it.
>
> Can't this just be __old instead of *std::__addressof(__old) ?
>
Hi Julian!
On 2020-01-17T13:18:21-0800, Julian Brown wrote:
> This patch adds a new function to logically decrement the "dynamic
> reference counter" for a mapped OpenACC variable, and handles some cases
> in which that counter drops to zero inside a structured data
> block. Previously, it's
On 5/8/20 3:47 PM, Segher Boessenkool wrote:
Hi,
On Thu, May 07, 2020 at 09:29:03PM -0500, Bill Schmidt wrote:
diff --git a/gcc/config/rs6000/altivec.md b/gcc/config/rs6000/altivec.md
index 5ef4889ba55..33ba57855bc 100644
--- a/gcc/config/rs6000/altivec.md
+++ b/gcc/config/rs6000/altivec.md
@@
This enhances store-order preserving store motion to handle the case
of non-invariant dependent stores in the sequence of unconditionally
executed stores on exit by re-issueing them as part of the sequence
of stores on the exit. This fixes the observed regression of
gcc.target/i386/pr64110.c
On Sun, May 10, 2020 at 9:14 AM Bill Schmidt wrote:
>
> 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
On 11/05/20 14:09 +0200, François Dumont via Libstdc++ wrote:
On 11/05/20 12:51 pm, Ville Voutilainen wrote:
On Mon, 11 May 2020 at 00:09, François Dumont via Libstdc++
wrote:
I just committed this patch.
This was a commit-without-review. When the patch was originally
posted, the
"Yangfei (Felix)" writes:
> Hi,
>
> Witnessed another ICE with option -mgeneral-regs-only.
> I have created a bug for that:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94991
>
> For the given testcase, we are doing FAIL for scalar floating move expand
> pattern since TARGET_FLOAT
>
Alex Coplan writes:
>> -Original Message-
>> From: Richard Sandiford
>> Sent: 06 May 2020 11:28
>> To: Alex Coplan
>> Cc: gcc-patches@gcc.gnu.org; Richard Earnshaw ;
>> Marcus Shawcroft ; Kyrylo Tkachov
>> ; nd
>> Subject: Re: [PATCH] aarch64: prefer using csinv, csneg in zero extend
On 09/05/20 17:01 -0700, Thomas Rodgers via Libstdc++ wrote:
* Note, this patch supersedes my previous atomic wait and semaphore
patches.
Add support for -
atomic wait/notify_one/notify_all
counting_semaphore
binary_semaphore
latch
* include/Makefile.am
ping?
On 5/5/20 4:08 PM, Nathan Sidwell wrote:
I discovered that libitm:
(a) declares __cxa_allocate_exception and friends directly,
(b) doesn't mark them as 'throw()'
(c) doesn't mark the replacment fns _ITM_$foo as nothrow either
We happen to get away with it because of code in the compiler
It looks like hash table sanitization is now safe to enable for the
decl_specializations and type_specializations tables, probably ever
since PR94454 was fixed.
Bootstrapped and regtested on x86_64-pc-linux-gnu with the attached
debugging patch that makes all entries hash to 0, and also
On Mon, May 11, 2020 at 7:52 AM bin.cheng via Gcc-patches
wrote:
>
> 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
On Fri, May 8, 2020 at 7:11 PM Jeff Law via Gcc-patches
wrote:
>
> On Fri, 2020-05-08 at 13:06 -0300, Giuliano Belinassi via Gcc-patches wrote:
> > Hi,
> >
> > This patch Refactors tree-vrp.c to eliminate all global variables except
> > 'x_vrp_values', which will require that
On Mon, May 11, 2020 at 1:26 PM Martin Liška wrote:
>
> Hi.
>
> Starting from r11-165-geb72dc663e9070b2 we should not rewrite parameters that
> have DECL_NOT_GIMPLE_REG_P set to true.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
Hmm, I
This canonicalizes those to a constant literal.
Bootstrap / regtest running on x86_64-unknown-linux-gnu.
2020-05-11 Richard Biener
* gimple-fold.c (maybe_canonicalize_mem_ref_addr): Canonicalize
literal constant [..] to a constant literal.
---
gcc/gimple-fold.c | 23
Hi!
On Sat, May 09, 2020 at 08:08:34PM -0500, Bill Schmidt wrote:
> I should have noticed this patch before submitting Kelvin's earlier
> related patches, sorry. I think it should still be fine to apply
> the patches in order, but if you'd like me to combine this into the
> two earlier ones, I'd
On 11/05/20 12:51 pm, Ville Voutilainen wrote:
On Mon, 11 May 2020 at 00:09, François Dumont via Libstdc++
wrote:
I just committed this patch.
This was a commit-without-review. When the patch was originally
posted, the maintainer said
"Let's revisit it in a few weeks.". That's not the same as
Hi.
Starting from r11-165-geb72dc663e9070b2 we should not rewrite parameters that
have DECL_NOT_GIMPLE_REG_P set to true.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
Thanks,
Martin
gcc/ChangeLog:
2020-05-11 Martin Liska
PR
On Mon, 11 May 2020 at 00:09, François Dumont via Libstdc++
wrote:
>
> I just committed this patch.
This was a commit-without-review. When the patch was originally
posted, the maintainer said
"Let's revisit it in a few weeks.". That's not the same as "OK when
stage1 reopens."
Hi!
On Sat, May 09, 2020 at 01:15:44PM -0400, David Edelsohn wrote:
> Okay with those changes, plus any issues noticed by Segher.
The only thing I can add is, I hope Bill's builtin work will make it
unnecessary to also define QUINARY and SENARY macros (yes I looked it
up), before we need those
Richard Biener writes:
> On Mon, 11 May 2020, Alexander Monakov wrote:
>
>> On Mon, 11 May 2020, Richard Sandiford wrote:
>>
>> > Like you say, the idea is that since the operation is commutative and
>> > is the same in both vector and scalar form, there's no reason to require
>> > any
On Mon, 11 May 2020, Alexander Monakov wrote:
> On Mon, 11 May 2020, Richard Sandiford wrote:
>
> > Like you say, the idea is that since the operation is commutative and
> > is the same in both vector and scalar form, there's no reason to require
> > any -ffast-math flags.
>
> Note that PR88540
On 10/05/20 23:03 +0200, François Dumont via Libstdc++ wrote:
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
Hi!
On Sat, May 09, 2020 at 12:05:08PM -0500, Bill Schmidt wrote:
> From: Carl Love
>
> Add support for xxgenpcv[dw]m, along with individual and overloaded
> built-in functions for access.
> (xxgenpcvm_): New insn.
> (xxgenpcvm): New expansion.
Eww. Let's please use or not use
- The testcase uses the -fgnu-tm option but does not ensure that support
is enabled. This patch adds the test to the testcase.
* gcc/testsuite/g++.dg/ipa/pr94856.C: Require fgnu-tm.
---
gcc/testsuite/ChangeLog| 4
gcc/testsuite/g++.dg/ipa/pr94856.C | 1 +
2 files
On Mon, 11 May 2020, Richard Sandiford wrote:
> Like you say, the idea is that since the operation is commutative and
> is the same in both vector and scalar form, there's no reason to require
> any -ffast-math flags.
Note that PR88540 that Richard is referencing uses open-coded x < y ? x : y
Richard Biener writes:
> 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 instructions semantics match C expression x
Now with missing testcase.
On Mon, May 11, 2020 at 11:20 AM Uros Bizjak wrote:
>
> Enable V2SFmode vectorization and vectorize V2SFmode PLUS,
> MINUS, MULT, MIN and MAX operations using XMM registers.
>
> To avoid unwanted secondary effects (e.g. exceptions), load values
> to XMM registers using
Enable V2SFmode vectorization and vectorize V2SFmode PLUS,
MINUS, MULT, MIN and MAX operations using XMM registers.
To avoid unwanted secondary effects (e.g. exceptions), load values
to XMM registers using MOVQ that clears high bits of the XMM
register outside V2SFmode.
The compiler now
On Mon, 11 May 2020, luoxhu wrote:
> 在 2020-05-06 20:09，Richard Biener 写道：
> > On Thu, 30 Apr 2020, luoxhu wrote:
> >
> >> Update the patch with overflow check. Bootstrap and regression tested PASS
> >> on Power8-LE.
> >>
> >>
> >> Use determine_value_range to get value range info for fold
在 2020-05-06 20:09，Richard Biener 写道：
On Thu, 30 Apr 2020, luoxhu wrote:
Update the patch with overflow check. Bootstrap and regression tested
PASS on Power8-LE.
Use determine_value_range to get value range info for fold convert
expressions
with internal operation
On 08/05/20 17:05 +0200, Ulrich Drepper via Libstdc++ wrote:
This is not yet implemented. Here is a patch.
2020-05-08 Ulrich Drepper
* include/bits/atomic_base.h (atomic_flag): Implement test
memeber function.
* include/std/version: Define __cpp_lib_atomic_flag_test.
*
Hi.
I'm going to install the typo fix to both master and gcc-10 branch.
Martin
gcc/ChangeLog:
2020-05-11 Martin Liska
PR c/95040
* common.opt: Fix typo in option description.
---
gcc/common.opt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
73 matches
Mail list logo
