➜

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 serhiy.storchaka
Recipients Yury.Selivanov, casevh, josh.r, lemburg, mark.dickinson, pitrou, rhettinger, serhiy.storchaka, skrah, vstinner, yselivanov, zbyrne
Date 2016-02-06.08:37:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1454747850.83.0.335129209967.issue21955@psf.upfronthosting.co.za>
In-reply-to
Content 
> I see two main trends: optimize most cases (optimize most operators for int and float,  ex: fastint5_4.patch) versus optimize very few cases to limit changes and to limit effects on ceval.c (ex: inline-2.patch).

I agree that may be optimizing very few cases is better. We need to collect the statistics of using different operations with different types in long run of tests or benchmarks. If say division is used 100 times less than addition, we shouldn't complicate ceval loop to optimize it.
History
Date User Action Args
2016-02-06 08:37:30serhiy.storchakasetrecipients: + serhiy.storchaka, lemburg, rhettinger, mark.dickinson, pitrou, vstinner, casevh, skrah, Yury.Selivanov, yselivanov, josh.r, zbyrne
2016-02-06 08:37:30serhiy.storchakasetmessageid: <1454747850.83.0.335129209967.issue21955@psf.upfronthosting.co.za>
2016-02-06 08:37:30serhiy.storchakalinkissue21955 messages
2016-02-06 08:37:30serhiy.storchakacreate