Status reports for "JIT for firewalling"
tuchalia at gmail.com
Mon Jul 27 20:36:19 UTC 2015
Unfortunately I haven't been able to make any further progress.
I've been having a lot of problems to get the compiler working. I tested
many different hypotheses about the bug with no success so far, and I've
talked with David Chisnall to see if he could lend me a hand and he has
given me some pointers. So, hopefully, I'll be past this stage this week.
El lun., 20 jul. 2015 a las 15:43, George Neville-Neil (<gnn at freebsd.org>)
> Seems like the next thing to do is build from source as David suggests.
> On 20 Jul 2015, at 4:47, Daniel Peyrolon wrote:
> > Hi everyone,
> > This has not been a productive week. I've been so far unable to get
> > the
> > compiler working, I contacted David Chinsall as I said, and I have
> > been
> > looking to make everything works. The initialization process of LLVM
> > is not
> > working as expected, which may be related to a bad install (we have
> > already
> > disarded that), a bad building process, or a bad LLVM initialization
> > process. Given the fact that the LLVM API has changed a lot since the
> > last
> > time, that may be possible.
> > El sáb., 11 jul. 2015 a las 12:24, Daniel Peyrolon
> > (<tuchalia at gmail.com>)
> > escribió:
> >> Hi everyone,
> >> This last pair of weeks I've written the code needed to compile
> >> almost all
> >> the rules, except those that modify control flow: call and skipto.
> >> For
> >> those ones I will have to write them by hand on LLVM IR.
> >> I also started working on the testing code. I'm using conductor to
> >> control the different hosts. I already have reserved a pair of hosts
> >> from
> >> the netperf cluster in order to get that running.
> >> So far I haven't been able to test anything because the compiler is
> >> not
> >> working yet, there has been a change in the API of LLVM since I last
> >> worked
> >> with it, I sent an email to my past mentor, David Chisnall asking for
> >> advice.
> >> --
> >> Daniel
> > --
> > Daniel
More information about the soc-status