From: Basile Starynkevitch <basile@starynkevitch.net>
To: David Malcolm <dmalcolm@redhat.com>
Cc: jit@gcc.gnu.org
Subject: cross-compilation & libgccjit
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <55A77505.7030004@starynkevitch.net> (raw)
In-Reply-To: <1436972619.830.28.camel@surprise>
On 07/15/2015 17:03, David Malcolm wrote that he is working on:
> (a) libgccjit: adding support for cross-compilation (perhaps with a
> gcc_jit_target type).
If you do that, you really should change the name of your library. By
definition Just-In-Time compilation is
with the host same as the target and forbids the idea of
cross-compilation (which is always Ahead Of Time).
Perhaps your library should be renamed as libgccgeneratecode and sit in
gcc/generate/
That name is not sexy, but I really believe that cross-compilation
cannot be Just In Time by definition; so please don't call your library
libgccjit (or anything containing JIT acronym) if it is not related to
Just In Time compilation, see
https://en.wikipedia.org/wiki/Just-in-time_compilation
Please, please, don't name gccjit something which is not only for Just
In Time. Find another name!
Cheers
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mine, sont seulement les miennes} ***
next prev parent reply other threads:[~2015-07-16 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 missing gcc_jit_context_new_rvalue_from_long_long etc....? Basile Starynkevitch
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Basile Starynkevitch
2015-01-01 0:00 ` Basile Starynkevitch
2015-01-01 0:00 ` Basile Starynkevitch [this message]
2015-01-01 0:00 ` cross-compilation & libgccjit David Malcolm
2015-01-01 0:00 ` Basile Starynkevitch
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=55A77505.7030004@starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=dmalcolm@redhat.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).