[Libre-soc-bugs] [Bug 980] Implement C-based Power ISA pseudocode compiler

[bugzilla-daemon at libre-soc.org]

https://bugs.libre-soc.org/show_bug.cgi?id=980

--- Comment #123 from Dmitry Selyutin <ghostmansd at gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #122)
> (In reply to Dmitry Selyutin from comment #119)
> > 28 commits since the last update. This was a tough journey!! The code can
> > now be compiled successfully.
> 
> hooraay! that's brilliant
> 
> >  This is a valid C code. The most difficult
> > commit was this:
> > 
> > https://git.libre-soc.org/?p=openpower-isa.git;a=commitdiff;
> > h=90c93ec3cf18b96a9e70464f2b549c9bace1bbe4
> > 
> > Believe it or not, this was done manually.
> 
> daaamn... :)
> 
> 
> > pointer to it". I cannot stress how annoying and boring it was, 
> 
> sometimes i find it good to switch off if you know what i mean :)
> 
> > probably one
> > of the most annoying tasks I ever did, but I decided that writing yet
> > another parser would consume even more time.
> 
> ahh... yes :)
>  
> > This can be checked via the following incantation:
> > 
> > gcc -Os -Isrc/liboppc -Wall -Werror -Wextra test.c -c -o test.o
> > 
> > As you see I took extra measures to ensure we pass some stricter checks.
> > 
> > I'm planning to add src/liboppc/oppc.c autogeneration 
> 
> ah not to the repo, please, if that's the plan? (maybr misunderstding)
> > So, I'm planning to add src/liboppc/oppc.c autogeneration as part of the
> > build
> 
> build script and makefiles yes but to repo no? am i understanding right?

I've pushed a commit which adds a Makefile with simple commands to check it:

https://git.libre-soc.org/?p=openpower-isa.git;a=commitdiff;h=ab9c2cf0f935d6d97e319fbd4d177d7f8679a58f

I'll rebase libopid against the recent master in scope of bug #1254, put these
changes atop, and then add these sweet pair to build once I ensure it works in
CI. But this for 1254, my works here are done, it's ready and can be checked.

> i am veeery happy for that to happen, you've done a hell of a lot.

Thanks! It was a tough one. :-)

> if you can outline what it would take to do a python-cffi wrapper
> plus auto-introspection/generation of the c protos to ensure that
> the python helpers.py is the "canonical" source, plus a hefty budget
> with a bit extra for some unexpected things (which we know always
> haoppens sigh) and chuck it onto 1211 or 1212 as appropriate, that'd
> be fantastic.
> 
> correction: if you are *interested* to do that... :)

Certainly, but I'll take some well-deserved rest first. :-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.