https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98167
--- Comment #15 from Hongtao.liu ---
(In reply to Andrew Pinski from comment #14)
> (In reply to Hongtao.liu from comment #13)
> > fold shulfps to vec_perm_exp, but still 2 shulfps are generated.
> >
> > __m128 f (__m128 a, __m128 b)
> > {
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65056
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
On Fri, 2021-08-27 at 13:11 +0800, YunQiang Su wrote:
> 在 2021/6/18 11:29, YunQiang Su 写道:
> > Currently, the asm output file for MIPS has no rev info.
> > It can make some trouble, for example:
> > assembler is mips1 by default,
> > gcc is fpxx by default.
> > To assemble the output of gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48128
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |4.8.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101472
--- Comment #5 from Hongtao.liu ---
Fixed in GCC12, backport to GCC11 and GCC10.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101472
--- Comment #4 from CVS Commits ---
The releases/gcc-10 branch has been updated by hongtao Liu
:
https://gcc.gnu.org/g:fab014ecf9f7faf3b607a1e0892d0aeabe556661
commit r10-10073-gfab014ecf9f7faf3b607a1e0892d0aeabe556661
Author: konglin1
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101472
--- Comment #3 from CVS Commits ---
The releases/gcc-11 branch has been updated by hongtao Liu
:
https://gcc.gnu.org/g:b186040b468f6da512b9b123e1d4549f44396993
commit r11-8934-gb186040b468f6da512b9b123e1d4549f44396993
Author: konglin1
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101472
--- Comment #2 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:44a545a6abdd330083c1d12ad70092defbba702a
commit r12-3181-g44a545a6abdd330083c1d12ad70092defbba702a
Author: konglin1
Date: Mon Aug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102080
--- Comment #11 from Hongtao.liu ---
Created attachment 51363
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51363=edit
Proposed patch
I'm testing this patch.
在 2021/6/18 11:29, YunQiang Su 写道:
Currently, the asm output file for MIPS has no rev info.
It can make some trouble, for example:
assembler is mips1 by default,
gcc is fpxx by default.
To assemble the output of gcc -S, we have to pass -mips2
to assembler.
gcc/ChangeLog:
*
On Fri, Aug 27, 2021 at 10:03 AM Kong, Lingling via Gcc-patches
wrote:
>
> Hi,
>
> For avx512f_scattersi, mask operand only affect set src, we need
> to refine the pattern to let gcc know mask register also affect the dest.
> So we put mask operand into UNSPEC_VSIBADDR.
>
> Bootstrapped and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83636
--- Comment #2 from YunQiang Su ---
Patch has been sent to:
https://gcc.gnu.org/pipermail/gcc-patches/2021-August/578243.html
for some instructions, MIPS r6 uses different encoding other than
the previous releases.
1. mips/n32.S disable .set mips4: since it casuses old insn encoding
is used.
https://github.com/libffi/libffi/pull/396
2. mips/ffi.c: the encoding for JR is hardcoded: we need to use
different value
On Thu, Aug 26, 2021 at 7:09 PM Richard Biener via Gcc-patches
wrote:
>
> On Thu, Aug 26, 2021 at 12:50 PM Richard Sandiford
> wrote:
> >
> > Richard Biener via Gcc-patches writes:
> > > On Thu, Aug 26, 2021 at 11:06 AM Richard Sandiford
> > > wrote:
> > >>
> > >> Richard Biener via
On Thu, 2021-08-26 at 23:56 -0400, YunQiang Su wrote:
> gcc/ChangeLog:
>
> PR target/102089
> * config.gcc: MIPS: use N64 ABI by default if the triple end
> with -gnuabi64, which is used by Debian since 2013.
> ---
> gcc/config.gcc | 14 ++
> 1 file changed,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102089
--- Comment #3 from YunQiang Su ---
https://gcc.gnu.org/pipermail/gcc-patches/2021-August/578240.html
Patch has been sent to gcc-patches.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102090
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
gcc/ChangeLog:
PR target/102089
* config.gcc: MIPS: use N64 ABI by default if the triple end
with -gnuabi64, which is used by Debian since 2013.
---
gcc/config.gcc | 14 ++
1 file changed, 14 insertions(+)
diff --git a/gcc/config.gcc b/gcc/config.gcc
index
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102090
--- Comment #4 from friedkeenan at protonmail dot com ---
I think you're correct. That's really strange, but I guess that's what
std::construct_at is for? But that also confuses me, how is GCC's
implementation of std::construct_at working if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102090
--- Comment #3 from Andrew Pinski ---
DR 1312 also mentions something similar with respect to casting to void*.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102090
--- Comment #2 from Andrew Pinski ---
clang produces:
:3:16: error: consteval function never produces a constant expression
[-Winvalid-constexpr]
consteval auto fuck() {
^
:5:23: note: call to placement 'operator new'
const
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102090
--- Comment #1 from Andrew Pinski ---
I don't think inplacement new is valid for constexpr. See PR 61105 also.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102089
--- Comment #2 from YunQiang Su ---
(In reply to Andrew Pinski from comment #1)
> Patches should be sent to gcc-patches@ after reading
> https://gcc.gnu.org/contribute.html
Yes. the patch will be send just now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102089
Andrew Pinski changed:
What|Removed |Added
Target||mips*-*-linux-gnuabi64
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102090
Bug ID: 102090
Summary: Placement-new is not constexpr
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Hi,
- Add documents of XuanTie series [1].
- Add QEMU binary [2] by now, you can execute application with argument
‘-cpu c910’,
and opening source is on the way.
- Add my colleague [3] to commit patches of binutils
[1] https://github.com/rjiejie/XuanTie-doc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102030
--- Comment #4 from Joe Eagar ---
I hadn't realized the nonnull attribute is 1-based. That makes sense.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102089
Bug ID: 102089
Summary: MIPS: use N64 ABI by default if the triple end with
-gnuabi64
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102080
Andrew Pinski changed:
What|Removed |Added
Component|target |middle-end
--- Comment #10 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67170
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |6.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102080
--- Comment #9 from Hongtao.liu ---
(In reply to Andrew Pinski from comment #8)
> That is the mask is a vector mode still for these patterns according to the
> internals doc.
> Rather than the scalar mode you have:
> (match_operand: 1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102080
--- Comment #8 from Andrew Pinski ---
That is the mask is a vector mode still for these patterns according to the
internals doc.
Rather than the scalar mode you have:
(match_operand: 1 "register_operand")
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102080
--- Comment #7 from Andrew Pinski ---
The operation works elementwise if the operands are vectors.
No I think x86's cond_* patterns are not correct.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102080
--- Comment #6 from Andrew Pinski ---
This is the match pattern which does it:
(for uncond_op (UNCOND_BINARY)
cond_op (COND_BINARY)
(simplify
(vec_cond @0 (view_convert? (uncond_op@4 @1 @2)) @3)
(with { tree op_type = TREE_TYPE (@4);
On Thu, Aug 26, 2021 at 05:28:42PM -0400, Michael Meissner wrote:
> I have patches for adding XXSPLTI32DX, but so far, I'm not sure whether it is
> a
> win or not. This has the xxsplti32dx_operand predicate and the
> xxsplti32dx_constant_p internal function and a separate constraint ("eD") for
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102080
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102080
--- Comment #4 from Hongtao.liu ---
diff --git a/test.c.032t.ccp1 b/test.c.033t.forwprop1
index 5b18739..c6f0587 100644
--- a/test.c.032t.ccp1
+++ b/test.c.033t.forwprop1
@@ -31,11 +31,12 @@ void EncodedFromDisplay ()
__m256 __trans_tmp_11;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28662
Bug 28662 depends on bug 67623, which changed state.
Bug 67623 Summary: interaction between cpp and Fortran
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67623
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58334
Andrew Pinski changed:
What|Removed |Added
CC||Joost.VandeVondele at mat dot
ethz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67623
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Fri, Aug 13, 2021 at 05:22:47PM +, Joseph Myers wrote:
> On Fri, 13 Aug 2021, Andreas Schwab wrote:
>
> > On Aug 12 2021, Patrick McGehearty via Gcc-patches wrote:
> > How can it happen that __LONG_DOUBLE_IEEE128__ is not defined? This
> > file is always compiled with -mfloat128 and this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87737
--- Comment #3 from Andrew Pinski ---
GCC 10+ rejects this code with:
/app/example.f90:2:9:
2 | program p
| 1
Error: Entity 'master.0.f' at (1) has a deferred type parameter and requires
either the POINTER or ALLOCATABLE
Hi,
For avx512f_scattersi, mask operand only affect set src, we need to
refine the pattern to let gcc know mask register also affect the dest.
So we put mask operand into UNSPEC_VSIBADDR.
Bootstrapped and regression tested on x86_64-linux-gnu{-m32,-m64}.
Ok for master?
gcc/ChangeLog:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55210
Andrew Pinski changed:
What|Removed |Added
CC||Melven.Roehrig-Zoellner@DLR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91237
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55210
--- Comment #3 from Andrew Pinski ---
*** Bug 68968 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68968
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55210
Andrew Pinski changed:
What|Removed |Added
CC||siteg at mathalacarte dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65025
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102068
--- Comment #2 from CVS Commits ---
The master branch has been updated by David Edelsohn :
https://gcc.gnu.org/g:5faf7120398c9bf290758891a975da1f727d631a
commit r12-3178-g5faf7120398c9bf290758891a975da1f727d631a
Author: David Edelsohn
Date:
Further fixes to structure alignment when the structure is packed
and contains double. This patch checks for packed attribute
at the top level.
Bootstrapped on powerpc-ibm-aix7.2.3.0
gcc/ChangeLog:
PR target/102068
* config/rs6000/rs6000.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98167
--- Comment #14 from Andrew Pinski ---
(In reply to Hongtao.liu from comment #13)
> fold shulfps to vec_perm_exp, but still 2 shulfps are generated.
>
> __m128 f (__m128 a, __m128 b)
> {
> vector(4) float _3;
> vector(4) float _5;
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43147
--- Comment #20 from Hongtao.liu ---
Fixed in GCC12, now gcc generate optimal codes.
main:
.LFB532:
.cfi_startproc
subq$8, %rsp
.cfi_def_cfa_offset 16
movaps .LC0(%rip), %xmm0
callprintv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98167
--- Comment #13 from Hongtao.liu ---
fold shulfps to vec_perm_exp, but still 2 shulfps are generated.
__m128 f (__m128 a, __m128 b)
{
vector(4) float _3;
vector(4) float _5;
vector(4) float _6;
;; basic block 2, loop depth 0
;;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98167
--- Comment #12 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:0fa4787bf34b173ce6f198e99b6f6dd8a3f98014
commit r12-3177-g0fa4787bf34b173ce6f198e99b6f6dd8a3f98014
Author: liuhongt
Date: Fri Dec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43147
--- Comment #19 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:0fa4787bf34b173ce6f198e99b6f6dd8a3f98014
commit r12-3177-g0fa4787bf34b173ce6f198e99b6f6dd8a3f98014
Author: liuhongt
Date: Fri Dec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66995
Andrew Pinski changed:
What|Removed |Added
Blocks||94404
Summary|First
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93625
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93625
Andrew Pinski changed:
What|Removed |Added
Summary|inline specifier in a |[DR281] inline specifier in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102080
--- Comment #3 from Hongtao.liu ---
(In reply to H.J. Lu from comment #2)
> It is caused by r12-2679.
Mine.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67633
--- Comment #2 from Andrew Pinski ---
GCC, clang and MSVC all argree here but ICC disagrees.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90960
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89687
Andrew Pinski changed:
What|Removed |Added
Known to work||10.1.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83249
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64519
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
I will prepare a patch without the changes to .../rs6000/_divkc3.c
but I have no way of testing it to confirm it fixes the original
complaint.
On 8/26/2021 5:09 PM, Joseph Myers wrote:
On Thu, 26 Aug 2021, Patrick McGehearty via Gcc-patches wrote:
The revision retains the use of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79531
--- Comment #2 from Andrew Pinski ---
Since GCC 8, we produce:
:8:16: error: 'virtual void derived::method2()' marked 'override', but
does not override
virtual void method2() override;
^~~
:11:6: error: no declaration
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70476
--- Comment #3 from Andrew Pinski ---
GCC, clang, ICC, and MSVC all agree they have external linkage.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95407
--- Comment #2 from Andrew Pinski ---
I think PR 67943 is also related. But then DR 472 is also related to that one.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67943
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2021-08-26
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52953
Andrew Pinski changed:
What|Removed |Added
CC||jtcash at ucsd dot edu
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89616
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91609
--- Comment #4 from Andrew Pinski ---
Seems fixed in GCC 11+.
Hi!
On Thu, Jul 29, 2021 at 08:31:02AM -0500, Bill Schmidt wrote:
> * config/rs6000/rs6000-call.c (rs6000-builtins.h): New #include.
> (rs6000_init_builtins): Call rs6000_autoinit_builtins; skip the old
> initialization logic when new builtins are enabled.
s/; s/. S/
> + /*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101243
--- Comment #5 from Jonathan Wakely ---
For the attachment in comment 3 trunk now says:
In file included from /home/jwakely/gcc/12/include/c++/12.0.0/functional:59,
from /tmp/pr-1.cc:2:
This makes the std::function constructor use perfect forwarding, to
avoid an unnecessary move-construction of the target. This means we need
to rewrite the _Function_base::_Base_manager::_M_init_functor function
to use a forwarding reference, and so can reuse it for the clone
operation.
Also
Signed-off-by: Jonathan Wakely
libstdc++-v3/ChangeLog:
* include/bits/std_function.h (function): Adjust doxygen
comments.
* include/bits/unique_ptr.h (make_unique_for_overwrite):
Change parameter name to match doxygen comment.
Tested powerpc64le-linux. Committed
Add static assertions to std::function, so that more user-friendly
diagnostics are given when trying to store a non-copyable target object.
These preconditions were added as "Mandates:" by LWG 2447, but I'm
committing them separately from implementing that, to allow just this
change to be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92193
--- Comment #2 from Jonathan Wakely ---
This makes the diagnostics for std::vector diabolical.
We hit a nice static assertion saying something like:
/home/jwakely/gcc/12/include/c++/12.0.0/bits/stl_uninitialized.h:90:56: error:
static
On Thu, Aug 26, 2021 at 6:53 PM Segher Boessenkool
wrote:
>
> Hi!
>
> On Thu, Aug 26, 2021 at 02:57:35PM -0400, David Edelsohn wrote:
> > * config/rs6000/ibm-ldouble.c (ldouble_qadd_internal): Rename
> > from
> > __gcc_qadd.
> > (__gcc_qadd): Call
Hi!
On Thu, Aug 26, 2021 at 02:57:35PM -0400, David Edelsohn wrote:
> * config/rs6000/ibm-ldouble.c (ldouble_qadd_internal): Rename from
> __gcc_qadd.
> (__gcc_qadd): Call ldouble_qadd_internal.
> (__gcc_qsub): Call ldouble_qadd_internal with second
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95484
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
Snapshot gcc-9-20210826 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/9-20210826/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 9 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69855
--- Comment #10 from Andrew Pinski ---
(In reply to Nathan Sidwell from comment #9)
> Reopening. I think I'm on the path of getting this right ...
I think r11-3699 fixed it the right way.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81609
--- Comment #5 from Andrew Pinski ---
Was fixed by r11-3699.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32042
--- Comment #3 from Andrew Pinski ---
Was fixed by r11-3699.
On Thu, 26 Aug 2021, Patrick McGehearty via Gcc-patches wrote:
> The revision retains the use of __LIBGCC_DF_* in .../rs6000/_divkc3.c
> instead of __LIBGCC_KF_* since some older but still supported environments
> do not recognize the KF floating point mode properly. This change has a
That part
The v4 revision adds a test in libgcc/libgcc2.c for when
"__LIBGCC_TF_MANT_DIG__ == 106" to use __LIBGCC_DF_EPSILON__ instead
of __LIBGCC_TF_EPSILON__. That is specific to IBM 128-bit format long
doubles where EPSILON is very, very small and 1/EPSILON oveflows to
infinity. This change avoids the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102088
--- Comment #2 from Martin Sebor ---
At -O0 the warning looks right although not as nice as what the analyzer prints
(but the analyzer doesn't catch it at -O1 or higher):
$ gcc -S -Wall -fanalyzer z.c
z.c: In function ‘f’:
z.c:5:7: warning:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102088
--- Comment #1 from Martin Sebor ---
The patch below changes the latest warning to the following without any dg.exp
test failures:
z.c: In function ‘f’:
z.c:9:3: warning: ‘x’ may be used uninitialized [-Wmaybe-uninitialized]
9 | return
On Thu, Aug 26, 2021 at 02:17:57PM -0500, will schmidt wrote:
> On Wed, 2021-08-25 at 15:46 -0400, Michael Meissner wrote:
> > Generate XXSPLTIDP on power10.
> >
> > I have added a temporary switch (-mxxspltidp) to control whether or not the
> > XXSPLTIDP instruction is generated.
>
> How
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94405
--- Comment #1 from Andrew Pinski ---
Only MSVC rejects this code.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102088
Bug ID: 102088
Summary: poor uninitialized warning points to an initialized
variable, no note to uninitialized
Product: gcc
Version: 12.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89898
--- Comment #3 from Andrew Pinski ---
This was implemented by r9-3836 which is P0732R2:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0732r2.pdf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89898
--- Comment #2 from Andrew Pinski ---
This is valid C++ 20 too:
struct A { int t; };
template struct X { int d = a.t; };
template a > int f () { return a.d; }
int g(void)
{
return f{1}>();
}
Yes I know it looks off but it is valid now
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89898
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88344
--- Comment #2 from Andrew Pinski ---
The same is true for C2x and C++11 style attributes:
struct B {
[[gnu::always_inline]];
};
The C front-end warns:
:3:3: warning: 'always_inline' attribute ignored [-Wattributes]
3 |
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88344
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2021-08-26
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32042
Andrew Pinski changed:
What|Removed |Added
Known to work||11.1.0
--- Comment #2 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81609
--- Comment #4 from Andrew Pinski ---
Seems fixed for GCC 11.
1 - 100 of 276 matches
Mail list logo
