search

cbysnoopy / python-on-a-chip

Automatically exported from code.google.com/p/python-on-a-chip
0 stars 0 forks source link

Fix endian issue (again) #45

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
ipm> print 3.14
-490.564453 
ipm> print 1.0
 0.000000 

What is the expected output? What do you see instead?
3.140000
1.000000

Original issue reported on code.google.com by dwhall...@gmail.com on 7 Sep 2009 at 3:51

GoogleCodeExporter commented 9 years ago 
When this issue is resolved, change system test t244.py to follow what the 
comment 
says.

Original comment by dwhall...@gmail.com on 7 Sep 2009 at 3:56

GoogleCodeExporter commented 9 years ago 
Created branch for work: https://python-on-a-
chip.googlecode.com/svn/branches/issue_0245_fix_endian_issue

Original comment by dwhall...@gmail.com on 7 Sep 2009 at 8:37

GoogleCodeExporter commented 9 years ago 
Uncommented float test in t244.py.  Added system test t245.py.  Fixed syntax 
error in 
src/vm/obj.c (comments around text after #endif).  Fixed mem_getFloat() so that 
BIG_ENDIAN architectures perform byte swap for float.  PyMite images continue 
to use 
little-endian formatting.  Platforms, at91sam7s-ek and mbed are set to little 
endian.

Original comment by dwhall...@gmail.com on 8 Sep 2009 at 2:06

GoogleCodeExporter commented 9 years ago 
System tests pass.  Merged branch issue_0245_fix_endian_issue.  Mainlined.  See 
r380

Original comment by dwhall...@gmail.com on 8 Sep 2009 at 2:10

GoogleCodeExporter commented 9 years ago 
Changing Milestone-r10 to Milestone-r09

Original comment by dwhall...@gmail.com on 7 Mar 2010 at 6:26

GoogleCodeExporter commented 9 years ago 
Changed r09 to R09

Original comment by dwhall...@gmail.com on 12 Mar 2010 at 8:22

GoogleCodeExporter commented 9 years ago

Original comment by dwhall...@gmail.com on 13 Mar 2010 at 1:30