From: Mihailo Stojanovic
Hi all,
Currently, SF->SI and DF->DI conversions on Aarch64 with the "nosimd"
flag provided sometimes cause the emitting of a vector variant of the
fcvtz[su] instruction (e.g. fcvtzu s0, s0).
This modifies the corresponding pattern to only select the vector
variant of t
The previous change to this testcase missed the fact that the data may
be accessed via an anchor, depending on the optimization level,
leading to false failures.
This patch restricts matching to upper16:lower16 followed by
non-spaces, followed by +4 (in f4) or +320 (in f5).
Using '.*' instead of
Hi!
On 2021-03-26T16:22:20+0100, Jakub Jelinek wrote:
> On Fri, Mar 26, 2021 at 04:19:56PM +0100, Tobias Burnus wrote:
>> On 26.03.21 15:46, Jakub Jelinek via Gcc-patches wrote:
>> > On Fri, Mar 26, 2021 at 03:42:22PM +0100, Tobias Burnus wrote:
>> > > How about the following patch? It moves the
Hi Tobias,
An earlier version of the patch, without the exclusion of unlimited
polymorphic expressions caused several regressions. However, omitting the
exclusion now causes no regressions. I forgot to go back to this wrinkle.
I have included your testcases with appropriate attribution and pushed
On Fri, Mar 19, 2021 at 01:04:19PM +, Richard Sandiford via Gcc-patches
wrote:
> > As the following testcase shows, we emit a -Wpsabi note about argument
> > passing change since GCC 9, but in reality the ABI didn't change.
> > The alignment is 8 bits in GCC < 9 and 32 bits in GCC >= 9 and
> >
On Fri, 26 Mar 2021, Richard Sandiford wrote:
> Richard Biener writes:
> > On Wed, 24 Mar 2021, Stam Markianos-Wright wrote:
> >
> >> Hi all,
> >>
> >> This patch resolves bug:
> >>
> >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96974
> >>
> >> This is achieved by forcing a re-calculation o
On Sat, 27 Mar 2021, Jakub Jelinek wrote:
> Hi!
>
> extract_muldiv{,_1} is apparently only prepared to handle scalar integer
> operations, the callers ensure it by only calling it if the divisor or
> one of the multiplicands is INTEGER_CST and because neither multiplication
> nor division nor mod
Hi all,
This patch fixes the RTL representation of the move_lo_quad patterns to use
aarch64_simd_or_scalar_imm_zero
for the zero part rather than a vec_duplicate of zero or a const_int 0.
The expander that generates them is also adjusted so that we use and match the
correct const_vector forms th
On Mon, Mar 29, 2021 at 10:41:17AM +, Kyrylo Tkachov wrote:
> Hi all,
>
> This patch fixes the RTL representation of the move_lo_quad patterns to use
> aarch64_simd_or_scalar_imm_zero
> for the zero part rather than a vec_duplicate of zero or a const_int 0.
> The expander that generates them
> -Original Message-
> From: Jakub Jelinek
> Sent: 29 March 2021 11:45
> To: Kyrylo Tkachov
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] aarch64: PR target/99037 Fix RTL represntation in
> move_lo_quad patterns
>
> On Mon, Mar 29, 2021 at 10:41:17AM +, Kyrylo Tkachov wrote:
This avoids asserting anything on the SLP_TREE_REPRESENTATIVE of
an SLP permute node (which shouldn't be there).
Bootstrapped / tested on x86_64-unknown-linux-gnu, pushed.
2021-03-29 Richard Biener
PR tree-optimization/99807
* tree-vect-slp.c (vect_slp_analyze_node_operations_
cpplib-11.1-b20210207.sr.po.gz
Description: Binary data
The Translation Project robot, in the
name of your translation coordinator.
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'cpplib' has been submitted
by the Serbian team of translators. The file is available at:
https://translationproject.org/latest/cpplib/sr.po
(This file, 'cpplib-11.1-b202102
The vectorizer has a very different effect with -mabi=ilp32, and
doesn't emit the expecte diagnostic, so this patch expects it only
under lp64.
2021-03-29 Christophe Lyon
gcc/testsuite/
PR target/96974
* g++.target/aarch64/sve/pr96974.C: Expect SLP diagnostic only
On 28/03/21 22:23 +0100, Jonathan Wakely via Libstdc++ wrote:
On Sun, 28 Mar 2021, 22:20 Gerald Pfeifer, wrote:
Hi folks,
I noticed http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html
has a link to https://github.com/llvm/llvm-project/tree/master/pstl
which does not exist any more.
Wo
Similarly to other recently-added autovectorization patterns, mult has
been erroneously enabled for iwmmxt. However, V4HI and V2SI modes are
supported, so we make an exception for them.
The new testcase is derived from gcc.dg/ubsan/pr79904.c, with
additional modes added.
I kept dg-do compile beca
On Mon, Mar 22, 2021 at 4:57 PM H.J. Lu wrote:
>
> On Mon, Mar 22, 2021 at 7:10 AM Jan Hubicka wrote:
> >
> > >
> > > gcc/
> > >
> > > * config/i386/i386-expand.c (expand_set_or_cpymem_via_rep):
> > > For TARGET_PREFER_KNOWN_REP_MOVSB_STOSB, don't convert QImode
> > > to SImode.
Hi all,
as preremark I want to note that the testcase class_assign_4.f90
was added for PR83118/PR96012 (fixes problems in handling class objects, Dec
18, 2020)
and got revised for PR99124 (class defined operators, Feb 23, 2021).
Both patches were then also applied to GCC 9 and 10.
On 26.03.21 1
Hi!
On Sat, Mar 27, 2021 at 04:07:18PM +0100, Florian Weimer wrote:
> * Michael Meissner via Gcc-patches:
> > On Wed, Feb 24, 2021 at 11:12:54PM +, Joseph Myers wrote:
> >> This change appears to have broken builds for powerpc in a configuration
> >> that bootstraps a cross toolchain starting
On Sun, 28 Mar 2021, Patrick Palka wrote:
> This rewrites our range adaptor implementation for more comprehensible
> error messages, improved SFINAE behavior and conformance to P2281.
>
> The diagnostic improvements mostly comes from using appropriately named
> functors instead of lambdas in the
Hi!
aarch64 currently doesn't support declare simd where the return value and
arguments
have different sizes and warns about that case. This change adds a dg-warning
for that case like various other tests have already.
Committed to trunk.
2021-03-29 Jakub Jelinek
PR fortran/93660
Hi!
I'd like to ping following patch:
> https://gcc.gnu.org/pipermail/gcc-patches/2021-March/59.html
> PR99490 dwarf2out -gsplit-dwarf ranges fixes
Thanks
Jakub
On Sat, Mar 27, 2021 at 04:07:18PM +0100, Florian Weimer wrote:
> This issue is still present.
>
> What about the patch below?
>
> Thanks,
> Florian
>
> rs6000: Do not build _Float128/Decimal routines with --disable-decimal-float
>
> Fixes commit 781183595acba67a37c66f59a0c1d9b5fee7e248 ("Add c
Hi,
this patch fixes if (deref) that is reversed in merge_call_lhs_flags.
I re-run stats on cc1plus that seems comparable to last run.
Bootstrapped/regtested x86_64-linux.
Alias oracle query stats:
refs_may_alias_p: 66575703 disambiguations
On March 29, 2021 8:11:51 PM GMT+02:00, Jan Hubicka wrote:
>Hi,
>this patch fixes if (deref) that is reversed in merge_call_lhs_flags.
>I re-run stats on cc1plus that seems comparable to last run.
>
>Bootstrapped/regtested x86_64-linux.
>
>Alias oracle query stats:
Hi Iain, could you add a note about this change to the
gcc-11/changes.html page? There are probably some people who would be
interested in this who could use a note about it. Thanks
On Tue, Dec 22, 2020 at 3:53 PM Jason Merrill via Gcc-patches
wrote:
>
> On 12/22/20 3:39 PM, Iain Sandoe wrote:
>
While we're modifying elements_view, this also implements the one-line
resolution of LWG 3492.
libstdc++-v3/ChangeLog:
* include/std/ranges (__detail::__returnable_element): New
concept.
(elements_view): Use this concept in its constraints. Add
missing private acc
The header currently copies some simple algorithms from
, which was originally done in order to avoid a
circular dependency with the header. This is no longer an issue since
the latter header now includes instead of all of
.
This means we could now just include and remove the
copied algorithms
libstdc++-v3/ChangeLog:
* include/std/ranges (__detail::find): Define.
(split_view::_OuterIter::operator++): Apply proposed resolution
of LWG 3505.
* testsuite/std/ranges/adaptors/split.cc (test10): New test.
---
libstdc++-v3/include/std/ranges | 28 +
On Mon, 29 Mar 2021, Patrick Palka wrote:
> The header currently copies some simple algorithms from
> , which was originally done in order to avoid a
> circular dependency with the header. This is no longer an issue since
> the latter header now includes instead of all of
> .
>
> This means we
> >gcc/testsuite/ChangeLog:
> >
> >2021-03-29 Jan Hubicka
> >
> > * gcc.c-torture/compile/pr99751.c: New test.
>
> Why compile torture?
Ah, sorry, it was meant to be execute. I will move the test.
Honza
> > >gcc/testsuite/ChangeLog:
> > >
> > >2021-03-29 Jan Hubicka
> > >
> > > * gcc.c-torture/compile/pr99751.c: New test.
> >
> > Why compile torture?
>
> Ah, sorry, it was meant to be execute. I will move the test.
It is now renamed as
https://gcc.gnu.org/g:7b6ca93b2d57ead352cd5cc3e10be4c33
On 25/03/21 4:29 pm, Jonathan Wakely wrote:
Oh, it's the same generate(sz) bug as you already found. But I've
found other bugs, e.g. with GLIBCXX_SEED_TEST_RNG=1908970375).
I think we should also add a check for non-empty containers to those
test functions, and ensure we don't try to erase from
This is a regression present on the mainline: the compiler fails to assign an
aggregate to a full-access component (i.e. Atomic or VFA) as a whole if the
type of the component is not full access itself.
Tested on x86-64/Linux, applied on the mainline.
2021-03-29 Eric Botcazou
PR ad
Hi!
On Fri, Mar 26, 2021 at 10:26:57PM -0500, Xionghu Luo wrote:
> 32bit and P7 VSX could also benefit a lot from the variable vec_insert
> implementation with shift/insert/shift back method.
> * config/rs6000/altivec.md (altivec_lvsl_reg): Change to ...
> (altivec_lvsl_reg_): ... thi
On Sat, Mar 27, 2021 at 04:07:18PM +0100, Florian Weimer wrote:
> This issue is still present.
>
> What about the patch below?
>
> Thanks,
> Florian
>
> rs6000: Do not build _Float128/Decimal routines with --disable-decimal-float
>
> Fixes commit 781183595acba67a37c66f59a0c1d9b5fee7e248 ("Add c
36 matches
Mail list logo
