From: Mateus Carmo Martins de Freitas Barbosa <mateus.carmo.barbosa@usp.br>
To: gcc@gcc.gnu.org
Subject: Is GIMPLE stable?
Date: Tue, 10 Sep 2019 03:08:00 -0000 [thread overview]
Message-ID: <CACeY_chhWebmAMyCpqdKwWAZiLK-m+NiUrMEHFBv-38BLR+LxQ@mail.gmail.com> (raw)
There's an ongoing discussion on the rustc forum
(<https://users.rust-lang.org/t/call-for-help-implementing-an-independent-rust-frontend-for-gcc/32163>)
on implementing a GCC front-end for the Rust compiler, and the issue
of whether GIMPLE is stable was brought up. Namely, if a compiler
front-end were to output GIMPLE directly, how often (if at all) would
its codebase have to be changed to due to breaking changes from GCC?
I did find this reply
<https://gcc.gnu.org/ml/gcc/2011-05/msg00313.html> which says:
>> ?^ It looks like GIMPLE is expected to change per version of gcc. Is there a time in >> the future when GIMPLE will be pretty stable?
>
> "Pretty stable" won't be enough, and I don't see us arriving there at
> the moment.
But this is fairly old (2011) so it seemed reasonable to ask if this
is still the case.
next reply other threads:[~2019-09-10 3:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 3:08 Mateus Carmo Martins de Freitas Barbosa [this message]
2019-09-10 4:05 ` Ian Lance Taylor via gcc
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=CACeY_chhWebmAMyCpqdKwWAZiLK-m+NiUrMEHFBv-38BLR+LxQ@mail.gmail.com \
--to=mateus.carmo.barbosa@usp.br \
--cc=gcc@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).