#2005: Parrot no longer builds on Darwin/PPC
----------------------+-----------------------------------------------------
 Reporter:  jkeenan   |       Owner:         
     Type:  bug       |      Status:  new    
 Priority:  critical  |   Milestone:         
Component:  build     |     Version:  3.0.0  
 Severity:  fatal     |    Keywords:         
     Lang:            |       Patch:  applied
 Platform:  darwin    |  
----------------------+-----------------------------------------------------

Comment(by jkeenan):

 Last night bacek suggested I test commit 77b57cc on my Darwin/PPC box.
 This commit '''did''' fix the build error reported in the Description of
 this ticket.  However, performance collapsed:  time needed to run `make`
 and `make test` soared to approximately 63 minutes.  While I don't
 normally record this time, my sense is that these days building and
 testing usually take 20-25 minutes on this machine.

 bacek then encouraged me to build with `--optimize` at the same commit
 point.  I did so.  While that significantly improved the build and test
 time to 29:66 -- still worse than I am used to.

 (I should note that on this particular build I used `cc=g++`, where
 normally I use `cc=gcc` and use `g++` only for `link` and `ld`.  At the
 moment, I am starting a run using my normal procedure -- a procedure I
 have used consistently since December 2006.  No `--optimize` is also my
 normal procedure, in part out of habit and in part out of the fact that I
 get failures with `--optimize` on this box; see TT #1930.  As I have
 previously argued, even if this machine is old enough that it falls
 outside the scope of our 'support' policy, there is value in facing up to
 the fact that our software performs worse on it than it did four years ago
 -- and we ought to know why it performs worse.)

 On my Linux/i386 (a Debian Linode), the situation is much more optimistic.
 At 77b57cc I got a combined build and test time of 7:40 without
 `--optimize` and 5:66 and 4:58 on two runs with `--optimize`.  At
 8ae02700, with `--optimize` I got a combined time of 6:57.  This
 represents only a few runs, but it does suggest that gen_gc is capable of
 improving this broad measure of performance whether you optimize or not.

 Thank you very much.

 kid51

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/2005#comment:5>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to