https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113087
--- Comment #37 from Robin Dapp ---
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113206#c9
> Using 4a0a8dc1b88408222b88e10278017189f6144602, the spec run failed on:
> zvl128b (All runtime fails):
> 527.cam4 (Runtime)
> 531.deepsjeng (Runtime)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495
--- Comment #30 from JuzheZhong ---
Ok. I believe m_avl_def_in && m_avl_def_out can be removed with a better
algorthm.
Then the memory-hog should be fixed soon.
I am gonna rewrite avl_vl_unmodified_between_p and trigger full coverage
testingl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113441
--- Comment #8 from JuzheZhong ---
I believe the change between Nov and Dec causes regression.
But I don't continue on bisection.
Hope this information can help with your bisection.
Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109092
--- Comment #9 from GCC Commits ---
The trunk branch has been updated by Lehua Ding :
https://gcc.gnu.org/g:f625c017e60b6e05675b7d6280f2c7677ce691c3
commit r14-8333-gf625c017e60b6e05675b7d6280f2c7677ce691c3
Author: Juzhe-Zhong
Date: Mon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113507
--- Comment #3 from H.J. Lu ---
(In reply to Kewen Lin from comment #2)
> Guessing /usr/local/bin/ld is a gnu ld? Based on what I heard before, gnu ld
> has some problems on aix, people pass object files to aix system and use aix
> ld there.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112600
Tamar Christina changed:
What|Removed |Added
CC||tnfchris at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113466
--- Comment #3 from Richard Biener ---
Well, this simply highlights that the CFG doesn't really match "returns-twice".
The "returns-twice" part is just
(void) // no return value
but only the SJLJ __builtin_setjmp_setup/receiver has this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113441
--- Comment #7 from JuzheZhong ---
(In reply to Tamar Christina from comment #6)
> Hello,
>
> I can bisect it if you want. it should only take a few seconds.
Ok. Thanks a lot ...
I take 2 hours to bisect it manually but still didn't locate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113441
--- Comment #6 from Tamar Christina ---
Hello,
I can bisect it if you want. it should only take a few seconds.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113441
--- Comment #5 from JuzheZhong ---
Confirm at Nov, 1. The regression is gone.
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=eac0917bd3d2ead4829d56c8f2769176087c7b3d
This commit is ok, which has no regressions.
Still bisecting manually.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113466
Jakub Jelinek changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495
--- Comment #29 from Richard Biener ---
(In reply to rguent...@suse.de from comment #26)
> On Fri, 19 Jan 2024, juzhe.zhong at rivai dot ai wrote:
>
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495
> >
> > --- Comment #22 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495
--- Comment #28 from JuzheZhong ---
(In reply to Robin Dapp from comment #27)
> Following up on this:
>
> I'm seeing the same thing Patrick does. We create a lot of large non-sparse
> sbitmaps that amount to around 33G in total.
>
> I did
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495
--- Comment #27 from Robin Dapp ---
Following up on this:
I'm seeing the same thing Patrick does. We create a lot of large non-sparse
sbitmaps that amount to around 33G in total.
I did local experiments replacing all sbitmaps that are not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111966
--- Comment #1 from GCC Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:13127dac106724bef3a979539a878b368b79ce56
commit r14-8332-g13127dac106724bef3a979539a878b368b79ce56
Author: Tobias Burnus
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113539
--- Comment #4 from Alex Coplan ---
Reproduces with just -O3 -fno-strict-aliasing FWIW, no LTO or -mcpu needed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113539
Tamar Christina changed:
What|Removed |Added
Priority|P3 |P1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113539
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
--- Comment #2 from Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113539
Tamar Christina changed:
What|Removed |Added
CC||tnfchris at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113401
--- Comment #9 from Iain Sandoe ---
(In reply to Florian Weimer from comment #8)
> Which version of the manual page are you looking at?
>
> https://man7.org/linux/man-pages/man3/pthread_cleanup_push.3.html seems
> pretty clear about the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113539
Bug ID: 113539
Summary: [14 Regression] perlbench miscompiled on aarch64 since
r14-8223-g1c1853a70f
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113401
--- Comment #8 from Florian Weimer ---
Which version of the manual page are you looking at?
https://man7.org/linux/man-pages/man3/pthread_cleanup_push.3.html seems pretty
clear about the scope-based nature (search for discussion of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113401
--- Comment #7 from Iain Sandoe ---
(In reply to Florian Weimer from comment #6)
> Sorry, pthread_cleanup_push is purely scope-based, like the existing
> handler. It cannot be used to push a handler to some unscoped cleanup
> function list that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113401
--- Comment #6 from Florian Weimer ---
Sorry, pthread_cleanup_push is purely scope-based, like the existing handler.
It cannot be used to push a handler to some unscoped cleanup function list that
persists even after the current function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113401
--- Comment #5 from Iain Sandoe ---
(In reply to Florian Weimer from comment #4)
> (In reply to Iain Sandoe from comment #3)
> > for platforms using pthreads as the underlying resource, then perhaps we can
> > do this without thread_atexit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113425
--- Comment #4 from Tamar Christina ---
(In reply to Christophe Lyon from comment #3)
> What I meant by arm-* is that we see the same issue on several of the
> configurations we test, as can be seen on
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113425
--- Comment #3 from Christophe Lyon ---
What I meant by arm-* is that we see the same issue on several of the
configurations we test, as can be seen on
https://linaro.atlassian.net/browse/GNU-1100
We have recently improved the extraction of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113401
--- Comment #4 from Florian Weimer ---
(In reply to Iain Sandoe from comment #3)
> for platforms using pthreads as the underlying resource, then perhaps we can
> do this without thread_atexit (which I do not see in many places) by using
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113521
--- Comment #3 from Richard Biener ---
It's probably the same issue though - IPA summarries not being forgiving to
decl type changes.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82580
Uroš Bizjak changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113425
Tamar Christina changed:
What|Removed |Added
CC||tnfchris at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113520
Richard Biener changed:
What|Removed |Added
Keywords||diagnostic
--- Comment #7 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113520
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2024-01-22
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109929
--- Comment #5 from Xi Ruoyao ---
The first good commit is:
commit aa2ad77a9b3994fb679e5295d9570f6f8696540d
Author: Szabolcs Nagy
Date: Tue May 9 11:07:05 2023 +0100
aarch64: Do not force a stack frame for EH returns
but I cannot see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111267
--- Comment #12 from Richard Sandiford ---
I don't object to the patch, but for the record: the current heuristics go back
a long way. Although I reworked the pass to use rtl-ssa a few years ago, I
tried as far as possible to preserve the old
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113519
--- Comment #3 from Richard Biener ---
Hmm, -fdebug-types-section ... mumbles sth about axing that.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113538
Bug ID: 113538
Summary: [RISC-V] --param=riscv-vector-abi will fail some cases
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109929
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59859
Bug 59859 depends on bug 109929, which changed state.
Bug 109929 Summary: profiledbootstrap failure on aarch64-linux-gnu with
graphite optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109929
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113511
Richard Biener changed:
What|Removed |Added
Target||powerpc*
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #11 from hirtham...@allterra-dno.de ---
(In reply to Jonathan Wakely from comment #7)
> (In reply to Jonathan Wakely from comment #6)
> > (In reply to Hirthammer from comment #5)
> > > This whole thing with std::format and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113504
--- Comment #2 from Ruben Laso ---
(In reply to Jonathan Wakely from comment #1)
> The parallel algos are taken from
> https://github.com/llvm/llvm-project/tree/main/pstl so I would file an issue
> upstream rather than here. The Intel PSTL
101 - 142 of 142 matches
Mail list logo