https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102762
--- Comment #5 from CVS Commits ---
The releases/gcc-11 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:30c18bbfed2fae5ff89841172553951a74125f8e
commit r11-9226-g30c18bbfed2fae5ff89841172553951a74125f8e
Author: Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102788
--- Comment #10 from CVS Commits ---
The releases/gcc-11 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:34ed721929700b85f19f14fc56fb598a658b2bbc
commit r11-9227-g34ed721929700b85f19f14fc56fb598a658b2bbc
Author: Richard Biene
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102572
Richard Biener changed:
What|Removed |Added
Known to work||11.2.1
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103035
Bug 103035 depends on bug 102572, which changed state.
Bug 102572 Summary: [11 Regression] ICE for skx in
vect_build_gather_load_calls, at tree-vect-stmts.c:2835 since
r11-3070-g783dc66f9ccb0019
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=1025
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102139
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101480
Richard Biener changed:
What|Removed |Added
Known to work||11.2.1
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103133
--- Comment #3 from Richard Biener ---
Still a user error - you should link with -pthread
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103130
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103133
--- Comment #4 from Jonathan Wakely ---
(In reply to Richard Biener from comment #3)
> Still a user error - you should link with -pthread
That doesn't help here though.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103133
--- Comment #5 from Jonathan Wakely ---
(In reply to Florian Weimer from comment #2)
> libstdc++.a still uses weak symbols. I assumed we had already removed all
> that weak symbol stuff from libstdc++ for __GLIBC_PREREQ (2, 34).
No, none of tha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101636
--- Comment #10 from rguenther at suse dot de ---
On Mon, 8 Nov 2021, marxin at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101636
>
> --- Comment #9 from Martin Liška ---
> Valgrind reports:
>
> ==9236== Conditiona
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
--- Comment #22 from rguenther at suse dot de ---
On Mon, 8 Nov 2021, hubicka at kam dot mff.cuni.cz wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
>
> --- Comment #21 from hubicka at kam dot mff.cuni.cz ---
> > to also allow to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103133
Jonathan Wakely changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
--- Comment #23 from hubicka at kam dot mff.cuni.cz ---
> We verify that by simply looking at the loop depth relation of
> the entry and exit of the path.
Which seem wrong for the path leaving loop and entering another...
>
> > It seems to me t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103121
--- Comment #2 from dave.anglin at bell dot net ---
On 2021-11-08 4:24 a.m., rguenth at gcc dot gnu.org wrote:
> David, can you try adding
> -fno-tree-vectorize to the command line to see if that silences the
> diagnostic?
It does not silence th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102518
--- Comment #6 from CVS Commits ---
The releases/gcc-11 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:ae3227710c71ca693ee43c825f5d0d0fbd3c3773
commit r11-9228-gae3227710c71ca693ee43c825f5d0d0fbd3c3773
Author: Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102798
--- Comment #13 from CVS Commits ---
The releases/gcc-11 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:1631d6d2910e03e4517079d6e6ad0ae1aeb24dfa
commit r11-9229-g1631d6d2910e03e4517079d6e6ad0ae1aeb24dfa
Author: Richard Biene
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102518
Richard Biener changed:
What|Removed |Added
Known to fail||11.2.0
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102262
--- Comment #4 from Jonathan Wakely ---
Another variation:
template
struct vector
{
struct _Temp_value
{
constexpr
_Temp_value()
{
}
#ifndef ICE
constexpr
~_Temp_value()
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
--- Comment #24 from rguenther at suse dot de ---
On Mon, 8 Nov 2021, hubicka at kam dot mff.cuni.cz wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
>
> --- Comment #23 from hubicka at kam dot mff.cuni.cz ---
> > We verify that by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101824
--- Comment #7 from CVS Commits ---
The releases/gcc-9 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:8dec0ae6200ae8c56dbeef5ff9acd2214282de67
commit r9-9817-g8dec0ae6200ae8c56dbeef5ff9acd2214282de67
Author: Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101373
--- Comment #19 from CVS Commits ---
The releases/gcc-9 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:2498de689b735422ef71d93e2afe7ae3e6988bb3
commit r9-9818-g2498de689b735422ef71d93e2afe7ae3e6988bb3
Author: Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101868
--- Comment #13 from CVS Commits ---
The releases/gcc-9 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:2498de689b735422ef71d93e2afe7ae3e6988bb3
commit r9-9818-g2498de689b735422ef71d93e2afe7ae3e6988bb3
Author: Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101824
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101868
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
--- Comment #25 from Richard Biener ---
(In reply to rguent...@suse.de from comment #24)
> On Mon, 8 Nov 2021, hubicka at kam dot mff.cuni.cz wrote:
>
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
> >
> > --- Comment #23 from hubicka
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
--- Comment #26 from Richard Biener ---
(In reply to Richard Biener from comment #25)
> (In reply to rguent...@suse.de from comment #24)
> > On Mon, 8 Nov 2021, hubicka at kam dot mff.cuni.cz wrote:
> >
> > > https://gcc.gnu.org/bugzilla/show_b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103120
--- Comment #6 from CVS Commits ---
The master branch has been updated by Aldy Hernandez :
https://gcc.gnu.org/g:18546941ae4c56cd9240d2dc2ca2806e01eb6fb7
commit r12-5000-g18546941ae4c56cd9240d2dc2ca2806e01eb6fb7
Author: Aldy Hernandez
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103120
Aldy Hernandez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101636
--- Comment #11 from Martin Liška ---
> I'm going to fix that (but it's spurious)
Now as you fixed the valgrind error, I can still see the original verification
error. What about you?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101636
--- Comment #12 from Martin Liška ---
https://godbolt.org/z/n1sjM6TEY
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
--- Comment #27 from Aldy Hernandez ---
(In reply to Richard Biener from comment #20)
> (In reply to hubicka from comment #19)
> > The testcase would be
> >
> > void test ()
> > {
> > int i;
> > if (test())
> > i=0;
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102831
--- Comment #4 from Martin Sebor ---
I have been testing the following changes to deal with other location and
warning related problems. They might be worth giving a try to see if they help
with this issue as well.
diff --git a/gcc/diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103121
Martin Sebor changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103121
--- Comment #4 from John David Anglin ---
Created attachment 51748
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51748&action=edit
Preprocessed source
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103134
Bug ID: 103134
Summary: Redundant DW_AT_entry_pc tags for inlined functions
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103099
--- Comment #5 from CVS Commits ---
The master branch has been updated by Martin Jambor :
https://gcc.gnu.org/g:239d82d4c05b30632fd09ba4056de7dac5aee070
commit r12-5003-g239d82d4c05b30632fd09ba4056de7dac5aee070
Author: Martin Jambor
Date: M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103107
--- Comment #5 from CVS Commits ---
The master branch has been updated by Martin Jambor :
https://gcc.gnu.org/g:239d82d4c05b30632fd09ba4056de7dac5aee070
commit r12-5003-g239d82d4c05b30632fd09ba4056de7dac5aee070
Author: Martin Jambor
Date: M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103099
Martin Jambor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103107
Martin Jambor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103132
Martin Jambor changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56665
--- Comment #8 from Bogdan Slusarczyk ---
(In reply to Nikita Kniazev from comment #6)
> This is not a GCC bug. The examples above have use after scope bug.
> Look at `assign_a` documentation
> https://www.boost.org/doc/libs/1_69_0/libs/spirit/cl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56665
--- Comment #9 from Bogdan Slusarczyk ---
Gushhh my fault, VALUE not VARIABLE :) all it is clear, sorry.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103117
Jan Hubicka changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103122
--- Comment #2 from CVS Commits ---
The master branch has been updated by Andrew Macleod :
https://gcc.gnu.org/g:0cd653bd2559701da9cc4c9bf51f22bdd68623b5
commit r12-5006-g0cd653bd2559701da9cc4c9bf51f22bdd68623b5
Author: Andrew MacLeod
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103122
Andrew Macleod changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103035
Bug 103035 depends on bug 103122, which changed state.
Bug 103122 Summary: [12 Regression] ICE in fill_block_cache, at
gimple-range-cache.cc:1277 with -O2 since r12-4866-gfc4076752067fb40
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103122
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102906
--- Comment #9 from Christophe Lyon ---
(In reply to Aldy Hernandez from comment #7)
> > then size ivopts-4.o:
> >textdata bss dec hex filename
> > 38 0 0 38 26 ivopts-4.o
> > where the testcase exp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103135
Bug ID: 103135
Summary: DW_AT_high_pc 0 offset for inlined functions with a
singled instruction
Product: gcc
Version: 11.2.1
Status: UNCONFIRMED
Severity: norm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102906
Aldy Hernandez changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103127
--- Comment #3 from Peter Bergner ---
(In reply to Andrew Pinski from comment #1)
> The types are OPAQUE_TYPE.
[snip]
> So if I understand this correctly and PR 98872 correctly. We should not
> expand a DEFERRED_INIT for this type.
So something
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103136
Bug ID: 103136
Summary: [12 Regression] ICE in maybe_gen_insn, at
optabs.c:7871
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103136
G. Steinmetz changed:
What|Removed |Added
Keywords||ice-on-valid-code
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103137
Bug ID: 103137
Summary: [12 Regression] ICE in gfc_simplify_transpose, at
fortran/simplify.c:8181
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: norm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103138
Bug ID: 103138
Summary: [12 Regression] ICE in gfc_simplify_cshift, at
fortran/simplify.c:2139
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103139
Bug ID: 103139
Summary: [12 Regression] ICE in fold_convert_loc, at
fold-const.c:2573
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103121
Martin Sebor changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #5 from Martin Sebor --
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103121
Martin Sebor changed:
What|Removed |Added
CC||aldyh at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103127
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=103127
--- Comment #5 from Peter Bergner ---
(In reply to qinzhao from comment #4)
> with -ftrivial-auto-var-init=zero, failed at the same place.
You mean without the patch from Comment #3? With the patch, I don't see an ICE
using -ftrivial-auto-var-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103121
Andrew Macleod changed:
What|Removed |Added
CC||amacleod at redhat dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103127
--- Comment #6 from qinzhao at gcc dot gnu.org ---
(In reply to Peter Bergner from comment #5)
> (In reply to qinzhao from comment #4)
> > with -ftrivial-auto-var-init=zero, failed at the same place.
>
> You mean without the patch from Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103127
--- Comment #7 from qinzhao at gcc dot gnu.org ---
(In reply to Peter Bergner from comment #3)
> (In reply to Andrew Pinski from comment #1)
> > The types are OPAQUE_TYPE.
> [snip]
> > So if I understand this correctly and PR 98872 correctly. We
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103140
Bug ID: 103140
Summary: __builtin_bit_cast To C array target type
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: patch
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103121
--- Comment #8 from Martin Sebor ---
The [1, 1] range comes from a call to qry->range_of_expr (vr, exp, stmt) in in
get_size_range() in pointer-query.cc:
(gdb) p debug(gimple_bb(stmt))
[local count: 118111600]:
_4 = _1 + 1;
grp_name_37 = __bui
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103127
--- Comment #8 from Peter Bergner ---
(In reply to qinzhao from comment #7)
> (In reply to Peter Bergner from comment #3)
> > (In reply to Andrew Pinski from comment #1)
> > > The types are OPAQUE_TYPE.
> > [snip]
> > > So if I understand this c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103140
--- Comment #1 from Will Wray ---
Created attachment 51750
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51750&action=edit
c++: __builtin_bit_cast To C array target type
Proposed patch, submitted here:
https://gcc.gnu.org/pipermail/gcc-p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103121
--- Comment #9 from Andrew Macleod ---
(In reply to Martin Sebor from comment #8)
> The [1, 1] range comes from a call to qry->range_of_expr (vr, exp, stmt) in
> in get_size_range() in pointer-query.cc:
>
> (gdb)
> #7 0x0192c0df in str
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103127
--- Comment #9 from Qing Zhao ---
> On Nov 8, 2021, at 1:56 PM, bergner at gcc dot gnu.org
> wrote:
>
>
> So this then?
This is better, I think.
You can send a patch review request to gcc-patch alias for more comments or
approval.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103141
Bug ID: 103141
Summary: #pragma GCC diagnostic ignored
"-Wno-deprecated-declarations" doesn't work
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103138
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103141
--- Comment #1 from Noah Andrews ---
-Wno-deprecated also has this issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103121
--- Comment #10 from Martin Sebor ---
Sorry, I've been having trouble with GDB and so I'm running two GDB sessions
and I have been mixing output from both of them. I see the warning for the
store to *_23 in BB 13, not for BB 12. Here's a fresh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103137
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103142
Bug ID: 103142
Summary: [12 regression] gfortran.dg/vector_subscript_1.f90
fails at execution after r12-4976
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Sev
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103141
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103121
--- Comment #11 from Andrew Macleod ---
(In reply to Martin Sebor from comment #10)
> Sorry, I've been having trouble with GDB and so I'm running two GDB sessions
> and I have been mixing output from both of them. I see the warning for the
> st
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103142
Jan Hubicka changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102043
Jan Hubicka changed:
What|Removed |Added
CC||seurer at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103136
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103102
Andrew Pinski changed:
What|Removed |Added
CC||gs...@t-online.de
--- Comment #8 from A
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103127
--- Comment #10 from Peter Bergner ---
(In reply to Qing Zhao from comment #9)
> This is better, I think.
> You can send a patch review request to gcc-patch alias for more comments or
> approval.
Ok, if people are fine with this, I'll kick off
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103121
--- Comment #12 from Martin Sebor ---
Okay, here's my question: when I call range_of_expr (vr, _4, stmt) with stmt
being 'grp_name_37 = __builtin_alloca (_4)' in BB 4, should I not expect the
result to be either VR_VARYING or [0, +INF]?
What I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103137
--- Comment #2 from anlauf at gcc dot gnu.org ---
After playing with the Intel compiler, which accepts the testcase, I start
to think the code could actually be valid F2018.
At least I cannot find text in the F2018 standard prohibiting PARAMETER
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103138
--- Comment #2 from anlauf at gcc dot gnu.org ---
There are more testcases also with valid code which would ICE when using
CLASS and PARAMETER, or are rejected. See also pr103137.
Another one:
program p
type t
end type
class(t), paramete
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103121
--- Comment #13 from Martin Sebor ---
Here's a reduced test case that reproduces the problem with an x86_64-linux GCC
in ILP32 mode:
$ cat pr103121.C && gcc -O2 -S -Wall -m32 pr103121.C
typedef typeof (sizeof 0) size_t;
struct tree_node {
co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103141
--- Comment #3 from Noah Andrews ---
(In reply to Andrew Pinski from comment #2)
> you want:
> #pragma GCC diagnostic ignored "-Wdeprecated-declarations"
>
> Not the no- version
That's correct, thank you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102831
Peter Bergner changed:
What|Removed |Added
CC||bergner at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102831
--- Comment #6 from Peter Bergner ---
(In reply to Peter Bergner from comment #5)
> I see the same error in Comment #3 on my powerpc64le-linux build, which
> breaks my bootstrap too.
Hmmm, if I manually execute the failing compile command, it I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103121
--- Comment #14 from Andrew Macleod ---
As near as I can tell, you are calling debug_ranger () to see what ranger could
produce. That routine creates a new ranger and populates it, dumps out the
results, kills the ranger and returns.
When I pu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103143
Bug ID: 103143
Summary: [12 Regression] ICE due to infinite recursion in
pointer-query.cc
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103143
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101397
Martin Sebor changed:
What|Removed |Added
Depends on||103143
--- Comment #8 from Martin Sebor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99092
--- Comment #13 from Andrew Pinski ---
Did the LLVM assembler get fixed?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103143
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99657
Andrew Pinski changed:
What|Removed |Added
Keywords||error-recovery
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99657
Andrew Pinski changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99092
--- Comment #14 from Iain Sandoe ---
(In reply to Andrew Pinski from comment #13)
> Did the LLVM assembler get fixed?
not as of xcode 13.0 (I don't know if anyone filed a radar tho) - since the
problem was fixed on the branch, I guess no-one was
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102690
--- Comment #4 from seurer at gcc dot gnu.org ---
Was the change that caused this backported to gcc 11? I am seeing the same
failures there now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103143
--- Comment #1 from Andrew Pinski ---
But it does not fix:
int
f ()
{
char a[12];
__SVInt8_t freq;
return __builtin_bcmp (&freq, &freq, 10);
}
101 - 200 of 241 matches
Mail list logo