Hi Ard, Eric, and others, As promised, the next Zinc patchset will have less generated code! After a bit of work with Andy and Samuel, I'll be bundling the perlasm. One thing I'm wondering about, though, is the wisdom behind the current .S_shipped pattern. Usually the _shipped is for big firmware blobs that are hard (or impossible) to build independently. But in this case, the .S is generated from the .pl significantly faster than gcc even compiles a basic C file. And, since perl is needed to build the kernel anyway, it's not like it will be impossible to find the right tools. Rather than clutter up commits with the .pl _and_ the .S_shipped, what would you think if I just generated the .S each time as an ordinary build artifact. AFAICT, this is fairly usual, and it's hard to see downsides. Hence, why I'm writing this email: are there any downsides to that? Thanks, Jason
