Andreas Ericsson wrote:
>
> I would like to step up and say "I'll do
that", but unfortunately I can't,
> as my asm-fu is... well, I don't have any.
>
> I could probably do some janitorial work on the
C-sources or some such
> though, although you seem primarily focused on adding
new features, so
> I don't know what stuff you would like done, if any,
that I can do,
> especially since I'm not at all familiar with the nasm
sourcetree.
>
Well, these are things that I think we need:
- A Mach-O backend maintainer (Mac person).
- Someone to take responsibility for the instruction table,
since we
have a number of issues with it. This one actually
requires
relatively little understanding of the code base,
especially with the
changes that I've made recently. It mostly requires
being willing to
dig through manuals and websites and verify that the
table matches
reality.
- Automatic testing. Victor has written a regression test
framework,
but we really could use a pile of regression tests
(automatically
generating them should be at least partially possible.)
- Documentation.
There are a lot of core changes which are necessary, such as
fixing the
matching system. Right now, a big blocker to those is that
some of
those will require instruction table changes, and I'm sorry,
I can't do
both. I'm already spending *way* too much time and energy
on this.
-hpa
------------------------------------------------------------
-------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nasm-devel mailing list
Nasm-devel lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nasm-devel
|
------------------------------------------------------------
-------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.