public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: Ken Matsui <kmatsui@cs.washington.edu>, gcc-patches@gcc.gnu.org
Cc: Patrick Palka <ppalka@redhat.com>, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: use new built-in trait __is_reference
Date: Mon, 20 Mar 2023 15:25:37 +0800	[thread overview]
Message-ID: <c57b56394d9c42ab75f1f95c4ef2bfd7fa11ed9b.camel@xry111.site> (raw)
In-Reply-To: <CAML+3pVYKw0zzseC1H+yKwO5L77S001qcvwgwh80AizD80djOw@mail.gmail.com>

You need to CC libstdc++@gcc.gnu.org for any patches touching libstdc++.

On Sat, 2023-03-18 at 21:21 -0700, Ken Matsui via Gcc-patches wrote:
> libstdc++-v3/ChangeLog:
> 
> * include/std/type_traits (is_reference): Use __is_reference built-in
> trait.

Bad ChangeLog format.  You should have a tab (not 4 or 8 spaces, nor
nothing) to indent the ChangeLog content.

Is there any benefit to use a builtin, instead of the existing
implementation?  I can see no but maybe I'm stupid.

> ---
> diff --git a/libstdc++-v3/include/std/type_traits
> b/libstdc++-v3/include/std/type_traits

The patch fails to apply.  It seems because your mail client inserted an
additional newline before "b/".  Try to use git-send-email or configure
the mail client properly.

> index 2bd607a8b8f..18408d8ceb6 100644
> --- a/libstdc++-v3/include/std/type_traits
> +++ b/libstdc++-v3/include/std/type_traits
> @@ -639,6 +639,12 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
>    // Composite type categories.
> 
>    /// is_reference
> +#if __has_builtin(__is_reference)
> +  template<typename _Tp>
> +    struct is_reference
> +    : public integral_constant<bool, __is_reference(_Tp)>

If a patch depends on another patch not applied yet, sent them in a
series.  Or people are puzzled because when this patch is applied alone,
the code fails to build.

> +    { };
> +#else
>    template<typename _Tp>
>      struct is_reference
>      : public false_type
> @@ -653,6 +659,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
>      struct is_reference<_Tp&&>
>      : public true_type
>      { };
> +#endif
> 
>    /// is_arithmetic
>    template<typename _Tp>

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2023-03-20  7:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19  4:21 Ken Matsui
2023-03-20  7:25 ` Xi Ruoyao [this message]
2023-03-20  7:30   ` Ken Matsui
2023-03-20  7:51     ` Xi Ruoyao
2023-03-20  8:03       ` Ken Matsui
2023-03-20  8:07         ` Xi Ruoyao
2023-03-20  8:32           ` Ken Matsui
2023-03-20  9:14           ` Jonathan Wakely
2023-03-20  9:56             ` Ken Matsui
2023-03-20 13:22               ` Ken Matsui
2023-03-20 15:23               ` Patrick Palka
2023-03-20 20:24                 ` Ken Matsui

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=c57b56394d9c42ab75f1f95c4ef2bfd7fa11ed9b.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kmatsui@cs.washington.edu \
    --cc=libstdc++@gcc.gnu.org \
    --cc=ppalka@redhat.com \
    /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).