public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/101710] Sometimes constexpr cannot be used as constexpr
Date: Sun, 01 Aug 2021 08:54:22 +0000	[thread overview]
Message-ID: <bug-101710-4-ZHyOC8ONjm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101710-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101710

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #6)
> Changing:
>   if
> constexpr(type_info<T>.
> has_attribute_helper<can_t_use_default_null_ptr>()&&type_info<T>.
> not_has_has_attribute_helper<force_use_default_null_ptr>())
> 
> to:
>   if constexpr(type_info<T>.template
> has_attribute_helper<can_t_use_default_null_ptr>()&&type_info<T>.template
> not_has_has_attribute_helper<force_use_default_null_ptr>())
> 
> Fixes many of the errors
> Note the use of template.

This shows up in many places in your files.

There was two other errors I noticed:
* aligned_alloc is not defined; mingw does not define aligned_alloc I think.
* is_pointer<T> should have been std::is_pointer_v<T> as far as I can tell.

  parent reply	other threads:[~2021-08-01  8:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-01  2:11 [Bug c++/101710] New: " steve_green at qq dot com
2021-08-01  2:17 ` [Bug c++/101710] " steve_green at qq dot com
2021-08-01  8:22 ` pinskia at gcc dot gnu.org
2021-08-01  8:25 ` pinskia at gcc dot gnu.org
2021-08-01  8:26 ` steve_green at qq dot com
2021-08-01  8:28 ` steve_green at qq dot com
2021-08-01  8:42 ` pinskia at gcc dot gnu.org
2021-08-01  8:54 ` pinskia at gcc dot gnu.org [this message]
2021-08-01  8:59 ` steve_green at qq dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-101710-4-ZHyOC8ONjm@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).