https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19249
Andrew Pinski changed:
What|Removed |Added
Known to fail||
--- Comment #10 from Andrew Pinski ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103603
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |11.3
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103607
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |9.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103609
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |11.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103606
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |9.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103522
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100736
HaoChen Gui changed:
What|Removed |Added
CC||guihaoc at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103571
--- Comment #10 from Hongtao.liu ---
(In reply to Uroš Bizjak from comment #9)
> (In reply to Hongtao.liu from comment #8)
> > (In reply to Uroš Bizjak from comment #6)
> > > (In reply to Hongtao.liu from comment #5)
> > >
> > > > There're seve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87438
Andrew Pinski changed:
What|Removed |Added
CC||siddhesh at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103613
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103571
--- Comment #9 from Uroš Bizjak ---
(In reply to Hongtao.liu from comment #8)
> (In reply to Uroš Bizjak from comment #6)
> > (In reply to Hongtao.liu from comment #5)
> >
> > > There're several places in i386-expand.c which assume TARGET_AVX51
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100738
Hongtao.liu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100738
--- Comment #5 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:691f05c2197a7b79cb2d7fdbabe3182e22da320a
commit r12-5832-g691f05c2197a7b79cb2d7fdbabe3182e22da320a
Author: Haochen Jiang
Date: Thu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103571
--- Comment #8 from Hongtao.liu ---
(In reply to Uroš Bizjak from comment #6)
> (In reply to Hongtao.liu from comment #5)
>
> > There're several places in i386-expand.c which assume TARGET_AVX512FP16 for
> > case V8HF/V16HF/V32HF, if we want to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103614
Bug ID: 103614
Summary: Modulo equality optimization
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103613
Bug ID: 103613
Summary: microblaze: ICE in reload pass when building PIE
Product: gcc
Version: 11.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91247
--- Comment #4 from Mario Galindo ---
It has been fixed fixed in GCC 10.2.0 and GCC 11+
Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103612
--- Comment #2 from Pablo ---
(In reply to Andrew Pinski from comment #1)
> Dup of bug 101152 ?
No, I don't think so. Here the problem is %y acts like %Y, it uses 4 digits of
the input, and It doesn't produce an error even in the case where the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103302
--- Comment #10 from Alexandre Oliva ---
Created attachment 51947
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51947&action=edit
candidate patch under testing
Could the fix be as simple as this?
The resulting code is awful, with such s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92662
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71369
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71369
Andrew Pinski changed:
What|Removed |Added
Keywords||diagnostic
--- Comment #2 from Andrew Pi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90652
--- Comment #1 from Andrew Pinski ---
With a "fixed" source to the new syntax of concepts I get:
: In substitution of 'template requires (ToJson) &&
!(Serializable) std::ostream& operator<<(std::ostream&, const T&) [with T =
char]':
:5:86: req
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103612
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103612
Bug ID: 103612
Summary: get_time parsing error for two digits year
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: li
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103603
--- Comment #5 from Andrew Macleod ---
Yes, there is an updated patch that bootstraps posted here for approval:
https://gcc.gnu.org/pipermail/gcc-patches/2021-December/586351.html
Give it a go.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103611
--- Comment #4 from John Platts ---
(In reply to Andrew Pinski from comment #3)
> Hmm, GCC 4.8.1-5.5.0 produces:
> long long SSE2ExtractInt64<0>(long long __vector):
> .LFB499:
> .cfi_startproc
> pshufd xmm1, xmm0, 1
> m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103611
--- Comment #3 from Andrew Pinski ---
Hmm, GCC 4.8.1-5.5.0 produces:
long long SSE2ExtractInt64<0>(long long __vector):
.LFB499:
.cfi_startproc
pshufd xmm1, xmm0, 1
movdeax, xmm0
movdedx, xmm1
ret
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103149
Alexandre Oliva changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103149
--- Comment #3 from CVS Commits ---
The master branch has been updated by Alexandre Oliva :
https://gcc.gnu.org/g:0485ce9128f272fe7ccb48672f69d7be6bb26a9c
commit r12-5831-g0485ce9128f272fe7ccb48672f69d7be6bb26a9c
Author: Alexandre Oliva
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103611
--- Comment #2 from John Platts ---
Here is some code for extracting 64-bit integers from a SSE2 vector using GCC
vector extensions:
#include
#include
using Int64M128Vect [[__gnu__::__vector_size__(16)]] = std::int64_t;
template
std::int64_t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103611
--- Comment #1 from John Platts ---
Here is some C++ code for extracting 64-bit integers from a __m128i vector
using SSE4.1:
#include
#include
template
std::int64_t SSE41ExtractInt64(__m128i vect) noexcept {
static_assert(ElemIdx == (Elem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103611
Bug ID: 103611
Summary: GCC generates suboptimal code for SSE2/SSE4.1 64-bit
integer element extraction on 32-bit x86 targets
Product: gcc
Version: 11.2.0
Status: UNCONF
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103600
--- Comment #7 from Jonathan Wakely ---
Created attachment 51946
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51946&action=edit
libstdc++: Implement P1328 "Making std::type_info::operator== constexpr"
Jakub, that patch works for me. Her
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103603
--- Comment #4 from Kito Cheng ---
Hi Andrew:
Thanks for your quick response! the patch is work to me for the testcase,
but...I got seg fault when I built x86 GCC.
Here is a reduced case from gcov, and this testcase also take longer
compilatio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98782
--- Comment #15 from Tamar Christina ---
> That is, we're trading two memory accesses in the call branch
> (if we allocate R) against one memory access in both branches
> (if we spill R). As the call branch gets more likely,
> the cost of doing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101152
--- Comment #3 from Jonathan Wakely ---
It's not essential, but I think that would be helpful
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103610
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=103607
--- Comment #2 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:9eec77c0df9e5c67454a2e8f83246104458ba4f0
commit r12-5829-g9eec77c0df9e5c67454a2e8f83246104458ba4f0
Author: Harald Anlauf
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79452
--- Comment #12 from Jonathan Wakely ---
Well this request is satisfied by std::is_constant_evaluated() in C++20, which
is what __builtin_is_constant_evaluated() exists for. PR 100974 adds a newer
C++23 language feature that makes std::is_constan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103610
--- Comment #3 from anlauf at gcc dot gnu.org ---
Tentative patch:
diff --git a/gcc/fortran/array.c b/gcc/fortran/array.c
index e5e22099405..a23fabbdcdb 100644
--- a/gcc/fortran/array.c
+++ b/gcc/fortran/array.c
@@ -2330,6 +2330,9 @@ spec_dimen_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103370
--- Comment #4 from Joseph S. Myers ---
It seems this glibc build failure disappeared between commit
b880d1514c1e3dd75a6ea311a5cc956742bd713c and commit
8e836af61b7027c0819da62c12a8d18b7c46f3fc. (Not verified that the GCC change
was what's rele
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103610
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=103586
Peter Bergner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103607
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103556
Peter Bergner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103556
--- Comment #2 from CVS Commits ---
The master branch has been updated by Peter Bergner :
https://gcc.gnu.org/g:4394fd67264f5de650c2c3509c001c5f7203449d
commit r12-5827-g4394fd67264f5de650c2c3509c001c5f7203449d
Author: Peter Bergner
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103586
--- Comment #3 from CVS Commits ---
The master branch has been updated by Peter Bergner :
https://gcc.gnu.org/g:4394fd67264f5de650c2c3509c001c5f7203449d
commit r12-5827-g4394fd67264f5de650c2c3509c001c5f7203449d
Author: Peter Bergner
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103364
--- Comment #24 from Sarah Julia Kriesch ---
There can be a dependency to this kernel bug:
https://bugzilla.suse.com/show_bug.cgi?id=1188896
We want to integrate the patch from your colleague and look, what will be
changed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103444
--- Comment #4 from kargl at gcc dot gnu.org ---
This is as far as I have gotten on this bug. I don't know if
this is a race condition in libgfortran's async_close(), a
problem with gcc internal threading modeling (i.e., __gthrw_),
and problem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101962
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90341
Andrew Pinski changed:
What|Removed |Added
Keywords||needs-reduction
Status|WAITI
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71527
Andrew Pinski changed:
What|Removed |Added
Known to work||10.1.0, 9.1.0
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103610
G. Steinmetz changed:
What|Removed |Added
Keywords||ice-on-invalid-code
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103610
Bug ID: 103610
Summary: ICE in gfc_convert_mpz_to_signed, at
fortran/simplify.c:193
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98782
--- Comment #14 from rsandifo at gcc dot gnu.org
---
Thanks for the nice cut-down example.
In the original comment and the covering note to patch 1,
the highlighted spilled value is the final (terminating)
value of foo + 1024. Let's start with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103609
G. Steinmetz changed:
What|Removed |Added
Keywords||ice-on-invalid-code
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103609
Bug ID: 103609
Summary: [11/12 Regression] ICE in gfc_sym_get_dummy_args, at
fortran/symbol.c:5243
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: nor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103608
Bug ID: 103608
Summary: ICE in do_intent, at fortran/frontend-passes.c:3035
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103607
Bug ID: 103607
Summary: [9/10/11/12 Regression] ICE in do_subscript, at
fortran/frontend-passes.c:2927
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103606
G. Steinmetz changed:
What|Removed |Added
Keywords||ice-on-invalid-code
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103606
Bug ID: 103606
Summary: [9/10/11/12 Regression] ICE in resolve_fl_procedure,
at fortran/resolve.c:13297
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66641
Andrew Pinski changed:
What|Removed |Added
Depends on||101582
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101582
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66641
Andrew Pinski changed:
What|Removed |Added
Known to fail||11.2.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100974
Andrew Pinski changed:
What|Removed |Added
CC||gonzalo.gadeschi at gmail dot
com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79452
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69836
--- Comment #3 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #2)
> I wonder if this is just invalid code but no diagnostic required as state
> changes inside the scope of TemplateObject.
That is it needs to be reinterpret it aft
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103597
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=69836
--- Comment #2 from Andrew Pinski ---
I wonder if this is just invalid code but no diagnostic required as state
changes inside the scope of TemplateObject.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101152
--- Comment #2 from Jordi Vilar ---
(In reply to Jonathan Wakely from comment #1)
> I think the bug is that it treats 03 as 1903 instead of 0003. It is not
> supposed to print "N/A" though.
>
> %Y doesn't require exactly 4 digits, it allows 1-4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103597
--- Comment #5 from Jakub Jelinek ---
Completely untested patch to set the flag when a label is only known reachable
through fallthrough from previous instructions, never jumped to, as the only
goto to it is on a non-executable branch of GIMPLE_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103556
Peter Bergner changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83469
Andrew Pinski changed:
What|Removed |Added
Keywords||patch
URL|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93809
Andrew Pinski changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103588
--- Comment #4 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:652c28736209f10bac1aa7ecb31f9056b518dacf
commit r12-5826-g652c28736209f10bac1aa7ecb31f9056b518dacf
Author: Harald Anlauf
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103591
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103591
--- Comment #4 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:f47662204de27f7685699eeef89aa173ccf32d85
commit r12-5825-gf47662204de27f7685699eeef89aa173ccf32d85
Author: Harald Anlauf
Date: M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101152
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71557
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103586
Peter Bergner changed:
What|Removed |Added
Status|NEW |ASSIGNED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103598
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103600
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103605
--- Comment #1 from pc at gcc dot gnu.org ---
$ cat fmin.c
#include
double fm (double d0, double d1) {
return fmin (d0, d1);
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103605
Bug ID: 103605
Summary: [PowerPC] fmin/fmax should be inlined always with
xsmindp/xsmaxdp
Product: gcc
Version: 11.2.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103545
pc at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |pc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103603
--- Comment #3 from Andrew Macleod ---
Created attachment 51944
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51944&action=edit
Ported patch
See if this works. I'll run it through testing, but this should be a port of
the patches from PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103553
--- Comment #2 from Marek Polacek ---
Yes, I added that in GCC 11.
To make this work, I think we'll have to print parser->scope when there's one.
In this case it's
full-name "struct is_same"
so that could be extracted and used in finish_stat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84516
Bug 84516 depends on bug 95009, which changed state.
Bug 95009 Summary: [9/10 Regression] decltype of increment or decrement
bitfield expressions are wrong and causes assembler errors.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95009
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70733
Bug 70733 depends on bug 95009, which changed state.
Bug 95009 Summary: [9/10 Regression] decltype of increment or decrement
bitfield expressions are wrong and causes assembler errors.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95009
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95009
Marek Polacek changed:
What|Removed |Added
Summary|[9/10/11 Regression]|[9/10 Regression] decltype
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95009
--- Comment #7 from CVS Commits ---
The releases/gcc-11 branch has been updated by Marek Polacek
:
https://gcc.gnu.org/g:e3fab19a79e3dc3cdf3e54ca20107e1dc15a3927
commit r11-9363-ge3fab19a79e3dc3cdf3e54ca20107e1dc15a3927
Author: Marek Polacek
D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103593
--- Comment #4 from Marek Polacek ---
Yup, just the diagnostic is really bad because I still haven't fixed bug 97202
:(
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103593
Patrick Palka changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103603
--- Comment #2 from Kito Cheng ---
Oh, apologize for misleading, it should fixed via pr103231 rather than
pr103254.
it work after g:5deacf6058d1bc7261a75c9fd1f116c4442e9e60, no new file, but it's
not trivial backport-able.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103593
Patrick Palka changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95009
Marek Polacek changed:
What|Removed |Added
Summary|[9/10/11/12 Regression] |[9/10/11 Regression]
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99531
--- Comment #4 from Vladimir Makarov ---
Thank you for reporting this. It is true my patch caused this.
I've reproduced the bug on master too. I will be working on this PR. I
think a fix will be ready on the next week the best as the fix
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103600
--- Comment #5 from Jonathan Wakely ---
The new definition of operator== will be something like:
#if __GXX_TYPEINFO_EQUALITY_INLINE || __cplusplus > 202002L
_GLIBCXX23_CONSTEXPR inline bool
type_info::operator==(const type_info& __arg) cons
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103604
Martin Liška changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
1 - 100 of 194 matches
Mail list logo