https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112716
--- Comment #8 from Richard Biener ---
(In reply to uecker from comment #7)
> (In reply to rguent...@suse.de from comment #6)
> > On Mon, 27 Nov 2023, muecker at gwdg dot de wrote:
> >
> > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112716
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112743
Bug ID: 112743
Summary: RISC-V: building FAIL with -march=rv64(or
rv32)gc_zve32f_zvfh_zfh
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112743
Li Pan changed:
What|Removed |Added
CC||pan2.li at intel dot com
--- Comment #1 from L
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109077
--- Comment #3 from GCC Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:594ef1ff707866bcdc1f077c5d078a5bd250320f
commit r14-5899-g594ef1ff707866bcdc1f077c5d078a5bd250320f
Author: David Malcolm
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109077
--- Comment #4 from David Malcolm ---
Should be fixed on trunk for GCC 14 by the above patch.
Keeping open to track backporting to the GCC 11, 12 and 13 branches.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112744
Bug ID: 112744
Summary: Nested name specifier wrongly produces ambiguity in
accessing static field
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Severity: n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112733
Richard Biener changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112734
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112734
--- Comment #3 from Jakub Jelinek ---
And, we need to do it actually for all bitints including the smallest ones,
because libgcc.a will handle just 32/64/128 bit cases and not 2, 16, 37, 127,
238 etc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112719
--- Comment #5 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:03877e7eccd2734ca93a2d13aa2abf55e0aec923
commit r14-5900-g03877e7eccd2734ca93a2d13aa2abf55e0aec923
Author: Jakub Jelinek
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112719
--- Comment #6 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:f1b03fa964527678f15e6ef416bfe37e60b3dc54
commit r14-5901-gf1b03fa964527678f15e6ef416bfe37e60b3dc54
Author: Jakub Jelinek
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111754
--- Comment #14 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:e6c01334ccfca8bc748c8de90ba2a636d1662490
commit r14-5902-ge6c01334ccfca8bc748c8de90ba2a636d1662490
Author: Jakub Jelinek
Date:
This mailing list is for automated email from our Bugzilla bug
database, not for reporting bugs directly.
Please see https://gcc.gnu.org/bugs/ for instructions on how to report
bugs.
However, Andrew already explained why GCC is correct and this is not a
GCC bug. Just use DECLARE_SINGLETON(Receive
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112719
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109849
--- Comment #26 from Jonathan Wakely ---
(In reply to GCC Commits from comment #23)
> https://gcc.gnu.org/g:aae723d360ca26cd9fd0b039fb0a616bd0eae363
>
> commit r14-5831-gaae723d360ca26cd9fd0b039fb0a616bd0eae363
> Author: Martin Jambor
> Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112733
Jakub Jelinek changed:
What|Removed |Added
Keywords|needs-bisection |
--- Comment #5 from Jakub Jelinek ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109849
--- Comment #27 from Martin Jambor ---
(In reply to Jonathan Wakely from comment #26)
> (In reply to GCC Commits from comment #23)
> > https://gcc.gnu.org/g:aae723d360ca26cd9fd0b039fb0a616bd0eae363
> >
> > commit r14-5831-gaae723d360ca26cd9fd0b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52252
--- Comment #11 from rguenther at suse dot de ---
On Tue, 28 Nov 2023, pinskia at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52252
>
> Andrew Pinski changed:
>
>What|Removed |Adde
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32667
--- Comment #53 from rguenther at suse dot de ---
On Tue, 28 Nov 2023, post+gcc at ralfj dot de wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32667
>
> --- Comment #51 from post+gcc at ralfj dot de ---
> Oh great, I love it when one par
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32667
--- Comment #54 from Richard Biener ---
(In reply to post+gcc from comment #52)
> For the point discussed earlier with the `restrict` in the musl memcpy, I
> had another look at the definition of `restrict` and it's not entirely clear
> to me any
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32667
--- Comment #55 from Florian Weimer ---
(In reply to post+gcc from comment #52)
> For the point discussed earlier with the `restrict` in the musl memcpy, I
> had another look at the definition of `restrict` and it's not entirely clear
> to me any
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112694
--- Comment #6 from GCC Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:9f3f0b829b62f11f350867d2350e2af8639ec890
commit r14-5917-g9f3f0b829b62f11f350867d2350e2af8639ec890
Author: Juzhe-Zhong
Date: Tue Nov 28
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112694
JuzheZhong changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112732
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2023-11-28
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112734
--- Comment #4 from Richard Biener ---
Or make -ftrapv not cover bit-int?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112732
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=112734
--- Comment #5 from Jakub Jelinek ---
I think that is pretty much what is implemented (but not taking it into
account).
Ok, will try to figure out why we ICE.
I think -fnon-call-exceptions -ftrapv isn't really a good flag combination,
because no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112741
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=112742
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2023-11-28
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112745
Bug ID: 112745
Summary: stage 1 libgcc_s.so fails to link on FreeBSD
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112742
--- Comment #2 from Richard Biener ---
Ah, row*stride is loop invariant and that saves us with -m32. With -m64
we end up with
[local count: 105119324]:
row.0_1 = (unsigned int) row_13(D);
_2 = row.0_1 * stride_14(D);
[local count: 9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112743
Richard Biener changed:
What|Removed |Added
Component|c |target
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112729
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #2 from Hongyu Wang ---
> The cfi scan fails was caused by -fno-omit-frame-pointer which force push the
> frame pointer first and the cfi info become different. By default
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112736
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112729
--- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #3 from Hongyu Wang ---
[...]
> Hi Rainer, can you help verify if the change make these test pass on
> solaris/FreeBSD?
They do on Solaris/x86. Thanks.
FreeBSD was more
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112729
Rainer Orth changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
--- Comment #52 from Manolis Tsamis ---
(In reply to Sam James from comment #51)
> manolis, did you have a chance to look at the remaining pass issue? You'll
> need to revert Dave's commit locally which made the issue latent for
> building Pytho
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109849
--- Comment #28 from Jonathan Wakely ---
(In reply to Martin Jambor from comment #27)
> Unfortunately I cannot reproduce this, the above (on pristine master
> commit 006e90e1344 on an x86_64-linux) results in:
>
> Running target unix/-D_GLIBCXX
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111409
Rainer Orth changed:
What|Removed |Added
CC||ro at gcc dot gnu.org
--- Comment #3 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112728
Rainer Orth changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109849
--- Comment #29 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #28)
> (In reply to Martin Jambor from comment #27)
> > Can you please try if
> > https://gcc.gnu.org/pipermail/gcc-patches/2023-November/638318.html
> > fixes th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112729
--- Comment #7 from Hongyu Wang ---
(In reply to r...@cebitec.uni-bielefeld.de from comment #5)
>
> Is there a reason to have -fomit-frame-pointer once before and once
> after -mapx-features=push2pop2?
Ah, thanks for pointing that out. Will ad
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112563
--- Comment #14 from GCC Commits ---
The master branch has been updated by Rainer Orth :
https://gcc.gnu.org/g:088d3cbc5f906444a7dee98bc9a6f4b724ddfc21
commit r14-5927-g088d3cbc5f906444a7dee98bc9a6f4b724ddfc21
Author: Rainer Orth
Date: Tue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112563
--- Comment #15 from GCC Commits ---
The master branch has been updated by Rainer Orth :
https://gcc.gnu.org/g:33b6ce99b54917a910b59dbd643fd223fbba834c
commit r14-5928-g33b6ce99b54917a910b59dbd643fd223fbba834c
Author: Rainer Orth
Date: Tue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112733
--- Comment #6 from Jakub Jelinek ---
One thing is obviously we shouldn't crash on it and will debug that.
But, what multiple_of_p does (or its callers) is weird:
14552 /* Check for special cases to see if top is defined as
multiple
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112733
Jakub Jelinek changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112563
Rainer Orth changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |ro at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112716
--- Comment #9 from Martin Uecker ---
(In reply to Richard Biener from comment #8)
> (In reply to uecker from comment #7)
>
> > >
> > > Note that even without LTO when you enable inlining you'd expose two
> > > different structures with two di
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109253
--- Comment #3 from GCC Commits ---
The master branch has been updated by Jose E. Marchesi :
https://gcc.gnu.org/g:f31a019d1161ec78846473da743aedf49cca8c27
commit r14-5930-gf31a019d1161ec78846473da743aedf49cca8c27
Author: Jose E. Marchesi
Dat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110415
--- Comment #4 from GCC Commits ---
The master branch has been updated by Andrew Jenner :
https://gcc.gnu.org/g:b247e917ff13328298c1eecf8563b12edd7ade04
commit r14-5931-gb247e917ff13328298c1eecf8563b12edd7ade04
Author: Andrew Jenner
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109849
--- Comment #30 from Jonathan Wakely ---
So far the only FAIL is still see is:
FAIL: 23_containers/vector/types/1.cc -std=gnu++98 (test for excess errors)
I'm not sure if this is caused by your patch or one of Honza's. The test only
fails wit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110606
--- Comment #4 from Segher Boessenkool ---
It needs -O2 -fPIC -fno-exceptions to fail.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110415
Andrew Jenner changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37336
Bug 37336 depends on bug 110415, which changed state.
Bug 110415 Summary: (Re)allocation on assignment to allocatable polymorphic
variable from allocatable polymorphic function result
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110415
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111754
--- Comment #15 from prathamesh3492 at gcc dot gnu.org ---
Sorry for the regression, and thanks for the prompt fix!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110606
--- Comment #5 from Segher Boessenkool ---
The insn that it fails on is the result from a split using *tls_ld .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109253
Jose E. Marchesi changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112733
--- Comment #8 from Jakub Jelinek ---
As for the actual crash, I have again multiple possible fixes:
--- gcc/wide-int.cc.jj 2023-10-16 14:24:46.360204472 +0200
+++ gcc/wide-int.cc 2023-11-28 16:33:35.737394223 +0100
@@ -1297,6 +1297,8 @@ wi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112494
--- Comment #9 from GCC Commits ---
The master branch has been updated by Uros Bizjak :
https://gcc.gnu.org/g:99db2ce2419245e40808a9fad45113315496a907
commit r14-5933-g99db2ce2419245e40808a9fad45113315496a907
Author: Uros Bizjak
Date: Tue N
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112732
--- Comment #3 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:f26d68d5d128c86faaceeb81b1e8f22254ad53df
commit r14-5934-gf26d68d5d128c86faaceeb81b1e8f22254ad53df
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112741
--- Comment #3 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:f45d5e30bd98ea1d8dc29841a06b2cfa5662deb5
commit r14-5935-gf45d5e30bd98ea1d8dc29841a06b2cfa5662deb5
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112741
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101057
Bug 101057 depends on bug 112741, which changed state.
Bug 112741 Summary: ICE: in gimplify_var_or_parm_decl, at gimplify.cc:3261
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112741
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112732
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112560
Bug 112560 depends on bug 112494, which changed state.
Bug 112494 Summary: ICE in ix86_cc_mode, at config/i386/i386.cc:16477
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112494
What|Removed |Added
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112494
Uroš Bizjak changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112733
--- Comment #9 from Jakub Jelinek ---
Actually, maybe better variant of the first fix in the above comment would be:
--- gcc/wide-int.cc.jj 2023-11-28 16:56:50.0 +0100
+++ gcc/wide-int.cc 2023-11-28 16:58:02.268776755 +0100
@@ -1985
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112746
Bug ID: 112746
Summary: Missed optimization for redundancy computation
elimination (fre1(tree) for global variable)
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112280
--- Comment #8 from Sam James ---
I suspect I've just hit this when trying to build pixman on s390x too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112747
Bug ID: 112747
Summary: #pragma GCC diagnostic ignored "-Wstringop-overflow"
has no effect in pre-compiled headers.
Product: gcc
Version: unknown
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112746
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111909
--- Comment #3 from GCC Commits ---
The master branch has been updated by Marc Poulhi?s :
https://gcc.gnu.org/g:396db92d3aa7412dd7133563fecbc6237fa81c02
commit r14-5936-g396db92d3aa7412dd7133563fecbc6237fa81c02
Author: Simon Wright
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103185
Patrick Palka changed:
What|Removed |Added
Summary|ind[arr] is rejected when |[11/12/13/14 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103185
Patrick Palka changed:
What|Removed |Added
Target Milestone|--- |11.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112747
Lewis Hyatt changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64117
Lewis Hyatt changed:
What|Removed |Added
CC||piannetta at kalrayinc dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103183
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
Su
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112560
Uroš Bizjak changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112733
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112733
--- Comment #11 from Jakub Jelinek ---
Created attachment 56707
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56707&action=edit
gcc14-pr112733-2.patch
Second patch to be tested. Turned out it is more complicated than that.
If n > m, i.e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112738
--- Comment #3 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:68ffaf839883253e0f288862ff20b8005c92df4e
commit r14-5938-g68ffaf839883253e0f288862ff20b8005c92df4e
Author: Andrew Pinski
Date: Mo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112738
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112748
Bug ID: 112748
Summary: memmove(ptr, ptr, n) call optimized out even at -O0
with -fsanitize=undefined
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Severity
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94264
Jason Merrill changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
Assig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112748
--- Comment #1 from Andrew Pinski ---
Does -fsanitize=address remove it?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112748
--- Comment #2 from Tavian Barnes ---
(In reply to Andrew Pinski from comment #1)
> Does -fsanitize=address remove it?
Yes, it's still removed with -fsanitize=address.
While ASAN is necessary to check that the memory is really allocated, UBSAN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112749
Bug ID: 112749
Summary: GCC accepts invalid code in concepts (requires clause
incorrectly satisfied)
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112744
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
gcc version 14.0.0 20231128 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112744
Marek Polacek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112606
seurer at gcc dot gnu.org changed:
What|Removed |Added
CC||seurer at gcc dot gnu.org
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102419
Patrick Palka changed:
What|Removed |Added
CC||novulae at hotmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112749
Patrick Palka changed:
What|Removed |Added
Resolution|--- |DUPLICATE
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112751
Bug ID: 112751
Summary: [14 regression] gcc.target/powerpc/pcrel-sibcall-1.c
fails after r14-5628-g53ba8d669550d3
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112751
--- Comment #1 from Andrew Pinski ---
This is just a testsuite issue. The functions are currently marked as noinline.
You can either add -fno-ipa-vrp or mark them with noipa instead. I am not sure
if noipa here is right due to having some ipa h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53220
--- Comment #23 from GCC Commits ---
The trunk branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:305a2686c99bf9b57490419f25c79f6fb3ae0feb
commit r14-5941-g305a2686c99bf9b57490419f25c79f6fb3ae0feb
Author: Jason Merrill
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94264
--- Comment #8 from GCC Commits ---
The trunk branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:305a2686c99bf9b57490419f25c79f6fb3ae0feb
commit r14-5941-g305a2686c99bf9b57490419f25c79f6fb3ae0feb
Author: Jason Merrill
Date: Tue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70
Eric Botcazou changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109849
--- Comment #31 from Jonathan Wakely ---
Bisection points to r14-5831-gaae723d360ca26cd9fd0b039fb0a616bd0eae363 for that
remaining FAIL as well (and it isn't fixed by the new patch).
It introduced a new warning which wasn't present before:
/tm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52252
--- Comment #12 from Andrew Pinski ---
(In reply to rguent...@suse.de from comment #11)
> We're lacking a way to say one of the bit_not should be single-used,
> one multi-use would be OK and a fair trade-off - not sure if that
> would be enough h
1 - 100 of 133 matches
Mail list logo