Howdy, I can test on various platforms on the GCC compile farm. Just tell me what you need tested.
A list of the machines in the farm are here: http://gcc.gnu.org/wiki/CompileFarm Duke On Sun, Jan 9, 2011 at 7:06 PM, Nick Wellnhofer <[email protected]> wrote: > The code in trace_system_areas tries to put the register contents on the > stack, so it's a bit tricky. But it's doable. > > I'm not sure if I can get testers on sparc and ia64, though. > > Nick > > > On 10/01/11 01:54, Andrew Whitworth wrote: >> >> There is some platform-specific code in src/gc/system.c too. If you >> can include that garbage in your refactor now, You'll have a strong +1 >> from me. >> >> --Andrew Whitworth >> >> >> >> On Sun, Jan 9, 2011 at 5:57 PM, Nick Wellnhofer<[email protected]> >> wrote: >>> >>> At the moment, some platform-specific code is generated from source files >>> in >>> config/gen/platform. This is unnecessary because all these files can be >>> compiled directly. >>> >>> In branch nwellnhof/platform_src, I moved all that code to a new >>> directory >>> src/platform, cleaned it up a little, and adjusted the configure and >>> build >>> process. See >>> >>> https://github.com/parrot/parrot/commit/59fec7a832 >>> >>> In a next step, I'd like to move all platform dependent code like the >>> code >>> src/io or in the OS dynpmc to src/platform and remove all platform >>> #ifdefs >>> from the rest of the Parrot source. >>> >>> Obviously, I had to touch a lot of platform-specific code, so I could >>> need >>> testers on not so common platforms. >>> >>> Nick >>> _______________________________________________ >>> http://lists.parrot.org/mailman/listinfo/parrot-dev >>> > > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev > -- Jonathan "Duke" Leto [email protected] http://leto.net _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
