On Tue, 2022-08-02 at 11:10 +, YunQiang Su wrote:
> If we cannot get info from options and cpuinfo, we try to get from:
> 1. getauxval(AT_BASE_PLATFORM), introduced since Linux 5.7
> 2. _MIPS_ARCH from host compiler.
>
> This can fix the wrong loader usage on r5/r6 platform with
>
on 2022/8/24 13:11, HAO CHEN GUI wrote:
> Hi Segher,
>
> On 23/8/2022 下午 10:26, Segher Boessenkool wrote:
>> Hi!
>>
>> On Fri, Aug 19, 2022 at 10:35:54AM +0800, HAO CHEN GUI wrote:
>>> --- a/gcc/testsuite/gcc.target/powerpc/bfp/scalar-extract-exp-0.c
>>> +++
Hi Segher,
On 23/8/2022 下午 10:26, Segher Boessenkool wrote:
> Hi!
>
> On Fri, Aug 19, 2022 at 10:35:54AM +0800, HAO CHEN GUI wrote:
>> --- a/gcc/testsuite/gcc.target/powerpc/bfp/scalar-extract-exp-0.c
>> +++ b/gcc/testsuite/gcc.target/powerpc/bfp/scalar-extract-exp-0.c
>> @@ -1,7 +1,8 @@
>> /*
> Am 24.08.2022 um 01:54 schrieb Joseph Myers :
>
> When an object of decimal floating-point type is default-initialized,
> GCC is inconsistent about whether it is given the all-zero-bits
> representation (zero with the least quantum exponent) or whether it
> acts like a conversion of integer
YunQiang Su 于2022年8月2日周二 19:11写道：
>
> If we cannot get info from options and cpuinfo, we try to get from:
> 1. getauxval(AT_BASE_PLATFORM), introduced since Linux 5.7
> 2. _MIPS_ARCH from host compiler.
>
> This can fix the wrong loader usage on r5/r6 platform with
> -march=native.
>
Is it
Hi Segher, I'd like to resend and ping for this patch. Thanks.
From 23bffdacdf0eb1140c7a3571e6158797f4818d57 Mon Sep 17 00:00:00 2001
From: Xionghu Luo
Date: Thu, 4 Aug 2022 03:44:58 +
Subject: [PATCH v4] rs6000: Fix incorrect RTL for Power LE when removing the
UNSPECS [PR106069]
v4:
Since 256-bit vector integer comparison is under TARGET_AVX2,
and gimple folding for vblendvpd/vblendvps/vpblendvb relies on that.
Restrict gimple fold condition to TARGET_AVX2.
Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}.
Ok for trunk?
gcc/ChangeLog:
PR target/106704
I tried #define LOGICAL_OP_NON_SHORT_CIRCUIT 1 in RISC-V port. The warning is
still there.
Are you considering this
patch:https://gcc.gnu.org/pipermail/gcc-patches/2022-August/600120.html
to solve this issue ? Or you are trying another solution to fix this ?
juzhe.zh...@rivai.ai
From:
When an object of decimal floating-point type is default-initialized,
GCC is inconsistent about whether it is given the all-zero-bits
representation (zero with the least quantum exponent) or whether it
acts like a conversion of integer 0 to the DFP type (zero with quantum
exponent 0). In
On Tue, Aug 16, 2022 at 9:50 AM Lewis Hyatt wrote:
>
> On Wed, Jul 20, 2022 at 8:56 PM Lewis Hyatt wrote:
> >
> > Hello-
> >
> > May I please ping these two preprocessor patches?
> >
> > For PR103902:
> > https://gcc.gnu.org/pipermail/gcc-patches/2022-June/596704.html
> >
> > For PR55971:
> >
Hi!
On Mon, Jul 25, 2022 at 09:29:22PM +0800, Jiufu Guo wrote:
> When checking eq/neq with a constant which has only 16bits, it can be
> optimized to check the rotated data. By this, the constant building
> is optimized.
"ne", not "neq".
> gcc/ChangeLog:
>
> *
On 8/22/22 02:53, Jakub Jelinek wrote:
Hi!
On Thu, Aug 18, 2022 at 11:02:44PM +, Joseph Myers wrote:
ISO C2x standardizes the existing #warning extension. Arrange
accordingly for it not to be diagnosed with -std=c2x -pedantic, but to
be diagnosed with -Wc11-c2x-compat.
And here is the
On 8/22/22 17:10, Marek Polacek wrote:
This patch fixes a pretty stoopid thinko. When I added code to warn
about pessimizing std::move in initializations like
T t{std::move(T())};
I also added code to unwrap the expression from { }. But when we have
return {std::move(t)};
we cannot
On 8/23/22 09:39, Marek Polacek wrote:
On Sat, Aug 20, 2022 at 05:31:52PM -0400, Jason Merrill wrote:
On 8/19/22 15:34, Marek Polacek wrote:
On Thu, Aug 18, 2022 at 08:33:47PM -0400, Jason Merrill wrote:
On 8/18/22 13:19, Marek Polacek wrote:
On Mon, Aug 15, 2022 at 03:54:05PM -0400, Jason
Please do not send new patches as replies to other patches.
On Thu, Aug 18, 2022 at 05:48:29PM -0400, Michael Meissner wrote:
> mprove converting between 128-bit modes that use the same format.
You are missing some characters? But this is an edited version of the
subject anyway. Just don't do
I am checking in this as an obvious fix.
H.J.
---
Since XMM BF16 tests only require SSE2, replace vmovdqu with movdqu in
BF16 XMM ABI tests to support SSE2 machines without AVX.
Tested on x86-64 machines with and without AVX.
* gcc.target/x86_64/abi/bf16/asm-support.S: Replace vmovdqu
Dear all,
the simplification of the size of an array with a bad decl
should not be successful. Improve the error recovery for
such a situation.
The patch is nearly obvious. I therefore intend to commit
it in the next few days unless someone comes up with a
better solution.
Regtested on
On Tue, Aug 23, 2022 at 06:23:23PM +, Joseph Myers wrote:
> On Tue, 23 Aug 2022, Jakub Jelinek via Gcc-patches wrote:
>
> > On Tue, Aug 16, 2022 at 11:41:06AM +, Richard Biener wrote:
> > > I'm OK with the rest of the patch if Joseph doesn't have comments
> > > on the actual issignaling
On Tue, 23 Aug 2022, Jakub Jelinek via Gcc-patches wrote:
> On Tue, Aug 16, 2022 at 11:41:06AM +, Richard Biener wrote:
> > I'm OK with the rest of the patch if Joseph doesn't have comments
> > on the actual issignaling lowerings (which I didn't review for
> > correctness due to lack of
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-12.2.0.de.po', has
On Sat, Aug 20, 2022 at 05:31:52PM -0400, Jason Merrill wrote:
> On 8/19/22 15:34, Marek Polacek wrote:
> > On Thu, Aug 18, 2022 at 08:33:47PM -0400, Jason Merrill wrote:
> > > On 8/18/22 13:19, Marek Polacek wrote:
> > > > On Mon, Aug 15, 2022 at 03:54:05PM -0400, Jason Merrill wrote:
> > > > >
On Mon, 22 Aug 2022 at 19:15, Will Hawkins wrote:
>
> Until now operator+(char*, string) and operator+(string, char*) had
> different performance characteristics. The former required a single
> memory allocation and the latter required two. This patch makes the
> performance equal.
If you don't
The crc32q instruction takes 64-bit operands, but ignores high 32 bits
of the destination operand, and zero-extends the result from 32 bits.
Let's model this in the RTL pattern to avoid zero-extension when the
_mm_crc32_u64 intrinsic is used with a 32-bit type.
PR target/106453
From: Patrick O'Neill
RISC-V has no support for subword atomic operations; code currently
generates libatomic library calls.
This patch changes the default behavior to inline subword atomic calls
(using the same logic as the existing library call).
Behavior can be specified using the
Hello, gentle maintainer.
This is a message from the Translation Project robot. (If you have
any questions, send them to .)
A new POT file for textual domain 'gcc' has been made available
to the language teams for translation. It is archived as:
Tested powerpc64le-linux, pushed to trunk. Backport to gcc-12 needed.
-- >8 --
The optimization for the common case of std::visit forgot to handle the
edge case of passing zero variants to a non-void visitor and converting
the result to void.
libstdc++-v3/ChangeLog:
PR libstdc++/106589
On Tue, Aug 23, 2022 at 2:16 PM Richard Biener wrote:
>
> The following reverts a hunk from r8-5789-g11ef0b22d68cd1 that
> made compute_control_dep_chain start from function entry rather
> than the immediate dominator of the source block of the edge with
> the undefined value on the PHI node.
Ping^3.
On Fri, 5 Aug 2022, Alexander Monakov wrote:
> Ping^2.
>
> On Wed, 20 Jul 2022, Alexander Monakov wrote:
>
> >
> > Ping.
> >
> > On Thu, 7 Jul 2022, Alexander Monakov via Gcc-patches wrote:
> >
> > > From: Artem Klimov
> > >
> > > Fix PR99619, which asks to optimize TLS model
On Tue, 23 Aug 2022, Jonathan Wakely wrote:
> On Tue, 23 Aug 2022 at 02:36, Patrick Palka via Libstdc++
> wrote:
> > --- a/libstdc++-v3/include/bits/stl_pair.h
> > +++ b/libstdc++-v3/include/bits/stl_pair.h
> > @@ -212,6 +212,19 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
> > swap(second,
On Tue, 23 Aug 2022 at 14:44, Patrick Palka wrote:
>
> On Tue, 23 Aug 2022, Jonathan Wakely wrote:
>
> > On Tue, 23 Aug 2022 at 02:35, Patrick Palka via Libstdc++
> > wrote:
> > >
> > > P2321R2 adds new conditionally explicit constructors to std::tuple which
> > > we'll concisely implement in a
Another attempt to make kernel module happy.
One remaining issue: the patch cannot diagnostic some insane thing like
int x __attribute__((model("normal")));
int x __attribute__((model("extreme")));
It seems incredibly difficult to diagnose such thing: I can't figure out
any solution w/o
On Fri, Aug 19, 2022 at 10:40:10AM +0800, Kewen.Lin wrote:
> Since you proposed to update the documentation, I'm thinking if we can
> reconsider Fangrui's proposal in the PR which Alan seconded: Put preceding
> nops before GEP and succeeding nops after LEP. Previously I had the concern
> that the
Hi!
On Fri, Aug 19, 2022 at 10:35:54AM +0800, HAO CHEN GUI wrote:
> --- a/gcc/testsuite/gcc.target/powerpc/bfp/scalar-extract-exp-0.c
> +++ b/gcc/testsuite/gcc.target/powerpc/bfp/scalar-extract-exp-0.c
> @@ -1,7 +1,8 @@
> /* { dg-do compile { target { powerpc*-*-* } } } */
> -/* {
On Tue, 23 Aug 2022, Jonathan Wakely wrote:
> On Tue, 23 Aug 2022 at 02:35, Patrick Palka via Libstdc++
> wrote:
> >
> > P2321R2 adds new conditionally explicit constructors to std::tuple which
> > we'll concisely implement in a subsequent patch using explicit(bool), like
> > in our C++20
Hi!
On Tue, Aug 23, 2022 at 07:55:22AM -0500, Peter Bergner wrote:
> It looks good to me, but I cannot approve it.
Same here (both statements).
> That said, you're missing
> a ChangeLog entry for your new helper function. The ChangeLog mentions
> what changed, not why it changed.
And that is
The following applies similar measures as r13-2133-ge66cf626c72d58
to the computation of the use predicate when the path from PHI def
to use is too long and we run into compute_control_dep_chain limits.
It also moves the preprocessor define limits internal.
This resolves the reduced testcase but
On 8/23/22 6:49 AM, Surya Kumari Jangala wrote:
> sched1: Fix -fcompare-debug issue in schedule_region [PR105586]
>
> In schedule_region(), a basic block that does not contain any real insns
> is not scheduled and the dfa state at the entry of the bb is not copied
> to the fallthru basic block.
On Tue, Aug 23, 2022 at 12:12 PM Aldy Hernandez wrote:
>
> It looks like we're missing a newline for cases where we don't print
> anything.
>
> OK?
OK
> gcc/ChangeLog:
>
> * tree-ssa-threadbackward.cc (possibly_profitable_path_p): Always
> add newline.
>
I've reduced the following which doesn't seem covered in a good enough
way in the testsuite.
Pushed.
* gcc.dg/uninit-pred-10.c: New testcase.
---
gcc/testsuite/gcc.dg/uninit-pred-10.c | 36 +++
1 file changed, 36 insertions(+)
create mode 100644
The following reverts a hunk from r8-5789-g11ef0b22d68cd1 that
made compute_control_dep_chain start from function entry rather
than the immediate dominator of the source block of the edge with
the undefined value on the PHI node. Reverting at that point
does not reveal any testsuite FAIL, in
On 8/22/22 13:39, Paul Hollinsky wrote:
On Mon, Aug 22, 2022 at 09:19:29AM -0400, Nathan Sidwell wrote:
On 8/19/22 16:27, Paul Hollinsky wrote:
Hi all,
Would love some feedback on this patch!
Thanks,
Paul
On Mon, Aug 01, 2022 at 05:18:40AM +, Paul Hollinsky wrote:
Rather than
On Tue, 23 Aug 2022 at 02:36, Patrick Palka via Libstdc++
wrote:
> --- a/libstdc++-v3/include/bits/stl_pair.h
> +++ b/libstdc++-v3/include/bits/stl_pair.h
> @@ -212,6 +212,19 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
> swap(second, __p.second);
>}
>
> +#if __cplusplus > 202002L
> +
sched1: Fix -fcompare-debug issue in schedule_region [PR105586]
In schedule_region(), a basic block that does not contain any real insns
is not scheduled and the dfa state at the entry of the bb is not copied
to the fallthru basic block. However a DEBUG insn is treated as a real
insn, and if a bb
The current implementation of frange is just a type with some bits to
represent NAN and INF. We can do better and represent endpoints to
ultimately solve longstanding PRs such as PR24021. This patch adds
these endpoints. In follow-up patches I will add support for
relational operators using
And the same for depend-6.f90, which was obviously copied from depend-4.f90.
Committed as
https://gcc.gnu.org/r13-2152-gf05e3b2c63f3307ba405900f1a80c25b2e87b0a3
On 23.08.22 12:34, Tobias Burnus wrote:
Not really crucial as it is a compile-time test, but there was an off-by-one
typo:
!$omp
Not really crucial as it is a compile-time test, but there was an off-by-one
typo:
!$omp depobj(elem(5)) depend(in: daaa(2))
!$omp depobj(elem(6)) depend(in: daap(2))
- !$omp depobj(elem(6)) depend(in: doaa(2))
+ !$omp depobj(elem(7)) depend(in: doaa(2))
!$omp depobj(elem(8)) depend(in:
For the frange implementation with endpoints I'm about to contribute,
we need to set REAL_VALUE_TYPEs with negative infinity. The support
is already there in real.cc, but it is awkward to get at. One could
call real_inf() and then negate the value, but I've added the ability
to pass the sign
Like the integer version, when op1 == op2 is known to be true the
ranges are also equal.
gcc/ChangeLog:
* range-op-float.cc (foperator_equal::op1_range): Set range to
range of op2.
---
gcc/range-op-float.cc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
It looks like we're missing a newline for cases where we don't print
anything.
OK?
gcc/ChangeLog:
* tree-ssa-threadbackward.cc (possibly_profitable_path_p): Always
add newline.
(profitable_path_p): Same.
---
gcc/tree-ssa-threadbackward.cc | 10 +-
1 file
On Mon, Aug 22, 2022 at 8:15 AM Richard Biener via Gcc-patches
wrote:
>
> On Sat, 20 Aug 2022, Andrew Pinski wrote:
>
> > On Sat, Aug 20, 2022 at 3:34 PM Andreas Schwab
> > wrote:
> > >
> > > This breaks bootstrap:
> > >
> > > ../../gcc/tree-vect-loop-manip.cc: In function 'void
> > >
On Tue, 23 Aug 2022 at 02:35, Patrick Palka via Libstdc++
wrote:
>
> P2321R2 adds new conditionally explicit constructors to std::tuple which
> we'll concisely implement in a subsequent patch using explicit(bool), like
> in our C++20 std::pair implementation. But before we can do that, this
>
On Tue, Aug 16, 2022 at 11:41:06AM +, Richard Biener wrote:
> I'm OK with the rest of the patch if Joseph doesn't have comments
> on the actual issignaling lowerings (which I didn't review for
> correctness due to lack of knowledge).
I'd like to ping this patch.
Patch:
On Thu, Aug 18, 2022 at 8:48 AM Kong, Lingling via Gcc-patches
wrote:
>
> Hi,
>
> This patch is for pr105735/pr101991. It will enable below optimization:
> {
> - long unsigned int bit;
> -
> - [local count: 32534376]:
> -
> - [local count: 1041207449]:
> - # tmp_10 = PHI
> - # bit_12 =
On Tue, 23 Aug 2022, juzhe.zh...@rivai.ai wrote:
> From: zhongjuzhe
OK.
> gcc/ChangeLog:
>
> * tree-vect-loop-manip.cc (vect_gen_vector_loop_niters): Simply
> initialize const_vf to 0.
>
> ---
> gcc/tree-vect-loop-manip.cc | 5 +++--
> 1 file changed, 3 insertions(+), 2
From: zhongjuzhe
gcc/ChangeLog:
* tree-vect-loop-manip.cc (vect_gen_vector_loop_niters): Simply
initialize const_vf to 0.
---
gcc/tree-vect-loop-manip.cc | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/gcc/tree-vect-loop-manip.cc b/gcc/tree-vect-loop-manip.cc
On Mon, 22 Aug 2022, Marek Polacek wrote:
> On Mon, Aug 22, 2022 at 10:16:23AM -0700, Andrew Pinski wrote:
> > On Mon, Aug 22, 2022 at 9:58 AM Marek Polacek via Gcc-patches
> > wrote:
> > >
> > > r11-4123 came without a test but I happened upon a nice test case that
> > > got fixed by that
56 matches
Mail list logo
