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++/69549] Named Address Spaces does not compile in C++ Date: Mon, 22 Mar 2021 20:20:49 +0000 [thread overview] Message-ID: <bug-69549-4-kwrLCXU1Zq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-69549-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69549 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Thiago Macieira from comment #5) > BTW, Clang solved this by making __seg_fs, __seg_gs macros that resolve to > __attribute__: .... > That way, they don't need to be deduced as qualifiers in C, like const, > volatile and _Atomic. You still need to handle the attribute like qualifiers .... > So this compiles with Clang in C++: > > void *tid() { auto tib = (void * __seg_fs*)(0); return *tid; } The above is not the reason why namespaces are not handled in GCC's C++ front-end. The reason why they are not handled in C++ is because you need to handle them in overloads and templates correctly. Does clang handle those correctly or does it ignore that issue?
next prev parent reply other threads:[~2021-03-22 20:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-69549-4@http.gcc.gnu.org/bugzilla/> 2021-03-22 17:31 ` thiago at kde dot org 2021-03-22 17:43 ` thiago at kde dot org 2021-03-22 20:20 ` pinskia at gcc dot gnu.org [this message] 2021-03-23 1:36 ` thiago at kde dot org 2021-11-16 13:00 ` jwjagersma at gmail dot com 2021-11-20 0:31 ` jwjagersma at gmail dot com 2023-11-02 1:38 ` abelay at mit dot edu 2023-11-02 4:52 ` xry111 at gcc dot gnu.org 2023-11-02 12:40 ` jwjagersma at gmail dot com 2023-11-21 1:25 ` pinskia at gcc dot gnu.org
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-69549-4-kwrLCXU1Zq@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: linkBe 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).