https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104475
--- Comment #15 from Richard Biener ---
Thanks, it's still the same reason - we isolate a nullptr case and end up with
__atomic_or_fetch_4 (184B, 64, 0); [tail call]
The path we isolate is d->m_mutex == nullptr && !enable in
void QFutureInter
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104475
--- Comment #16 from Richard Biener ---
The odd thing is that we do
/* Pointer constants other than null smaller than param_min_pagesize
might be the result of erroneous null pointer addition/subtraction.
Unless zero is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107975
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:0525a7fad2a5b1d933a9662c11aa074b38cfa3d5
commit r13-4501-g0525a7fad2a5b1d933a9662c11aa074b38cfa3d5
Author: Jakub Jelinek
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107972
--- Comment #2 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:a0ee2e522523b35ac810bd31c9769b9906f87953
commit r13-4502-ga0ee2e522523b35ac810bd31c9769b9906f87953
Author: Jakub Jelinek
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107976
Richard Biener changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107986
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107987
Bug ID: 107987
Summary: [12/13 Regression] MVE vcmpq vector-scalar can trigger
ICE
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107975
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107986
--- Comment #6 from rguenther at suse dot de ---
On Tue, 6 Dec 2022, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107986
>
> Jakub Jelinek changed:
>
>What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107986
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107987
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |12.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107972
Jakub Jelinek changed:
What|Removed |Added
CC||amacleod at redhat dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104475
--- Comment #17 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:926f5059bb8d295e2b68cea7c9af53606946eb1a
commit r13-4503-g926f5059bb8d295e2b68cea7c9af53606946eb1a
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104475
--- Comment #18 from Richard Biener ---
The change improved the wording of the diagnostic by appending the note
indicating an object at zero address. It didn't mitigate the diagnostic which
as far as I analyzed is technically correct (but not v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107046
--- Comment #8 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:8872df353884fec6d7ff0e8bf8eee356439ec8d8
commit r13-4504-g8872df353884fec6d7ff0e8bf8eee356439ec8d8
Author: Jakub Jelinek
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107969
--- Comment #5 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:bcf89f05f7b0b1732553e224548f1de55321e437
commit r13-4505-gbcf89f05f7b0b1732553e224548f1de55321e437
Author: Jakub Jelinek
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107969
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r13-4497-20221206065114-g769370f3e2e-checking-yes-rtl-df-extra-aarch64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.0.0 20221206 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107970
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |crazylht at gmail dot
com
64-pc-linux-gnu --target=aarch64-unknown-linux-gnu
--with-ld=/usr/bin/aarch64-unknown-linux-gnu-ld
--with-as=/usr/bin/aarch64-unknown-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r13-4497-20221206065114-g769370f3e2e-checking-yes-rtl-df-extra-aarch64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.0.0 20221206 (experimental) (GCC)
/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r13-4497-20221206065114-g769370f3e2e-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.0.0 20221206 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107989
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107989
--- Comment #2 from Zdenek Sojka ---
(In reply to Jakub Jelinek from comment #1)
> Is this with r13-4501-g0525a7fad2a5b1d or later? If not, it is a dup of
> PR107975.
Thank you for the reply. This is with r13-4497, so a dup of PR107975.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107988
ktkachov at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2022-12-06
Ever confir
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107989
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107975
Jakub Jelinek changed:
What|Removed |Added
CC||zsojka at seznam dot cz
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107987
--- Comment #1 from CVS Commits ---
The master branch has been updated by Andre Simoes Dias Vieira
:
https://gcc.gnu.org/g:ed34c3bc3428bce663d42e9eeda10bc0c5d56d5c
commit r13-4506-ged34c3bc3428bce663d42e9eeda10bc0c5d56d5c
Author: Andre Vieira
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107991
Bug ID: 107991
Summary: Extra mov instructions with ternary on x86
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107988
Tamar Christina changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |tnfchris at gcc dot
gnu.org
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107992
Bug ID: 107992
Summary: m68k-linux-gnu bootstap error in gofrontend
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106323
--- Comment #4 from vfdff ---
Now, llvm use 4 loads and CMP+CCMP, https://gcc.godbolt.org/z/PM3jxEM9M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107980
--- Comment #5 from Aaron Ballman ---
(In reply to Andrew Pinski from comment #3)
> I think we should warn but how to warn is going to have to special case the
> macro I think.
I was contemplating a perhaps terrible idea of adding some new buil
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107980
--- Comment #6 from Andrew Pinski ---
Maybe add a _Static_warn builtin instead which is like _Static_assert but
instead of an error, it is a warning.
That is:
#define va_start(ap, ...) (_Static_warn(__builtin_va_opt_count(__VA_OPT__) <=
1, "Mor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107980
--- Comment #7 from Jakub Jelinek ---
Why do you need a builtin for counting number of arguments in __VA_OPT__?
That can be done in the preprocessor. All one needs is 1, 2 or more arguments.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106719
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107985
Aldy Hernandez changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107980
--- Comment #8 from Aaron Ballman ---
(Sorry, I meant __VA_ARGS__ and not __VA_OPT__; C23 on the brain!)
(In reply to Andrew Pinski from comment #6)
> Maybe add a _Static_warn builtin instead which is like _Static_assert but
> instead of an err
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107985
--- Comment #3 from Aldy Hernandez ---
Another alternative would be to add an is_a/as_a handler for unsupported_type's
in value-range.h and a corresponding entry for unsupported types in
range_operator:
virtual bool fold_range (irange &r, tree
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107980
--- Comment #9 from Aaron Ballman ---
Btw, a similar issue in this area is that GCC no longer diagnoses when the user
passes a second argument to va_start in C2x mode and the argument is not the
parameter before the ellipsis. e.g.,
```
#include
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107985
--- Comment #4 from Andrew Macleod ---
the gimple_range_op_handler constructor should check the operands for supported
types as well before setting m_valid.
There is also a ripple effect in gimple_ranger::prefill_stmt_dependencies where
the ass
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107980
--- Comment #10 from Jakub Jelinek ---
That again is completely valid in C2X.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107967
--- Comment #7 from Jakub Jelinek ---
Ok, I can reproduce this, disabling all the +-*/ handlers fixes it.
It isn libm.so.6 that matters for the failures, not the tests themselves.
So far I've looked at the expm1 stuff, the failures are:
Failure:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107980
--- Comment #11 from Aaron Ballman ---
(In reply to Jakub Jelinek from comment #10)
> That again is completely valid in C2X.
Yes, it is. And again, it's still something worth diagnosing (IMO) because it's
utter nonsense code that is invalid wit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107991
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Version|unknown
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107988
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107991
Andrew Pinski changed:
What|Removed |Added
Known to fail||8.1.0
Component|rtl-optimizati
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107985
--- Comment #5 from Aldy Hernandez ---
(In reply to Andrew Macleod from comment #4)
> the gimple_range_op_handler constructor should check the operands for
> supported types as well before setting m_valid.
>
> There is also a ripple effect in g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107967
--- Comment #8 from Jakub Jelinek ---
Actually, looking at:
288 // Be extra careful if there may be discrepancies between the
289 // compile and runtime results.
290 if ((mode_composite || (real_isneg (&inf) ? real_less (&resul
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107993
Bug ID: 107993
Summary: ICE: tree check: expected string_cst, have integer_cst
in get_target_clone_attr_len, at tree.cc:14872
Product: gcc
Version: 13.0
Status: UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104475
--- Comment #19 from Thiago Macieira ---
(In reply to Richard Biener from comment #15)
> Thanks, it's still the same reason - we isolate a nullptr case and end up
> with
>
> __atomic_or_fetch_4 (184B, 64, 0); [tail call]
>
> The path we isolat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107994
Bug ID: 107994
Summary: [12/13 Regression] ICE in fold_convert_loc, at
fold-const.cc:2606
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107995
Bug ID: 107995
Summary: ICE: Segmentation fault, without backtrace
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107996
Bug ID: 107996
Summary: ICE in gfc_walk_array_ref, at
fortran/trans-array.cc:11429
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107996
G. Steinmetz changed:
What|Removed |Added
Keywords||ice-on-invalid-code,
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107994
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2022-12-06
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107843
--- Comment #1 from David Faust ---
Looks like this is an issue with passing void* where an enum type is
expected in a function call. This is not specific to the BPF backend.
Not entirely clear to me whether this is expected or a bug, but it
do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106325
--- Comment #7 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:dcfc7ac94dbcf6c86c0c58ce6dc1d8bd853e4093
commit r13-4520-gdcfc7ac94dbcf6c86c0c58ce6dc1d8bd853e4093
Author: David Malcolm
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107441
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107993
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106325
--- Comment #8 from David Malcolm ---
Should be fixed on trunk for GCC 13 by the above patch.
Still affects GCC 12, GCC 11, and GCC 10.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107994
--- Comment #2 from Andrew Pinski ---
This should fix the issue (have not tested it yet):
diff --git a/gcc/gimplify.cc b/gcc/gimplify.cc
index 02415cb1b5c..ae13f9fd9e6 100644
--- a/gcc/gimplify.cc
+++ b/gcc/gimplify.cc
@@ -17098,6 +17098,9 @@ gi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107967
--- Comment #9 from Jakub Jelinek ---
Created attachment 54029
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54029&action=edit
gcc13-pr107967.patch
Untested fix. Deferring the mode_composite stuff for later.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107882
David Malcolm changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #3 from David Malc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106434
--- Comment #11 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:4ba94abf147fe7778a7541849ce27cafee74df9b
commit r13-4525-g4ba94abf147fe7778a7541849ce27cafee74df9b
Author: Jonathan Wakely
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107871
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:9cce91a63dcc40cb39e68f6a771e891e51c51946
commit r13-4527-g9cce91a63dcc40cb39e68f6a771e891e51c51946
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107979
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:2a23b93f944fa78d4284eb5687051c224e5ab08f
commit r13-4528-g2a23b93f944fa78d4284eb5687051c224e5ab08f
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107979
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107871
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106856
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=107997
Bug ID: 107997
Summary: fd8dd6c03849691 probably uncovered an issue building
the Linux kernel
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: norma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107998
Bug ID: 107998
Summary: [13 Regression] gcc-13-20221204 failure to build on
Cygwin No dirname for option: m32
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Se
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107882
--- Comment #4 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:dfe2ef7f2b6cac7017f32a0a04f74e1b6d9f1311
commit r13-4529-gdfe2ef7f2b6cac7017f32a0a04f74e1b6d9f1311
Author: David Malcolm
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107998
--- Comment #1 from James McKelvey ---
Created attachment 54032
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54032&action=edit
Config log
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107882
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107998
--- Comment #2 from James McKelvey ---
Configured with:
./configure --enable-languages=c,c++ --enable-threads=posix
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107998
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
Component|bootstrap
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107997
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-valid-code
Component|re
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106611
--- Comment #6 from Nikolas Klauser ---
Is there any update on this?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107770
--- Comment #1 from CVS Commits ---
The master branch has been updated by Antoni Boucher :
https://gcc.gnu.org/g:d2e782cb99c3116c389d6a9565678c4ffe26
commit r13-4531-gd2e782cb99c3116c389d6a9565678c4ffe26
Author: Antoni Boucher
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107999
Bug ID: 107999
Summary: test-error-array-bounds.c now fails because
[-Warray-bounds] was updated to [-Warray-bounds=] in
error messages
Product: gcc
Version: 12.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107954
--- Comment #3 from joseph at codesourcery dot com ---
Editorial review before the CD ballot slipped the schedule. Second-round
editorial review after a huge number of changes in the editorial review
slipped the schedule. Getting a final dra
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107770
Antoni changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107999
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
Summary|test-error-arra
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108000
Bug ID: 108000
Summary: Assert during ipa-cp with AutoFDO
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107980
--- Comment #12 from joseph at codesourcery dot com ---
The standard rule about not using extra arguments means that any warnings
would need to avoid even converting those arguments from pp-tokens to
tokens; it's OK for them to contain pp-toke
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108000
--- Comment #1 from Andrew Pinski ---
Can you provide the exact command lines being used and does it fail during
while using the profile or before?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108000
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2022-12-07
Status|UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108000
--- Comment #2 from Eugene Rozenfeld ---
I actually have a fix for this, just wanted to file a simple test case. I
initially ran into this failure while reviving autoprofiledbootstrap build. The
failure happens while using the profile and the bu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105050
--- Comment #7 from Andrew Pinski ---
I think clang still gives a better error message here though:
:43:15: error: static assertion expression is not an integral constant
expression
static_assert(test_swap());
^~~
:18:17: n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105050
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107970
--- Comment #2 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:da7fb32d403759daefefc79dc251d2437c1b638c
commit r13-4532-gda7fb32d403759daefefc79dc251d2437c1b638c
Author: liuhongt
Date: Tue Dec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107970
Hongtao.liu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107967
--- Comment #10 from caiyinyu ---
(In reply to Jakub Jelinek from comment #9)
> Created attachment 54029 [details]
> gcc13-pr107967.patch
>
> Untested fix. Deferring the mode_composite stuff for later.
There are still some fails and errors ar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105047
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103302
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
--- Comment #18 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105049
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
Summary|ICE: in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104975
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105059
Andrew Pinski changed:
What|Removed |Added
Keywords|accepts-invalid |documentation
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106708
--- Comment #1 from Jiu Fu Guo ---
PR93178 also mentioned the "li,oris" case.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18474
--- Comment #2 from Andrew Pinski ---
Note this is only invalid as n (if declared correctly) was not depedent so the
operator lookup would be bound at definition time.
That is the following needs to be accepted still:
template
void g(void)
{
1 - 100 of 121 matches
Mail list logo
