http://llvm.org/bugs/show_bug.cgi?id=8227
Summary: [Unit
Test][SupportTests.raw_ostreamTest.Types_{Unb,B}uffere
d] Failure: Windows adds an extra 0 to exponent.
Product: new-bugs
Version: trunk
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P
Component: new bugs
AssignedTo: [email protected]
ReportedBy: [email protected]
CC: [email protected]
SupportTests.raw_ostreamTest.Types_{Unb,B}uffered fail with:
[ RUN ] raw_ostreamTest.Types_Buffered
..\..\..\llvm\unittests\Support\raw_ostream_test.cpp(69): error: Value of:
printToString(1.1)
Actual: "1.100000e+000"
Expected: "1.100000e+00"
[ FAILED ] raw_ostreamTest.Types_Buffered (1 ms)
[ RUN ] raw_ostreamTest.Types_Unbuffered
..\..\..\llvm\unittests\Support\raw_ostream_test.cpp(100): error: Value of:
printToStringUnbuffered(1.1)
Actual: "1.100000e+000"
Expected: "1.100000e+00"
[ FAILED ] raw_ostreamTest.Types_Unbuffered (1 ms)
This seems to be another case of MSVC adding an extra 0 to the exponent. What
does the standard say about this? If it's not defined how many 0's there should
be, or it's implementation defined, then the test should be fixed. If Microsoft
is wrong, I think we should correct it in code if it's not too difficult.
--
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
LLVMbugs mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
