From: Per Bothner <per@bothner.com>
To: Emmanuel Oga <emmanueloga@gmail.com>
Cc: kawa@sourceware.org
Subject: Re: More internals documentation
Date: Sat, 10 Nov 2018 03:12:00 -0000 [thread overview]
Message-ID: <44947079-efd6-37f3-8f01-5404cb00faa0@bothner.com> (raw)
In-Reply-To: <CAMsuM5qEW10Wk3UT79xNinfysX4q0JxSX3-sQi=Lq5UOSRtcsA@mail.gmail.com>
On 11/9/18 5:49 PM, Emmanuel Oga wrote:
> Are there any changes from the top of your head in architecture that you
> would highlight?
There are some more complicated passes in the various ExpVisitor (tree-walking) passes.
Most the complicated stuff happens in InlineCalls, but there are some complex
stuff happening in FineInlineCalls and elsewhere. I don't think the internals
doc covers that very well.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2018-11-10 3:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 23:47 Emmanuel Oga
2018-11-10 0:01 ` Per Bothner
2018-11-10 1:50 ` Emmanuel Oga
2018-11-10 3:12 ` Per Bothner [this message]
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=44947079-efd6-37f3-8f01-5404cb00faa0@bothner.com \
--to=per@bothner.com \
--cc=emmanueloga@gmail.com \
--cc=kawa@sourceware.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).