I've had some time to think about this a little bit more, and I'm not completely convinced that it would be a good idea to back port a new machine code generator to 7.8. After all, that seems like a pretty major change to insert into what should theoretically be a stable release.
Perhaps it makes more sense to release 7.8 as-is and then focus attention on doing a stable release of 7.9/7.10/8.0/whatever. How far from being stable is 7.9 at this point? I've dabbled with it, but haven't done much serious work with it yet. Bill On May 23, 2012, at 6:49 PM, Bill Welliver wrote: > Yes, I realized that after I stepped away from the computer... I had ported > the 2 changes from ~April 6th, and after thinking about it don't remember > anything in the changesets that actually used the new macros. > > I'll take a closer look and see if I can do a proper job this time around. > > Bill > > On Wed, 23 May 2012, Henrik Grubbström (Lysator) @ Pike (-) developers forum > wrote: >> The fix involves more than one commit. You will eg need commit >> 4555f37d5b014dd680cf86b735fb20b659f296d3 which adds a function >> to interpret.c that was needed by the amd64 code-generator, and >> then by the new x86 code-generator. >> >> The easiest approach is probably to first backport the amd64 >> code-generator, and then the new x86 code-generator. >> /grubba
