https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472
--- Comment #32 from Eric Gallager ---
(In reply to matoro from comment #31)
> (In reply to Eric Gallager from comment #30)
> > (In reply to matoro from comment #26)
> > > We also had somebody report on IRC that they observed this on powerpc
The subject should be "Add tests for SX vector floating-point
instructions". The "support" has already been added.
Likewise for patches 5-9.
--
Xi Ruoyao
School of Aerospace Science and Technology, Xidian University
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86030
--- Comment #10 from John Soo ---
I'm also not sure
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=180ebb8a24d24fc5b105f2257d6216f6dfde62df
fixes the collect bug because collect uses collect_execute instead of the pex_*
exec functions.
gcc/testsuite/ChangeLog:
* gcc.target/loongarch/vector/lsx/lsx-vsadd-1.c: New test.
* gcc.target/loongarch/vector/lsx/lsx-vsadd-2.c: New test.
---
.../loongarch/vector/lsx/lsx-vsadd-1.c| 335 +
.../loongarch/vector/lsx/lsx-vsadd-2.c| 345
gcc/testsuite/ChangeLog:
* gcc.target/loongarch/vector/lsx/lsx-builtin.c: New test.
---
.../loongarch/vector/lsx/lsx-builtin.c| 5038 +
1 file changed, 5038 insertions(+)
create mode 100644 gcc/testsuite/gcc.target/loongarch/vector/lsx/lsx-builtin.c
diff --git
gcc/testsuite/ChangeLog:
* gcc.target/loongarch/strict-align.c: New test.
---
gcc/testsuite/gcc.target/loongarch/strict-align.c | 12
1 file changed, 12 insertions(+)
create mode 100644 gcc/testsuite/gcc.target/loongarch/strict-align.c
diff --git
gcc/testsuite/ChangeLog:
* gcc.target/loongarch/vector/loongarch-vector.exp: New test.
* gcc.target/loongarch/vector/simd_correctness_check.h: New test.
---
.../loongarch/vector/loongarch-vector.exp | 42 +++
.../loongarch/vector/simd_correctness_check.h | 54
v2 -> v3:
Standardize the code using the GNU format.
In order to better test the function of the vector instruction, the 128 and
256
bit test cases are further split according to the function of the instruction.
Xiaolong Chen (9):
LoongArch: Add tests of -mstrict-align option.
Ping this patch.
I think it's time to enable scalable vectorization by default and do the whole
regression every time (except vect.exp that we didn't enable yet)
Update current FAILs status:
Real FAILS (ICE and execution FAIL):
FAIL: gcc.dg/pr70252.c (internal compiler error: in
I found that it's more reasonable to use existing dominance analysis.
gcc/ChangeLog:
* config/riscv/riscv-vsetvl.cc
(pass_vsetvl::global_eliminate_vsetvl_insn): Use dominance analysis.
(pass_vsetvl::init): Ditto.
(pass_vsetvl::done): Ditto.
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111311
--- Comment #6 from CVS Commits ---
The trunk branch has been updated by Lehua Ding :
https://gcc.gnu.org/g:d05aac047e0643d5c32b706c4c3b12e13f35e19a
commit r14-3834-gd05aac047e0643d5c32b706c4c3b12e13f35e19a
Author: Juzhe-Zhong
Date: Mon
This patch add VLS modes VEC_PERM support which fix these following
FAILs in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111311:
FAIL: gcc.dg/tree-ssa/forwprop-40.c scan-tree-dump-times optimized
"BIT_FIELD_REF" 0
FAIL: gcc.dg/tree-ssa/forwprop-40.c scan-tree-dump-times optimized
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111324
--- Comment #3 from Jiu Fu Guo ---
A patch is posted:
https://gcc.gnu.org/pipermail/gcc-patches/2023-September/629534.html
Sure. Thanks kito.
juzhe.zh...@rivai.ai
From: Kito Cheng
Date: 2023-09-11 10:57
To: juzhe.zh...@rivai.ai
CC: gcc-patches; Kito.cheng
Subject: Re: Re: [PATCH] RISC-V: Add VLS modes VEC_PERM support[PR111311]
OK, but could you split this patch into two patches? pre-approved for both.
On Mon,
Committed.
gcc/ChangeLog:
* config/riscv/autovec-vls.md (*mov_vls): New pattern.
* config/riscv/vector-iterators.md: New iterator
---
gcc/config/riscv/autovec-vls.md | 8
gcc/config/riscv/vector-iterators.md | 15 +++
2 files changed, 23 insertions(+)
OK, but could you split this patch into two patches? pre-approved for both.
On Mon, Sep 11, 2023 at 10:36 AM juzhe.zh...@rivai.ai
wrote:
>
> >> Should we also add loads and stores as well?
> >> and just make sure this is also necessary for the fix and not sneaky,
> >> right?
>
> No, we don't
>> Should we also add loads and stores as well?
>> and just make sure this is also necessary for the fix and not sneaky, right?
No, we don't need loads/stores. Since this following handling codes:
(define_insn_and_split "*mov_lra"
[(set (match_operand:VLS_AVL_REG 0 "reg_or_mem_operand" "=vr,
On 9/10/23 20:18, Andrew Pinski via Gcc-patches wrote:
I noticed this while working on other MINMAX optimizations. It was
hard to find a simplified testcase though because it was dependent on
the ssa name versions. Adding the `:c` to cmp allows the pattern to
be match for the case where
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96708
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |11.0
--- Comment #5 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111346
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111346
--- Comment #5 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:190cf0ce8f4c141ac5b42d53b9ddeba367495333
commit r14-3832-g190cf0ce8f4c141ac5b42d53b9ddeba367495333
Author: Andrew Pinski
Date:
> diff --git a/gcc/config/riscv/autovec-vls.md b/gcc/config/riscv/autovec-vls.md
> index d208b418e5f..6f48f7d6232 100644
> --- a/gcc/config/riscv/autovec-vls.md
> +++ b/gcc/config/riscv/autovec-vls.md
> @@ -148,6 +148,14 @@
>[(set_attr "type" "vmov")
> (set_attr "mode" "")])
>
>
I noticed this while working on other MINMAX optimizations. It was
hard to find a simplified testcase though because it was dependent on
the ssa name versions. Adding the `:c` to cmp allows the pattern to
be match for the case where minmax as the first operand of the comparison
rather than the
On Thu, Sep 7, 2023 at 1:28 PM David Malcolm wrote:
> On Mon, 2023-09-04 at 22:13 -0400, Eric Feng wrote:
>
> > Hi Dave,
>
> Hi Eric, thanks for the patch.
>
> >
> > Recently I've been working on symbolic value support for the reference
> > count checker. I've attached a patch for it below; let
On Thu, Sep 7, 2023 at 1:28 PM David Malcolm wrote:
> On Mon, 2023-09-04 at 22:13 -0400, Eric Feng wrote:
>
> > Hi Dave,
>
> Hi Eric, thanks for the patch.
>
> >
> > Recently I've been working on symbolic value support for the reference
> > count checker. I've attached a patch for it below; let
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111306
--- Comment #8 from Hongtao.liu ---
Fixed in GCC14.1 GCC13.3 GCC12.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111335
Hongtao.liu changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111306
--- Comment #7 from CVS Commits ---
The releases/gcc-12 branch has been updated by hongtao Liu
:
https://gcc.gnu.org/g:82c1ff396e49b706d5baa11f4c884810f6350e95
commit r12-9852-g82c1ff396e49b706d5baa11f4c884810f6350e95
Author: liuhongt
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111335
--- Comment #3 from CVS Commits ---
The releases/gcc-12 branch has been updated by hongtao Liu
:
https://gcc.gnu.org/g:82c1ff396e49b706d5baa11f4c884810f6350e95
commit r12-9852-g82c1ff396e49b706d5baa11f4c884810f6350e95
Author: liuhongt
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111306
--- Comment #6 from CVS Commits ---
The releases/gcc-13 branch has been updated by hongtao Liu
:
https://gcc.gnu.org/g:162731529e4dd10970880c369471229735dc3e9b
commit r13-7789-g162731529e4dd10970880c369471229735dc3e9b
Author: liuhongt
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111335
--- Comment #2 from CVS Commits ---
The releases/gcc-13 branch has been updated by hongtao Liu
:
https://gcc.gnu.org/g:162731529e4dd10970880c369471229735dc3e9b
commit r13-7789-g162731529e4dd10970880c369471229735dc3e9b
Author: liuhongt
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111335
--- Comment #1 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:f197392a16ffb1327f1d12ff8ff05f9295e015cb
commit r14-3831-gf197392a16ffb1327f1d12ff8ff05f9295e015cb
Author: liuhongt
Date: Fri Sep
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111306
--- Comment #5 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:f197392a16ffb1327f1d12ff8ff05f9295e015cb
commit r14-3831-gf197392a16ffb1327f1d12ff8ff05f9295e015cb
Author: liuhongt
Date: Fri Sep
Here's the patch I've commited.
The patch also remove % for vfmaddcph.
gcc/ChangeLog:
PR target/111306
PR target/111335
* config/i386/sse.md (int_comm): New int_attr.
(fma__):
Remove % for Complex conjugate operations since they're not
commutative.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111348
--- Comment #2 from Andrew Pinski ---
Created attachment 55875
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55875=edit
testcase
Currentlyt test1 is able to optimize to MAX_EXPR , c> but not
test1_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111349
--- Comment #1 from Andrew Pinski ---
Created attachment 55874
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55874=edit
testcase
Currently test1_ is only able to optimize to `return a;` during fold.
test1 is caught via phiopt (minmax
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111346
--- Comment #4 from Andrew Pinski ---
Created attachment 55873
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55873=edit
Patch which I will commit after testing is finished
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111346
--- Comment #3 from Andrew Pinski ---
Actually here is a simplier testcase:
```
_Bool test1(int a, int b)
{
return ((a > b) ? a : b) >= a; // return 1;
}
_Bool test1_(int a, int b)
{
return a <= ((a > b) ? a : b); // return 1;
}
Committed, thanks Jeff.
Pan
-Original Message-
From: Gcc-patches On Behalf
Of Jeff Law via Gcc-patches
Sent: Sunday, September 10, 2023 9:38 PM
To: Juzhe-Zhong ; gcc-patches@gcc.gnu.org
Cc: kito.ch...@sifive.com; kito.ch...@gmail.com
Subject: Re: [PATCH] RISC-V: Expand fixed-vlmax/vls
Committed, thanks Jeff.
Pan
-Original Message-
From: Gcc-patches On Behalf
Of Jeff Law via Gcc-patches
Sent: Sunday, September 10, 2023 11:25 PM
To: Juzhe-Zhong ; gcc-patches@gcc.gnu.org
Cc: kito.ch...@sifive.com; kito.ch...@gmail.com
Subject: Re: [PATCH V2] RISC-V: Avoid unnecessary
Snapshot gcc-14-20230910 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20230910/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
> Hi!
>
> On 2023-09-07T19:00:49-0400, James Hu via Gcc wrote:
> > I noticed that adding incremental LTO was a GSoC project that was not
> > claimed this cycle (
> > https://summerofcode.withgoogle.com/programs/2023/organizations/gnu-compiler-collection-gcc).
> > I was curious about working on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111364
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111364
Bug ID: 111364
Summary: `MAX_EXPR <= a` is not optimized to `a >= b`
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111346
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86030
--- Comment #9 from John Soo ---
Would a patch for unix doing something similar to
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=180ebb8a24d24fc5b105f2257d6216f6dfde62df
be accepted? I am happy to start working on something like it but I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111363
Bug ID: 111363
Summary: internal compiler error when mistype type of
operator<=>
Product: gcc
Version: 9.4.0
Status: UNCONFIRMED
Severity: normal
Some targets like arm-eabi with newlib and default settings rely on
__sync_synchronize() to ensure synchronization. Newlib does not
implement it by default, to make users aware they have to take special
care.
This makes a few tests fail to link.
This patch requires the missing thread-fence
Some targets like arm-eabi with newlib and default settings rely on
__sync_synchronize() to ensure synchronization. Newlib does not
implement it by default, to make users aware they have to take special
care.
This makes a few tests fail to link.
This patch adds a new thread_fence effective
swap: Fix incorrect lane extraction by vec_extract() [PR106770]
In the routine rs6000_analyze_swaps(), special handling of swappable
instructions is done even if the webs that contain the swappable
instructions are not optimized, i.e., the webs do not contain any
permuting load/store instructions
Ping.
> > > On Thu, Aug 10, 2023 at 03:04:03PM +0200, Stefan Schulze Frielinghaus
> > > wrote:
> > > > In the former fix in commit 41ef5a34161356817807be3a2e51fbdbe575ae85 I
> > > > completely missed the fact that the normal form of a generated constant
> > > > for a
> > > > mode with fewer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102665
--- Comment #7 from Eric Gallager ---
Making some more progress on this:
https://github.com/gcc-mirror/gcc/compare/master...cooljeanius:gcc:me/PR102665
Some notes:
- There are a lot of these; I'm not quite sure how many to include in a single
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111331
Andrew Pinski changed:
What|Removed |Added
Summary|[11/12/13/14 Regression]|[11/12/13 Regression] Wrong
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111331
--- Comment #13 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:30e6ee074588bacefd2dfe745b188bb20c81fe5e
commit r14-3827-g30e6ee074588bacefd2dfe745b188bb20c81fe5e
Author: Andrew Pinski
Date:
On 9/8/23 06:39, Andrew Pinski via Gcc-patches wrote:
The problem here is after r6-7425-ga9fee7cdc3c62d0e51730,
the comparison to see if the transformation could be done was using the
wrong value. Instead of see if the inner was LE (for MIN and GE for MAX)
the outer value, it was comparing
On 8/31/23 11:36, Edwin Lu wrote:
Related Discussion:
https://inbox.sourceware.org/gcc-patches/12fb5088-3f28-0a69-de1e-f387371a5...@gmail.com/
This patch updates the THEAD instructions to ensure that no insn is left
without a type attribute.
Tested for regressions using rv32/64 multilib for
François Dumont via Gcc-patches writes:
> Following confirmation of the fix by TC here is the patch where I'm
> simply adding a 'constexpr' on _M_next().
>
> Please let me know this ChangeLog entry is correct. I would prefer
> this patch to be assigned to 'TC' with me as co-author but I don't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91972
Eric Gallager changed:
What|Removed |Added
Keywords|easyhack|
--- Comment #9 from Eric Gallager ---
On 9/10/23 08:07, Juzhe-Zhong wrote:
gcc/ChangeLog:
* config/riscv/riscv-v.cc (shuffle_compress_patterns): Avoid
unnecessary slideup.
OK
jeff
Address comment: [PATCH V2] RISC-V: Avoid unnecessary slideup in compress
pattern of vec_perm (gnu.org)
juzhe.zh...@rivai.ai
From: Jeff Law
Date: 2023-09-10 21:34
To: Juzhe-Zhong; gcc-patches
CC: kito.cheng; kito.cheng; rdapp.gcc
Subject: Re: [PATCH] RISC-V: Avoid unnecessary slideup in
Tested on x86_64-darwin21 and i686-darwin9 with both dwarfutils and
llvm-based dsymutil implementations. Pushed to trunk, thanks
Iain
--- 8< ---
Although the Darwin ABI places both hot and cold partitions in the same
section (the linker can partition by name), this does not work with the
Address comment: [PATCH V2] RISC-V: Avoid unnecessary slideup in compress
pattern of vec_perm (gnu.org)
juzhe.zh...@rivai.ai
From: Juzhe-Zhong
Date: 2023-09-10 22:07
To: gcc-patches
CC: kito.cheng; kito.cheng; jeffreyalaw; rdapp.gcc; Juzhe-Zhong
Subject: [PATCH V2] RISC-V: Avoid unnecessary
gcc/ChangeLog:
* config/riscv/riscv-v.cc (shuffle_compress_patterns): Avoid
unnecessary slideup.
---
gcc/config/riscv/riscv-v.cc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gcc/config/riscv/riscv-v.cc b/gcc/config/riscv/riscv-v.cc
index
Following confirmation of the fix by TC here is the patch where I'm
simply adding a 'constexpr' on _M_next().
Please let me know this ChangeLog entry is correct. I would prefer this
patch to be assigned to 'TC' with me as co-author but I don't know how
to do such a thing. Unless I need to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472
--- Comment #31 from matoro ---
(In reply to Eric Gallager from comment #30)
> (In reply to matoro from comment #26)
> > We also had somebody report on IRC that they observed this on powerpc (not
> > sure what tuple), again with -j1. It does
On 9/9/23 20:33, Juzhe-Zhong wrote:
When debugging FAIL: gcc.dg/pr92301.c execution test.
Realize a vls vector permutation situation failed to vectorize since early
return false:
- /* For constant size indices, we dont't need to handle it here.
- Just leave it to vec_perm. */
- if
On 9/9/23 21:55, Juzhe-Zhong wrote:
If a const vector all elements are same, the slide up is unnecessary.
gcc/ChangeLog:
* config/riscv/riscv-v.cc (shuffle_compress_patterns): Avoid
unnecessary slideup.
---
gcc/config/riscv/riscv-v.cc | 2 +-
1 file changed, 1 insertion(+), 1
efix=/repo/gcc-trunk//binary-trunk-r14-3825-20230910101237-g0d50facd937-checking-yes-df-extra-riscv64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20230910 (experimental) (GCC)
epo/gcc-trunk//binary-trunk-r14-3825-20230910101237-g0d50facd937-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20230910 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81114
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111360
Eric Gallager changed:
What|Removed |Added
CC||belyshev at depni dot
sinp.msu.ru
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111360
Bug ID: 111360
Summary: contrib/gcc_update: bad test
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17239
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111359
Eric Gallager changed:
What|Removed |Added
CC||rearnsha at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111359
Bug ID: 111359
Summary: contrib/gcc-git-customization.sh uses getent, which is
non-portable
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111300
--- Comment #7 from Jonathan Wakely ---
Given the note, maybe this is an intentional error to avoid creating a compiled
module interface that might not be usable:
note: a later '-fabi-version=' (or =0) avoids this error with a change in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111300
Jonathan Wakely changed:
What|Removed |Added
Summary|[14 Regression] |Modules error: mangling of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111358
--- Comment #1 from Jiang An ---
Related issues:
Monadic operations of expected are not ADL-proof per the uses of **this in
[expected.object.monadic]. However, currently implementations make them
ADL-proof by directly naming the union member,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111358
Bug ID: 111358
Summary: libstdc++'s optional::and_then and optional::transform
are not ADL-proof
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords:
Thanks Joseph, below is a a revised version of this patch
with slight additional changes to the comment of
tagged_types_tu_compatible_p.
ok for trunk?
Martin
Am Mittwoch, dem 06.09.2023 um 20:59 + schrieb Joseph Myers:
> On Sat, 26 Aug 2023, Martin Uecker via Gcc-patches wrote:
>
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111356
--- Comment #4 from Xi Ruoyao ---
BTW it works with 13.2.0 with "ulimit -s 131072" too, so it's a stack usage
issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111356
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
Known to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110068
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472
--- Comment #30 from Eric Gallager ---
(In reply to matoro from comment #26)
> We also had somebody report on IRC that they observed this on powerpc (not
> sure what tuple), again with -j1. It does not seem to show up with -j2, so
> likely -j1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90685
--- Comment #4 from Eric Gallager ---
(In reply to Eric Gallager from comment #3)
> (In reply to Eric Gallager from comment #2)
> > I just got a similar error on gcc13 on the compile farm; config.guess there
> > reports:
> >
> > $
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472
Eric Gallager changed:
What|Removed |Added
Status|WAITING |NEW
CC|
86 matches
Mail list logo
