This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skip.montanaro
Recipients alexandre.vassalotti, arigo, christian.heimes, lemburg, pitrou, rhettinger, skip.montanaro
Date 2008-12-31.22:10:46
SpamBayes Score 7.940703e-07
Marked as misclassified No
Message-id <1230761448.56.0.552488657179.issue4753@psf.upfronthosting.co.za>
In-reply-to
Content
Works pretty well for me on my MacBook Pro, but on my G5 it performed
abysmally.  In fact, it ran so much worse that I cleaned up my sandbox 
and did both checks all over again to make sure I didn't mess something
up.  It looks like my MacBook Pro saw about a 14% degradation.  Both
computers are running Mac OS X 10.5.6 with the latest Xcode - 3.1.2.
On both computers gcc -v reports 4.0.1, Apple build 5490.

If this is applied to the core I think it will have to select for more
than just gcc.  It will also have to select based on the chip
architecture.
History
Date User Action Args
2008-12-31 22:11:49skip.montanarounlinkissue4753 messages
2008-12-31 22:10:48skip.montanarosetrecipients: + skip.montanaro, lemburg, arigo, rhettinger, pitrou, christian.heimes, alexandre.vassalotti
2008-12-31 22:10:48skip.montanarosetmessageid: <1230761448.56.0.552488657179.issue4753@psf.upfronthosting.co.za>
2008-12-31 22:10:48skip.montanarolinkissue4753 messages
2008-12-31 22:10:46skip.montanarocreate