From: Mikael Djurfeldt <mikael@djurfeldt.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Native code generation and gcc
Date: Sat, 3 Dec 2016 15:52:12 +0100 [thread overview]
Message-ID: <CAA2Xvw+80=6n=CK46xTjCbwQvfu3LqqT_FsU96VoMMPWhu5JJw@mail.gmail.com> (raw)
In-Reply-To: <CAA2XvwJmfmykKXrb+zgoEWs7LrBfWBgjP+jOYvdjT06=WAFfFw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
[I apologize beforehand for being completely out of context.]
Are there fundamental reasons for not re-using the gcc backends for native
code generation? I'm thinking of the (im?)possibility to convert the cps to
some of the intermediate languages of gcc.
If it wouldn't cause bad constraints the obvious gain is the many targets
(for free), the gcc optimizations, not having to maintain backends and free
future development.
Of course, there's the practical problem that gcc needs to be adapted for
this kind of use---but shouldn't it be adapted that way anyway? :)
Just an (old) idea...
Mikael
[-- Attachment #2: Type: text/html, Size: 896 bytes --]
next parent reply other threads:[~2016-12-03 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA2XvwKQubnmb4cQXGyP80GjT7_001-xxhFrdP3SKL3+6HkuVw@mail.gmail.com>
[not found] ` <CAA2XvwJjWigCcRBmk3dNJH4+0bEDTOoyL1=o5qj8JpbhuLm-xw@mail.gmail.com>
[not found] ` <CAA2XvwKb9hPUyeOvSZo0fWpDDEzSgjaw_Xehz4rMob1TyNucEA@mail.gmail.com>
[not found] ` <CAA2XvwLwPP728sAeV1mNmDVmGe_V0buiT_xgMDMihBqNXX_RgA@mail.gmail.com>
[not found] ` <CAA2Xvw+RCs4fMU5Pw6QP8ofWtX0k8EbnpLR5KkYUMvLbgopGZw@mail.gmail.com>
[not found] ` <CAA2XvwKRp1KDk285zTH3xLkEhHFcN=_owDf2RFPzt-JnXhxLAg@mail.gmail.com>
[not found] ` <CAA2XvwJUFZ-A+9sbNtomOCiCe=CR+WMAuuTdybUjocVgHmMZ-g@mail.gmail.com>
[not found] ` <CAA2Xvw+mzfKyfiC44VWrZcHRtwgYRDqci9ZbUgUndNq2HEL6tg@mail.gmail.com>
[not found] ` <CAA2XvwJmfmykKXrb+zgoEWs7LrBfWBgjP+jOYvdjT06=WAFfFw@mail.gmail.com>
2016-12-03 14:52 ` Mikael Djurfeldt [this message]
2016-12-04 10:09 ` Native code generation and gcc Helmut Eller
2016-12-04 15:17 ` Greg Troxel
2016-12-05 16:18 ` Lluís Vilanova
2016-12-11 18:09 ` Mikael Djurfeldt
2016-12-11 18:31 ` Stefan Monnier
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA2Xvw+80=6n=CK46xTjCbwQvfu3LqqT_FsU96VoMMPWhu5JJw@mail.gmail.com' \
--to=mikael@djurfeldt.com \
--cc=guile-devel@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).