https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116510
--- Comment #13 from rguenther at suse dot de ---
On Tue, 15 Oct 2024, ak at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116510
>
> --- Comment #12 from ak at gcc dot gnu.org ---
> Like this? It fixes the test case.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117128
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117166
--- Comment #1 from Sam James ---
It's very sensitive even if e.g. copying all the headers locally. Rather than
faff more, I'll try reduce it by hand first.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117159
--- Comment #2 from Hongtao Liu ---
typedef __attribute__((__vector_size__ (4))) unsigned char W;
typedef __attribute__((__vector_size__ (64))) int V;
typedef __attribute__((__vector_size__ (64))) long long Vq;
W w;
V v;
Vq vq;
static inline W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117166
Bug ID: 117166
Summary: [15 regression] ICE when building lxml-5.3.0 with LTO
(linemap_line_start, at libcpp/line-map.cc:949)
Product: gcc
Version: 15.0
Status: UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113952
Sam James changed:
What|Removed |Added
Keywords||patch
--- Comment #2 from Sam James ---
Pa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117165
Bug ID: 117165
Summary: ICE: in extract_insn, at recog.c:2311 unrecognizable
insn: UNSPECV_FNSTSW with -mgeneral-regs-only and
__builtin_ia32_fnstsw()
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108250
Sam James changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117159
Hongtao Liu changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |liuhongt at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115365
--- Comment #9 from GCC Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:a8b4ea1bcc10b5253992f4b932aec6862aef32fa
commit r15-4371-ga8b4ea1bcc10b5253992f4b932aec6862aef32fa
Author: liuhongt
Date: Tue Oct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116994
Davide Italiano changed:
What|Removed |Added
CC||lingling.kong7 at gmail dot com
--- C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117150
Eric Gallager changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117156
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
--- Comment #5 from Andrew Pinski ---
Also bugzilla is not to track already submitted patches.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
--- Comment #4 from Andrew Pinski ---
https://gcc.gnu.org/pipermail/gcc-patches/2024-July/657957.html
Adding a new macro for GCC 15 won't fix many many older compilers out there. So
most code will still use the old name for many many years to c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117162
Joseph S. Myers changed:
What|Removed |Added
Last reconfirmed||2024-10-16
Status|UNCONFI
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
--- Comment #3 from Paul Caprioli ---
Note that this is not for me; it's for everybody else.
The idea is for this to be the standard macro for specifying the IEEE rounding
to nearest attribute `roundTiesToEven`.
My contacts at Intel tell me the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117164
Bug ID: 117164
Summary: ICE building gcc.dg/nested-func-12.c with -std=gnu23
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
Bug ID: 117163
Summary: Missing macro to round to nearest floating-point value
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212
--- Comment #401 from Oleg Endo ---
It seems there is a silent wrong-code bug somewhere when building some
Dreamcast projects with LRA and LTO enabled. It results in wrong graphics
being output. So far could not isolate the wrong-code though.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117008
--- Comment #15 from Matt Bentley ---
Created attachment 59356
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59356&action=edit
.ii file for bool[array] causing same issue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117008
--- Comment #14 from Matt Bentley ---
Created attachment 59355
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59355&action=edit
.ii file for vector code causing same issue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117008
--- Comment #13 from Matt Bentley ---
Bool C-arrays also display the same problem, but only if a warm-up loop is
present before the main loop (to 'warm up' the cache). I discovered this by
accident the other day. char arrays and int arrays did n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117123
Davide Italiano changed:
What|Removed |Added
CC||pheeck at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117162
Bug ID: 117162
Summary: Universal character names designating members of the
basic character set or control characters should be
allowed in string literals or character constants
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116016
Sam James changed:
What|Removed |Added
Target Milestone|--- |15.0
--- Comment #69 from Sam James ---
Th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96974
Andrew Pinski changed:
What|Removed |Added
CC||Robert.Hardwick at arm dot com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117161
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116016
qinzhao at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117161
--- Comment #1 from Robert Hardwick ---
Created attachment 59354
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59354&action=edit
Preprocessed source stored into /tmp/ccEF5DEn.out file, please attach this to
your bugreport.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117161
Bug ID: 117161
Summary: internal compiler error: in
vect_get_vector_types_for_stmt, at
tree-vect-stmts.c:12252 on gcc 10.2 for aarch64+sve
Product: gcc
Version:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116016
--- Comment #67 from GCC Commits ---
The master branch has been updated by Qing Zhao :
https://gcc.gnu.org/g:e7380688fa5917011c3fb85b5e06fb00f776a95d
commit r15-4370-ge7380688fa5917011c3fb85b5e06fb00f776a95d
Author: Qing Zhao
Date: Tue Oct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117160
Bug ID: 117160
Summary: [15 regression] GCC trunk generates larger code than
GCC 14 at -Os/-Oz (progressed in 14)
Product: gcc
Version: 15.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115328
--- Comment #2 from Gaius Mulley ---
Created attachment 59353
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59353&action=edit
Proposed fix
Here is a proposed fix, which passes all regressions and implements the FORWARD
keyword. It also
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117022
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|--- |15.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117022
--- Comment #5 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:50f27896adb272b40ab03a56fd192e74789bef97
commit r15-4369-g50f27896adb272b40ab03a56fd192e74789bef97
Author: Jakub Jelinek
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116876
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111645
--- Comment #7 from Carl Love ---
Patch committed that add the signed __int128 and unsigned __int128 argument
types for the
overloaded built-ins vec_sld, vec_sldb, vec_sldw, vec_sll, vec_slo, vec_srdb,
vec_srl,
vec_sr0 built-ins was committed:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80637
--- Comment #7 from GCC Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:b110e092d260906432931796c1d96cba305c60e4
commit r15-4368-gb110e092d260906432931796c1d96cba305c60e4
Author: Patrick Palka
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116891
--- Comment #12 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:4366f0c7e296ea0d7279343c9b0a1d597588a1da
commit r15-4367-g4366f0c7e296ea0d7279343c9b0a1d597588a1da
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116710
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
Ass
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116710
--- Comment #1 from GCC Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:8161c4adea7f1842f9d28633d82e912ebb7a4cf9
commit r15-4366-g8161c4adea7f1842f9d28633d82e912ebb7a4cf9
Author: Patrick Palka
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117054
--- Comment #3 from GCC Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:bb2bfdb2048aed18ef7dc01b51816a800e83ce54
commit r15-4365-gbb2bfdb2048aed18ef7dc01b51816a800e83ce54
Author: Patrick Palka
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116510
--- Comment #12 from ak at gcc dot gnu.org ---
Like this? It fixes the test case.
I'm not sure why you want AND_EXPR, this is a truth formula. Maybe it should be
TRUTH_ANDIF_EXPR though to short circuit.
diff --git a/gcc/tree-if-conv.cc b/gcc/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117128
Sam James changed:
What|Removed |Added
Summary|[15 regression] GCC trunk |[15 regression] GCC trunk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117145
Sam James changed:
What|Removed |Added
Keywords|needs-bisection |
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117152
--- Comment #4 from David Malcolm ---
It's happening here:
(gdb) bt
#0 0x00f95395 in dump_function_name (pp=0x4d00c40
, t=, flags=148)
at ../../src/gcc/cp/error.cc:2139
#1 0x00f94109 in dump_function_decl (pp=0x4d00c40
, t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117159
Bug ID: 117159
Summary: kmovw storing to memory is assumed to zero-extend
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117128
Davide Italiano changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117157
--- Comment #4 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:a72064c8c12f2cc3ab6fde7cd42f31f27193b5c4
commit r15-4363-ga72064c8c12f2cc3ab6fde7cd42f31f27193b5c4
Author: Andrew Pinski
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116627
Frank Scheiner changed:
What|Removed |Added
CC||frank.scheiner at web dot de
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117158
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
Target Mi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111425
Frank Scheiner changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117158
Bug ID: 117158
Summary: ICE with array access inside a template with a base
class
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117141
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113341
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |MOVED
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117154
--- Comment #6 from Carlos Galvez ---
Alright reading Richard's comment I now understand he's not implying current
behavior is correct, but rather explaining why it happens. I take it then that
this is a bug in Clang then. Thanks for the clarifi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109642
Andrew Pinski changed:
What|Removed |Added
CC||dimitry@unified-streaming.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117155
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117156
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117157
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |15.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117157
--- Comment #2 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:11f0ea45b1b63ec7eb6a52179ca6fd4304e7e312
commit r15-4362-g11f0ea45b1b63ec7eb6a52179ca6fd4304e7e312
Author: Andrew Pinski
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117116
--- Comment #16 from Uroš Bizjak ---
Fixed on mainline, will be backported to other release branches.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117157
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-10-15
Assignee|unassigne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117156
--- Comment #4 from mauro russo ---
ok, thank you.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117157
Bug ID: 117157
Summary: changes-meaning is not in the index
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: documentation
Severity: normal
Priority: P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117116
--- Comment #15 from GCC Commits ---
The master branch has been updated by Uros Bizjak :
https://gcc.gnu.org/g:80d7032067a3a5b76aecd657d9b35b0a8f5a941d
commit r15-4359-g80d7032067a3a5b76aecd657d9b35b0a8f5a941d
Author: Uros Bizjak
Date: Tue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117154
--- Comment #5 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #4)
> (and Richard Smith aid so in
*said so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117156
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117154
--- Comment #4 from Jonathan Wakely ---
Why should access to a protected destructor be different to access to a
protected constructor? It's obviously related (and Richard Smith aid so in the
llvm issue too).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117156
--- Comment #2 from Jonathan Wakely ---
The post should say -Wno-changes-meaning disables it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117156
--- Comment #1 from Jonathan Wakely ---
The blog post is wrong, GCC is behaving as intended.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117154
--- Comment #3 from Carlos Galvez ---
Please note that this ticket is about protected *destructor*. For protected
*constructor*, clang has same behavior as GCC.
CWG 2244 does not appear to consider this case?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80881
--- Comment #67 from Julian Waters ---
Command line used in compiling the reproducer: xgcc -O2 -S -std=c11 -pedantic
-Wpedantic tls.c
The thing that has me puzzled is that the main differences between both patches
are in the load of the primary
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115444
--- Comment #11 from Jonathan Wakely ---
Patch posted:
https://gcc.gnu.org/pipermail/gcc-patches/2024-October/665537.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114817
--- Comment #5 from Jonathan Wakely ---
Patch posted:
https://gcc.gnu.org/pipermail/gcc-patches/2024-October/665537.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117156
Bug ID: 117156
Summary: not applied option “-Wchanges-meaning”
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68350
Jonathan Wakely changed:
What|Removed |Added
Keywords||patch
--- Comment #17 from Jonathan Wa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108770
--- Comment #3 from qinzhao at gcc dot gnu.org ---
With my patch for new option -fdiagnostics-explain-harder, the output is:
t_108770.c: In function ‘init’:
t_108770.c:10:13: warning: array subscript 2 is above array bounds of ‘const
char *[2]’
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117142
Sam James changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
Summ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84884
--- Comment #2 from Andrew Pinski ---
https://wg21.link/cwg2244
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84884
Andrew Pinski changed:
What|Removed |Added
See Also||https://github.com/llvm/llv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117154
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84884
Andrew Pinski changed:
What|Removed |Added
CC||carlosgalvezp at gmail dot com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117155
--- Comment #3 from Dimitry Andric ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to Dimitry Andric from comment #0)
> > After r15-3941-g2531f014fb2364 ("c++: Implement -Wdangling-reference
>
> I think the correct commit is
> r13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117155
--- Comment #2 from Jonathan Wakely ---
(In reply to Dimitry Andric from comment #0)
> Clearly, there is no dangling reference here, and not even a temporary. And
> even if there was a temporary, its lifetime should have been extended.
No, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117155
--- Comment #1 from Jonathan Wakely ---
(In reply to Dimitry Andric from comment #0)
> After r15-3941-g2531f014fb2364 ("c++: Implement -Wdangling-reference
I think the correct commit is
r13-3511-gd2249cd9adf5ae638577139177a50f7e62d8abd9
> [PR1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106676
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83417
Jason Merrill changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117154
--- Comment #1 from Jonathan Wakely ---
This is https://wg21.link/cwg2244 and it looks like GCC already implements the
suggested resolution.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106676
--- Comment #14 from GCC Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:7f65f94917866c6b18d9698eec6451c1bf21e0f9
commit r15-4356-g7f65f94917866c6b18d9698eec6451c1bf21e0f9
Author: Jonathan Wakely
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67491
Bug 67491 depends on bug 80637, which changed state.
Bug 80637 Summary: [CWG2918] constraint on a member function does causes
ambigious and not allowing forming a pointer to the function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80637
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80637
Jason Merrill changed:
What|Removed |Added
Resolution|--- |FIXED
Summary|constraint on a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117155
Bug ID: 117155
Summary: Bogus -Wdangling-reference warning after
r13-3511-gd2249cd9adf
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116613
--- Comment #24 from Kamil Dudka ---
(In reply to David Malcolm from comment #21)
> (In reply to David Malcolm from comment #20)
> > How about another option
> > -fdiagnostics-set-output=
> > that would work like
> > -fdiagnostics-add-outpu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105766
Bug 105766 depends on bug 94894, which changed state.
Bug 94894 Summary: avoidable instantiation of conversion function template
during overload resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94894
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106201
Bug 106201 depends on bug 94894, which changed state.
Bug 94894 Summary: avoidable instantiation of conversion function template
during overload resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94894
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94894
Patrick Palka changed:
What|Removed |Added
Target Milestone|13.0|---
Status|RESOLVED
1 - 100 of 172 matches
Mail list logo