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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106726
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2022-08-24
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100736
--- Comment #5 from Peter Bergner ---
(In reply to Segher Boessenkool from comment #3)
> Send patches to gcc-patches@, please. Or is there a question? Ask that
> question then, please :-)
Segher, do you have an answer for Hao Chen's question
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106418
Peter Bergner changed:
What|Removed |Added
CC||bergner at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106727
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322
--- Comment #49 from Kewen Lin ---
Hi Richi,
One thing I'm not sure about is that if we want to backport this to gcc-11 and
gcc-10? Although the failure got exposed by .MULH pattern recog which is only
in gcc-12, IMHO the underlying issue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106727
Bug ID: 106727
Summary: Missed fold / canonicalization for checking if a
number is a power of 2
Product: gcc
Version: 12.1.1
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103353
Kewen Lin changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103353
--- Comment #11 from CVS Commits ---
The releases/gcc-10 branch has been updated by Kewen Lin :
https://gcc.gnu.org/g:501fba663052b0b4a1eb6a42c32b74c254cbedbc
commit r10-10959-g501fba663052b0b4a1eb6a42c32b74c254cbedbc
Author: Kewen Lin
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103353
--- Comment #10 from CVS Commits ---
The releases/gcc-11 branch has been updated by Kewen Lin :
https://gcc.gnu.org/g:3fc2a9dba4c06115daaa8a39acffadbc33b51152
commit r11-10220-g3fc2a9dba4c06115daaa8a39acffadbc33b51152
Author: Kewen.Lin
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322
--- Comment #48 from CVS Commits ---
The releases/gcc-12 branch has been updated by Kewen Lin :
https://gcc.gnu.org/g:9f532fec01d6651cc3cc136073f044a7953d8560
commit r12-8710-g9f532fec01d6651cc3cc136073f044a7953d8560
Author: Kewen Lin
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103353
--- Comment #9 from CVS Commits ---
The releases/gcc-12 branch has been updated by Kewen Lin :
https://gcc.gnu.org/g:d0d72e0b1ebbac487d70281a56799bf547034ec1
commit r12-8709-gd0d72e0b1ebbac487d70281a56799bf547034ec1
Author: Kewen.Lin
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106516
--- Comment #7 from Kewen Lin ---
(In reply to Peter Bergner from comment #6)
> (In reply to Kewen Lin from comment #5)
> > Created attachment 53492 [details]
> > Adjust pr104992.c with vect_int_mod
> >
> > > So it sounds like we want a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100295
Andrew Pinski changed:
What|Removed |Added
CC||janezz55 at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106689
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106721
--- Comment #4 from Hongtao.liu ---
(In reply to Jakub Jelinek from comment #3)
> Created attachment 53494 [details]
> gcc13-pr106721.patch
>
> Untested fix. This fixes all <[a-zA-Z] occurrences in tmp-mddump.md (except
> those in comments).
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:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69410
--- Comment #8 from Zopolis0 ---
Created attachment 53498
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53498=edit
Possible patch
This is a more production-ready version of the patch I used, gcc completes a
full no bootstrap build with
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106509
--- Comment #4 from GARY.WHITE at ColoState dot edu ---
Somewhat resolved -- does not happen with UCRT, only with MSVCRT.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103694
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103694
--- Comment #6 from anlauf at gcc dot gnu.org ---
Potential fix that regtests cleanly:
diff --git a/gcc/fortran/simplify.cc b/gcc/fortran/simplify.cc
index f992c31e5d7..3d2a68fa36a 100644
--- a/gcc/fortran/simplify.cc
+++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105678
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105678
--- Comment #10 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:c9c0684ad3092e5aa50453903c09959cb2e83fc7
commit r12-8707-gc9c0684ad3092e5aa50453903c09959cb2e83fc7
Author: Jonathan
king-yes-rtl-df-extra-aarch64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.0.0 20220823 (experimental) (GCC)
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106725
Bug ID: 106725
Summary: LTO semantics for __attribute__((leaf))
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106516
--- Comment #6 from Peter Bergner ---
(In reply to Kewen Lin from comment #5)
> Created attachment 53492 [details]
> Adjust pr104992.c with vect_int_mod
>
> > So it sounds like we want a generic target supports test that is true on
> > targets
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:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106669
--- Comment #2 from Jonathan Wakely ---
Please open an LWG issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106676
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106724
--- Comment #2 from Andrew Pinski ---
Well branch cost should be more tuned too.
Here is an example where BRANCH_COST=4 is needed to get one branch:
```
int g(void);
int f(int a, int b, int c, int d)
{
if (a > b && c > d)
return g();
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106589
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |ASSIGNED
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106589
--- Comment #5 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:e85bb1881e57e53306ede2a15f30d06480d69886
commit r13-2157-ge85bb1881e57e53306ede2a15f30d06480d69886
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106724
--- Comment #1 from Andrew Pinski ---
Note clang/LLVM produces the branch-less version also.
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106719
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |10.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106722
--- Comment #6 from Andrew Pinski ---
Note I think for RISCV, logical-op-non-short-circuit seems like it should
change to 1, I filed PR 106724 for that with an example even.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106724
Bug ID: 106724
Summary: logical-op-non-short-circuit maybe should be 1
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
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,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106714
--- Comment #1 from CVS Commits ---
The master branch has been updated by H.J. Lu :
https://gcc.gnu.org/g:aeb9b58225916bc84a0cd02c6fc77bbb92167e53
commit r13-2156-gaeb9b58225916bc84a0cd02c6fc77bbb92167e53
Author: H.J. Lu
Date: Thu Aug 18
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358
--- Comment #13 from Jeffrey Walton ---
Add a mee too. When using sanitizers, like -fsanitize=undefined, the compiler
driver is not adding the necessary libraries to link the program. Ugh...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106692
Tobias Burnus changed:
What|Removed |Added
CC||burnus at gcc dot gnu.org
--- Comment
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
Hello,
On Tue, 23 Aug 2022, Florian Weimer via Gcc wrote:
> We currently have a latent bug in glibc where C++ constructor calls can
> fail if they have static or thread storage duration and a non-trivial
> destructor. The reason is that __cxa_atexit (and
> __cxa_thread_atexit_impl) may have to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106718
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106722
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106722
--- Comment #4 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:baa3ffb19c54fa334ac2884f6acb5d31aa79ac32
commit r13-2155-gbaa3ffb19c54fa334ac2884f6acb5d31aa79ac32
Author: Richard Biener
Date:
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106723
Bug ID: 106723
Summary: Unreplaced mode/code attributes in aarch64/arm
backends
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
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.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106099
--- Comment #14 from Jakub Jelinek ---
Created attachment 53496
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53496=edit
gcc13-pr106099.patch
Untested fix. There are 2 issues. One was that tree-cfg.cc was emitting
__builtin_trap
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106722
--- Comment #3 from Richard Biener ---
Created attachment 53495
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53495=edit
preprocessed source, from riscv
This is the original preprocessed testcase from riscv64-linux. Reproduces
with a
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
Hi Florian,
What would be the most ELF-flavored way to implement this? After the
final link, I expect that the count (or counts, we need a separate
counter for thread-local storage) would show up under a new dynamic tag
in the dynamic segment. This is actually a very good fit because older
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
> +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106713
Martin Liška changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
We currently have a latent bug in glibc where C++ constructor calls can
fail if they have static or thread storage duration and a non-trivial
destructor. The reason is that __cxa_atexit (and
__cxa_thread_atexit_impl) may have to allocate memory. We can avoid
that if we know how many such static
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106720
Jürgen Reuter changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106719
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2022-08-23
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106566
--- Comment #5 from CVS Commits ---
The releases/gcc-12 branch has been updated by Tobias Burnus
:
https://gcc.gnu.org/g:50b7cf395656ccd32d4d5d8e0e338135d28f52f6
commit r12-8704-g50b7cf395656ccd32d4d5d8e0e338135d28f52f6
Author: Tobias Burnus
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106548
--- Comment #5 from CVS Commits ---
The releases/gcc-12 branch has been updated by Tobias Burnus
:
https://gcc.gnu.org/g:2413eed009878c347c65950c649c0da59e759238
commit r12-8703-g2413eed009878c347c65950c649c0da59e759238
Author: Tobias Burnus
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106721
--- Comment #3 from Jakub Jelinek ---
Created attachment 53494
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53494=edit
gcc13-pr106721.patch
Untested fix. This fixes all <[a-zA-Z] occurrences in tmp-mddump.md (except
those in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106722
--- Comment #2 from Richard Biener ---
Note it's the dependence chain from def to use that is empty because of this
limit.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106722
--- Comment #1 from Richard Biener ---
The uninit code already handles this but it runs into its MAX_CHAIN_LEN path
discovery limit.
upping that by one fixes the reduced testcase, upping it to 8 (from 5) fixes
original preprocessed source.
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106721
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106722
Bug ID: 106722
Summary: bogus uninit warning in tree-vect-loop-manip.cc
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
1 - 100 of 128 matches
Mail list logo
