This patch resolves PR c++/84964 which is an ICE in the middle-end after
emitting a "sorry, unimplemented" message, and is a regression from
earlier releases of GCC. This issue is that after encountering a
function call requiring an unreasonable amount of stack space, the
code continues and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104700
--- Comment #6 from Richard Biener ---
Fix in testing.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104700
--- Comment #5 from Martin Liška ---
Btw. I see the same ICE on libreoffice.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104700
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104686
--- Comment #14 from Richard Biener ---
The pushed change is a micro-optimization not really addressing the underlying
issue which needs more analysis.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104686
--- Comment #13 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:a8250bbaeb2e8250c20db477fe67fd085214be7c
commit r12-7401-ga8250bbaeb2e8250c20db477fe67fd085214be7c
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104664
--- Comment #4 from Hongyu Wang ---
(In reply to Uroš Bizjak from comment #3)
> Reconfirmed as RA issue.
I'm afraid we'd avoid pattern like
(insn 180 179 182 2 (set (reg:V8HF 220)
(subreg:V8HF
Hi!
As mentioned in the PR, the latest Intel SDM has added:
"Processors that enumerate support for Intel® AVX (by setting the feature flag
CPUID.01H:ECX.AVX[bit 28])
guarantee that the 16-byte memory operations performed by the following
instructions will always be
carried out atomically:
•
Hi,
As PR103196 shows, p9-vec-length-full-7.c needs to be adjusted as the
complete unrolling can happen on some of its loops. This patch is to
use pragma "GCC unroll 0" to disable all possible loop unrollings.
Hope it can help the case not that fragile.
There are some other p9-vec-length*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101908
--- Comment #28 from cuilili ---
(In reply to H.J. Lu from comment #25)
> Can this be mitigated by removing redundant load and store?
Yes, inlining say_sphere can remove redundant loads and stores, O3 does
inlining, but O2 is more sensitive to
Hi,
This patch corrects the match pattern in pr56605.c. The former pattern
is wrong and test case fails with GCC11. It should match following insn on
each subtarget after mode promotion is disabled. The patch need to be
backported to GCC11.
//gimple
_17 = (unsigned int) _20;
Thanks, speculation barrier is not needed for loongarch.
I have removed the warning.
在 2022/2/25 上午3:32, Xi Ruoyao 写道:
On Sat, 2022-02-12 at 11:11 +0800, xucheng...@loongson.cn wrote:
From: chenglulu
2022-02-12 Chenghua Xu
Lulu Cheng
gcc/testsuite/
spec-barrier tests
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104712
--- Comment #3 from Andrew Pinski ---
(In reply to ajrh from comment #2)
> Oh drat, reduced test cases are maddening... it's an inline static const
> in my original. I'll try to reduce something again.
I think even with inline static
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104712
--- Comment #2 from ajrh at ajrh dot net ---
Oh drat, reduced test cases are maddening... it's an inline static const in
my original. I'll try to reduce something again.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104712
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104712
Bug ID: 104712
Summary: -fkeep-inline-functions causing link errors (debian
but not godbolt?)
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104704
--- Comment #4 from H.J. Lu ---
(In reply to Hongtao.liu from comment #3)
> (In reply to H.J. Lu from comment #1)
> > ix86_expand_vector_move shouldn't use ix86_gen_scratch_sse_rtx.
>
> Is it problematic for TARGET_GEN_MEMSET_SCRATCH_RTX?
It
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104686
--- Comment #12 from Hongtao.liu ---
(In reply to Hongtao.liu from comment #11)
> (In reply to Martin Liška from comment #8)
> > (In reply to Martin Liška from comment #7)
> > > (In reply to Richard Biener from comment #6)
> > > > Both
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104704
--- Comment #3 from Hongtao.liu ---
(In reply to H.J. Lu from comment #1)
> ix86_expand_vector_move shouldn't use ix86_gen_scratch_sse_rtx.
Is it problematic for TARGET_GEN_MEMSET_SCRATCH_RTX?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104704
--- Comment #2 from Hongtao.liu ---
Yes, thanks for the reproduced testcase.
On Fri, Feb 25, 2022 at 4:44 PM Hongyu Wang via Gcc-patches
wrote:
>
> Hi,
>
> This patch intends to sync with llvm change in
> https://reviews.llvm.org/D120307 to add enumeration and truncate
This will be documented in intel intrinsic guide.
> imm to unsigned char, so users could use ~ on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101908
--- Comment #27 from Hongtao.liu ---
> We can start with disabling vectorization with very cheap cost model to fix
Of course only for (>=)16-byte struct passing.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101908
--- Comment #26 from Hongtao.liu ---
(In reply to Richard Biener from comment #22)
> (In reply to Hongtao.liu from comment #21)
> > Now we have SLP node available in vector cost hook, maybe we can do sth in
> > cost model to prevent
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104686
--- Comment #11 from Hongtao.liu ---
(In reply to Martin Liška from comment #8)
> (In reply to Martin Liška from comment #7)
> > (In reply to Richard Biener from comment #6)
> > > Both revisions affect vectorizer cost modeling only. With
> > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104618
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:0096b0b467b2c98ed258f0ead9a8b87b2a6d8466
commit r12-7398-g0096b0b467b2c98ed258f0ead9a8b87b2a6d8466
Author: Jason Merrill
Date:
The patch for PR90451 deferred marking to the point of actual use; we missed
this one because of the parens.
Tested x86_64-pc-linux-gnu, applying to trunk.
PR c++/104618
gcc/cp/ChangeLog:
* typeck.cc (cp_build_addr_expr_1): Also
maybe_undo_parenthesized_ref.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104711
--- Comment #4 from Segher Boessenkool ---
Created attachment 52522
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52522=edit
testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104711
--- Comment #3 from Segher Boessenkool ---
... does NOT have a good enough balance ...
Sorry :-)
Snapshot gcc-12-20220227 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20220227/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104711
Segher Boessenkool changed:
What|Removed |Added
Last reconfirmed||2022-02-27
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104711
Andrew Pinski changed:
What|Removed |Added
Keywords||documentation
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104711
Bug ID: 104711
Summary: Unnecessary -Wshift-negative-value warning
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104710
Arnaud Charlet changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104710
Bug ID: 104710
Summary: Ada-Bootstrap fails with gcc-4.8.4
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104570
Mikael Morin changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |mikael at gcc dot
gnu.org
The declarations of _DINFINITY, _SINFINITY and _SQNAN need to be constant
expressions.
Committed to trunk.
Dave
---
2022-02-27 John David Anglin
fixincludes/ChangeLog:
* inclhack.def (hpux_math_constexpr): New hack.
* fixincl.x: Regenerate.
* tests/base/math.h:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104610
--- Comment #14 from H.J. Lu ---
(In reply to H.J. Lu from comment #13)
> (In reply to Hongtao.liu from comment #8)
> > Created attachment 52495 [details]
> > untested patch.
>
> I see these regressions with -m32:
>
> FAIL:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104610
--- Comment #13 from H.J. Lu ---
(In reply to Hongtao.liu from comment #8)
> Created attachment 52495 [details]
> untested patch.
I see these regressions with -m32:
FAIL: gcc.dg/lower-subreg-1.c scan-rtl-dump subreg1 "Splitting reg"
FAIL:
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 Swedish team of translators. The file is available at:
https://translationproject.org/latest/gcc/sv.po
(This file,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104709
Bug ID: 104709
Summary: A translated error message will include untanslated
parts
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104705
Martin Liška changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80270
Roger Sayle changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |roger at
nextmovesoftware dot com
This patch fixes PR middle-end/80270, an ICE-on-valid regression, where
performing a bitfield extraction on a variable explicitly stored in a
hard register by the user causes a segmentation fault during RTL
expansion. Nearly identical source code without the "asm" qualifier
compiles fine. The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104707
Andrew Pinski changed:
What|Removed |Added
CC||rui314 at gmail dot com
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104708
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104708
--- Comment #1 from Rui Ueyama ---
Here is the link to the original bug report:
https://github.com/rui314/mold/issues/358
46 matches
Mail list logo
