* [GSoC][C++: Implement compiler built-in traits for the standard library traits]
@ 2023-02-28 10:57 Berke Yavas
2023-02-28 12:16 ` Jonathan Wakely
0 siblings, 1 reply; 2+ messages in thread
From: Berke Yavas @ 2023-02-28 10:57 UTC (permalink / raw)
To: gcc
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
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.
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?
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?
I will prepare a draft of the proposal and send it here for review as soon
as possible.
Best regards,
Berke
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [GSoC][C++: Implement compiler built-in traits for the standard library traits]
2023-02-28 10:57 [GSoC][C++: Implement compiler built-in traits for the standard library traits] Berke Yavas
@ 2023-02-28 12:16 ` Jonathan Wakely
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Wakely @ 2023-02-28 12:16 UTC (permalink / raw)
To: Berke Yavas; +Cc: gcc
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>.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-02-28 12:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-28 10:57 [GSoC][C++: Implement compiler built-in traits for the standard library traits] Berke Yavas
2023-02-28 12:16 ` Jonathan Wakely
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).