https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107090
--- Comment #11 from vfdff ---
Created attachment 53787
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53787&action=edit
has different operand order base on different commit node
hi @Andrew Pinski
* Showed as the figure swap_order.jpg at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107451
bartoldeman at users dot sourceforge.net changed:
What|Removed |Added
Attachment #53785|0 |1
is o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103035
Bug 103035 depends on bug 98694, which changed state.
Bug 98694 Summary: GCC produces incorrect code for loops with -O3 for
skylake-avx512 and icelake-server
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98694
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98694
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102786
Andrew Pinski changed:
What|Removed |Added
Known to work||10.4.0, 12.1.0, 9.5.0
Target Mileston
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101176
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |9.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101008
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |10.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107397
--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #5)
> No. I have no idea how to add a testcase to git.
> Every time I've tried, I end up deleting my git
> repository and grabbing a new clone. Not a pleas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107397
--- Comment #5 from Steve Kargl ---
On Fri, Oct 28, 2022 at 08:31:58PM +, anlauf at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107397
>
> --- Comment #4 from anlauf at gcc dot gnu.org ---
> (In reply to kargl from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107453
--- Comment #1 from Andrew Pinski ---
>From https://gcc.gnu.org/pipermail/gcc-patches/2022-October/604152.html:
It's possible further
target-specific fixes will be needed; target maintainers should watch
out for failures of c2x-stdarg-4.c, the e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107453
Bug ID: 107453
Summary: New stdarg tests in r13-3549-g4fe34cdcc80ac2 fail
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103413
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103413
--- Comment #19 from CVS Commits ---
The releases/gcc-10 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:3b4c9e0658b13b8db6c7f38242ed270cdb8fc932
commit r10-11063-g3b4c9e0658b13b8db6c7f38242ed270cdb8fc932
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93177
--- Comment #22 from Sergey Fedorov ---
(In reply to Iain Sandoe from comment #19)
> Created attachment 53779 [details]
> introduce ppc_intrinsics.h for powerpc*-darwin.
>
> This takes the header from the GCC-4.x apple debt branch (as present in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103413
--- Comment #18 from CVS Commits ---
The releases/gcc-11 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:f2298bd50109e5460e8949290b5337ec28310e91
commit r11-10343-gf2298bd50109e5460e8949290b5337ec28310e91
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #32 from joseph at codesourcery dot com ---
On Fri, 28 Oct 2022, jakub at gcc dot gnu.org via Gcc-bugs wrote:
> > That said, if C allows us to limit to 128bits then let's do that for now.
> > 32bit targets will still see all the com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103413
--- Comment #17 from CVS Commits ---
The releases/gcc-12 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:9831a5f4843b573bbdb2688bbf2de864b4e8be8b
commit r12-8875-g9831a5f4843b573bbdb2688bbf2de864b4e8be8b
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107397
--- Comment #4 from anlauf at gcc dot gnu.org ---
(In reply to kargl from comment #3)
> This patch fixes the ICE and issues an error. It has passed
> regression testing.
Great!
Do you plan to submit your patch? (Hint: git gcc-commit-mklog).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #31 from joseph at codesourcery dot com ---
On Fri, 28 Oct 2022, rguenth at gcc dot gnu.org via Gcc-bugs wrote:
> I wouldn't go with a new tree code, given semantics are INTEGER_TYPE it should
> be an INTEGER_TYPE.
Implementation n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105549
Andrew Pinski changed:
What|Removed |Added
Summary|aarch64: Wrong va_arg |aarch64: Wrong va_arg
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105597
Andrew Pinski changed:
What|Removed |Added
Component|c |tree-optimization
Summary|ic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107441
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107452
--- Comment #2 from Andrew Pinski ---
>Is this a known GCC issue? If needed I could also try to write a minimal test
>that reproduces this issue.
Yes it is a known issue as shown by the duplicate bug report. The duplicate bug
report has a nice
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107452
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106627
Andrew Pinski changed:
What|Removed |Added
CC||kim.walisch at gmail dot com
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107452
Bug ID: 107452
Summary: Failed to catch C++ exception thrown from
multiarch-function (x64 CPUs)
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: norm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107451
Andrew Pinski changed:
What|Removed |Added
Known to work||10.4.0
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107451
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
St
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107451
Bug ID: 107451
Summary: Segmentation fault with vectorized code.
Product: gcc
Version: 11.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #30 from Andrew Pinski ---
I have an use case until 1k except I don't need division. It will in handy
while translating P4 language (https://p4.org/p4-spec/docs/P4-16-v-1.2.3.html)
to C. P4 supports any bit size you want and there ar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106806
seurer at gcc dot gnu.org changed:
What|Removed |Added
Target|powerpc64le-linux-gnu |powerpc64le-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107073
seurer at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106806
--- Comment #1 from seurer at gcc dot gnu.org ---
*** Bug 107073 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107073
seurer at gcc dot gnu.org changed:
What|Removed |Added
CC||bergner at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107345
--- Comment #5 from Geoffrey ---
(In reply to David Malcolm from comment #3)
> Fixed on trunk for GCC 13 by the above patch.
>
> Keeping open for backporting to GCC 12.
That is really great! Thanks a lot!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107345
--- Comment #4 from Geoffrey ---
(In reply to David Malcolm from comment #3)
> Fixed on trunk for GCC 13 by the above patch.
>
> Keeping open for backporting to GCC 12.
That is really great! Thanks a lot!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107172
--- Comment #48 from H.J. Lu ---
(In reply to Roger Sayle from comment #47)
> I really don't believe that using UNSPEC here is the correct way to go, but
> it appears to be the (only?) approach that Segher is prepared to approve.
> Hohum.
I wi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107450
--- Comment #1 from Jason Liam ---
Also if we remove one of the template parameter(say T3) then msvc starts
compiling this code as well. Demo: https://godbolt.org/z/qacMzoT3q
Additionally, this current bug is most probably a duplicate of:
http
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107376
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107376
--- Comment #2 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:988dd22ec6665117e8587389ac85389f1c321c45
commit r13-3548-g988dd22ec6665117e8587389ac85389f1c321c45
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107439
--- Comment #2 from Patrick Palka ---
So the question is if in C++20 mode we're allowed to reject ahead of time a
call to an unknown template-id with dependent template arguments and no
function arguments (as in the original testcase):
template
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107436
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107411
qinzhao at gcc dot gnu.org changed:
What|Removed |Added
CC||qinzhao at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107346
--- Comment #10 from CVS Commits ---
The master branch has been updated by Andre Simoes Dias Vieira
:
https://gcc.gnu.org/g:95decac3ce8c8c7c5302cd6fac005a10463de165
commit r13-3547-g95decac3ce8c8c7c5302cd6fac005a10463de165
Author: Andre Vieira
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107439
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107407
Richard Biener changed:
What|Removed |Added
Known to fail||12.2.0
Summary|[12/13 Regre
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107407
--- Comment #4 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:031a400e49d8db156c43f9ec0b21ab0c2aee8c6d
commit r13-3546-g031a400e49d8db156c43f9ec0b21ab0c2aee8c6d
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107450
Bug ID: 107450
Summary: GCC accepts invalid program involving multiple
template parameter packs
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107435
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107449
Bug ID: 107449
Summary: CD-DCE fails to eliminate abnormal incoming edges
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: ice-checking, ice-on-valid-code
Severi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107447
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107447
--- Comment #3 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:1add3635563b39e3c0e9bed4930d11b3f605fdd3
commit r13-3545-g1add3635563b39e3c0e9bed4930d11b3f605fdd3
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107435
--- Comment #3 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:084128583212bd64308f50c2ab5f4c03be40e48c
commit r13-3544-g084128583212bd64308f50c2ab5f4c03be40e48c
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107407
--- Comment #3 from Richard Biener ---
Deleted dead store: MEM [(int *)&c][_6] = 3;
Further reduced testcase, we mistreat SSA name indexes with must aliases.
We do have
/* If we visit this PHI by following a backedge then we have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107447
--- Comment #2 from Richard Biener ---
Btw, there's also a stray incoming abnormal edge into bb2 here (as seen in
other bugs I've meanwhile fixed). We've elided a call to zero() there but
failed
to eliminate the incoming abnormal edge. CDDCE1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107447
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
L
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107443
Richard Biener changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107436
--- Comment #5 from Florian Schanda ---
Richard, if I may rephrase your statement (for clarity), you're saying:
> Under your assumptions, -fsignaling-nans should work. There are no known bugs
> in this setup, but if you find something please re
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107436
--- Comment #4 from Richard Biener ---
The question is what the expectations are. I think that all issues would be
considered bugs (see the list of referenced bugs).
Can you evaluate it according to your needs and file bugreports for issues no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107435
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassigned at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107432
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107426
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |12.3
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107425
Richard Biener changed:
What|Removed |Added
Priority|P3 |P4
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107424
Richard Biener changed:
What|Removed |Added
Priority|P3 |P4
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107422
Richard Biener changed:
What|Removed |Added
Priority|P5 |P4
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107411
Richard Biener changed:
What|Removed |Added
Blocks||24639
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107405
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107397
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |10.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107396
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #29 from Alejandro Colomar ---
Hi!
On 10/28/22 12:51, rguenther at suse dot de wrote:
> Quite likely yes (OTOH __BIGGEST_ALIGNMENT__ changed as well). That
> also means BITINT_MAXWIDTH should eventually be decided by the ABI
> grou
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #28 from rguenther at suse dot de ---
On Fri, 28 Oct 2022, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
>
> --- Comment #27 from Jakub Jelinek ---
> (In reply to Richard Biener from comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107413
--- Comment #6 from Rama Malladi ---
The compilation options were: -Ofast -mcpu=native -flto
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107413
--- Comment #5 from Rama Malladi ---
(In reply to Wilco from comment #2)
> That's interesting - if the reassociation pass has become a bit smarter in
> the last 5 years, we might no longer need this workaround. What is the
> effect on the overal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #27 from Jakub Jelinek ---
(In reply to Richard Biener from comment #26)
> Does the C standard limit the number of bits? Does it allow
> implementation defined limits?
The latter. limits.h defines BITINT_MAXWIDTH, which must be at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107407
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #26 from Richard Biener ---
Some random comments.
I wouldn't go with a new tree code, given semantics are INTEGER_TYPE it should
be an INTEGER_TYPE. The TYPE_PRECISION issue is real - we have 16 spare bits
in tree_type_common so we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107389
--- Comment #5 from Richard Biener ---
Created attachment 53784
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53784&action=edit
prototype
This implements an -O0 fold-builtins pass. I've disabled some but not all
"optimizations" and inst
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107436
--- Comment #3 from Florian Schanda ---
Maybe some additional constraints under which we operate can help:
- we never change our rounding mode away from RNE
- we never disable support for subnormals in any way
- we only ever use float32 and floa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107389
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107172
--- Comment #47 from Roger Sayle ---
I really don't believe that using UNSPEC here is the correct way to go, but it
appears to be the (only?) approach that Segher is prepared to approve. Hohum.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107057
--- Comment #9 from Uroš Bizjak ---
(In reply to Hongtao.liu from comment #7)
> And it looks like the pattern is wrongly defined since from [1].
>
> --cut begin
> Matching constraints are used in these circumstances. More pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90115
--- Comment #19 from CVS Commits ---
The releases/gcc-12 branch has been updated by Thomas Schwinge
:
https://gcc.gnu.org/g:9b116c51a451995f1bae8fdac0748fcf3f06aafe
commit r12-8874-g9b116c51a451995f1bae8fdac0748fcf3f06aafe
Author: Julian Brown
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90115
--- Comment #18 from CVS Commits ---
The master branch has been updated by Thomas Schwinge :
https://gcc.gnu.org/g:11e811d8e2f63667f60f73731bb934273f5882b8
commit r13-3541-g11e811d8e2f63667f60f73731bb934273f5882b8
Author: Julian Brown
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104069
--- Comment #26 from Sergei Trofimovich ---
#c12 fixed elfutils case.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107298
--- Comment #5 from CVS Commits ---
The master branch has been updated by Martin Liska :
https://gcc.gnu.org/g:3f9c071324eff249b23a7531e447fc17d928
commit r13-3539-g3f9c071324eff249b23a7531e447fc17d928
Author: Martin Liska
Date: Wed
85 matches
Mail list logo