From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Berke Yavas <iamberkeyavas@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [GSoC][C++: Implement compiler built-in traits for the standard library traits]
Date: Tue, 28 Feb 2023 12:16:03 +0000 [thread overview]
Message-ID: <CAH6eHdS=G079RZrjgYbM7h3vyJoDnd8OhnqJKb-JW1Tm7_OWWQ@mail.gmail.com> (raw)
In-Reply-To: <CAFTM=KtoTO9S7K3wGRa+xbT2wAGwmpMUQ1VXRCsFY=KSOqG25g@mail.gmail.com>
On Tue, 28 Feb 2023 at 10:58, Berke Yavas via Gcc <gcc@gcc.gnu.org> wrote:
>
> Hi,
>
> I am Berke. I am interested in the project C++: Implement compiler built-in
> traits for the standard library traits for the upcoming GSoC. I am a
> Software Engineer with a year of experience. I am very excited to have a
> chance to work on gcc.
Great, thanks for your interest in the project.
> So far, I have built gcc from source, runned tests. Have a few follow up
> questions.
>
> 1. Project is related with C++ frontend and library development, so during
> the development there should be no issue configuring with
> --disable-bootstrap --disable-multilib --disablelibstdcxx-pch(Thanks to irc
> folks who suggested the latter 2, I just wanted to confirm) right?
That's fine.
> 2. Is there any other built-in compiler traits that are not in the file
> `gcc/cp/cp-trait.def`?
> 3. __is_same built in is already used in a couple of places in libstdc++.
>
> File: libstdc++-v3/include/bits/c++config
> 840 #if _GLIBCXX_HAS_BUILTIN(__is_same)
> 841 # define _GLIBCXX_HAVE_BUILTIN_IS_SAME 1
> 842 #endif
>
> Is this the file where gcc checks if the compiler built in is available? So
> other compiler built-ins should be checked here too?
No, that's old code that's done differently for historical reasons.
For new built-ins you can just use __has_builtin instead. There are
lots of examples of using that in <type_traits>.
prev parent reply other threads:[~2023-02-28 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 10:57 Berke Yavas
2023-02-28 12:16 ` Jonathan Wakely [this message]
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='CAH6eHdS=G079RZrjgYbM7h3vyJoDnd8OhnqJKb-JW1Tm7_OWWQ@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=iamberkeyavas@gmail.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).