➜

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 christian.heimes
Recipients bfroehle, christian.heimes, eric.araujo, pitrou, tarek
Date 2013-01-04.10:01:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357293677.63.0.614197438043.issue5309@psf.upfronthosting.co.za>
In-reply-to
Content 
+1

I think it's sufficient to parallelize the compilation step (.c -> .o) and ignore the linker step. Linking is usually so fast that it doesn't matter.

Idea:
* separate compile step from link step
* run all compile calls for all extensions in parallel until all objects of all extensions are generated
* do linking and error reporting in serial mode
History
Date User Action Args
2013-01-04 10:01:17christian.heimessetrecipients: + christian.heimes, pitrou, tarek, eric.araujo, bfroehle
2013-01-04 10:01:17christian.heimessetmessageid: <1357293677.63.0.614197438043.issue5309@psf.upfronthosting.co.za>
2013-01-04 10:01:17christian.heimeslinkissue5309 messages
2013-01-04 10:01:17christian.heimescreate