From: "Marc Nieper-Wißkirchen" <marc.nieper+gnu@gmail.com>
To: "Marc Nieper-Wißkirchen via Jit" <jit@gcc.gnu.org>
Subject: Portability requirements of libgccjit++.h
Date: Mon, 31 Jan 2022 10:39:32 +0100 [thread overview]
Message-ID: <CAEYrNrTGNXbx6C=URFPev28eVFirv__oOd2KHfR0H9Cuzptwcw@mail.gmail.com> (raw)
The GCC project has the following portability requirements ([1]):
"The directories gcc, libcpp and fixincludes may use C++03. They may also
use the long long type if the host C++ compiler supports it. These
directories should use reasonably portable parts of C++03, so that it is
possible to build GCC with C++ compilers other than GCC itself. If testing
reveals that reasonably recent versions of non-GCC C++ compilers cannot
compile GCC, then GCC code should be adjusted accordingly. (Avoiding
unusual language constructs helps immensely.) Furthermore, these
directories *should* also be compatible with C++11."
Does this requirement apply to libgccjit++.h as well? The header file is
technically contained in the directory gcc. On the other hand, it is not
used when building GCC.
I am asking because I have found the C++11 nullptr keyword in the header
file. Can we generally lift the requirements to C++11 as far as the C++
API for libgccjit is concerned?
As any user of libgccjit has access to a recent C++ compiler (because with
libgccjit, there comes gcc), I would be very much in favor of lifting this
requirement so that further developments of the API can use C++11 features,
including parameter packs generalizing all the ad-hoc overloadings of
new_call in the current header.
Thanks,
Marc
--
[1] - https://gcc.gnu.org/codingconventions.html#Cxx_Language
next reply other threads:[~2022-01-31 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 9:39 Marc Nieper-Wißkirchen [this message]
2022-01-31 14:37 ` David Malcolm
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='CAEYrNrTGNXbx6C=URFPev28eVFirv__oOd2KHfR0H9Cuzptwcw@mail.gmail.com' \
--to=marc.nieper+gnu@gmail.com \
--cc=jit@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).