http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58687
--- Comment #13 from Max TenEyck Woodbury <mtewoodbury at gmail dot com> --- (In reply to jos...@codesourcery.com from comment #12) > On Wed, 30 Oct 2013, mtewoodbury at gmail dot com wrote: > >> Thank you, I will look info all of that. My own resources have limits; when >> it comes to testing generated code on many architectures, I will definitely >> need such resources. > > A fix for this particular bug should only need testing on one > architecture. It's not like changes to the register allocator that are > likely to have architecture-specific issues. Yes. 'make -w -k check' on the base configuration is still in progress. There's enough stuff wrong with the base that I need a log to check against. Using the compile farm here would add a queuing delay, slowing the process further. Oh, and could you mark this bug as either 'confirmed' or 'in-progress'? I do have another bug (58884) that will need those resources if I am the one that tackles fixing it... Later...
