Message 192179 - Python tracker

➜

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	V.E.O
Recipients	V.E.O, christian.heimes, eric.smith, mark.dickinson, skrah, vstinner
Date	2013-07-02.07:54:33
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1372751673.61.0.165693805567.issue18340@psf.upfronthosting.co.za>
In-reply-to

Content
Hi All, From my test, GCC will not enforce DFZ/FTZ only by compiler options. It needs code modify register flag. I think it's a problem with Intel Compiler. Maybe from platform.python_compiler(), these tests can identify the compiler and be skipped. But the identification is ambiguous, for in Linux it's "GCC Intel(R) C++ gcc x.x mode", in Windows it's like "MSC v.1600 32 bit (Intel)" If the support for Intel Compiler is not OK, we can pending these issues for future fix.

Hi All,

From my test, GCC will not enforce DFZ/FTZ only by compiler options. It needs code modify register flag.

I think it's a problem with Intel Compiler.
Maybe from platform.python_compiler(), these tests can identify the compiler and be skipped.
But the identification is ambiguous, for in Linux it's "GCC Intel(R) C++ gcc x.x mode", in Windows it's like "MSC v.1600 32 bit (Intel)"

If the support for Intel Compiler is not OK, we can pending these issues for future fix.

History
Date	User	Action	Args
2013-07-02 07:54:33	V.E.O	set	recipients: + V.E.O, mark.dickinson, vstinner, eric.smith, christian.heimes, skrah
2013-07-02 07:54:33	V.E.O	set	messageid: <1372751673.61.0.165693805567.issue18340@psf.upfronthosting.co.za>
2013-07-02 07:54:33	V.E.O	link	issue18340 messages
2013-07-02 07:54:33	V.E.O	create