[Bug target/44364] Wrong code with e500 double floating point

2010-06-10 Thread harry dot he at freescale dot com
--- Comment #44 from harry dot he at freescale dot com 2010-06-10 09:03 --- Thanks for your reminding, Mark. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44364

[Bug target/44364] Wrong code with e500 double floating point

2010-06-10 Thread harry dot he at freescale dot com
--- Comment #46 from harry dot he at freescale dot com 2010-06-11 01:09 --- Mark, I have reported the issue to CodeSourcery and waiting them to confirm, I guess our toolchain may need different patches for it, or there is something wrong in my validation. -- harry dot he

[Bug target/44364] Wrong code with e500 double floating point

2010-06-09 Thread harry dot he at freescale dot com
--- Comment #39 from harry dot he at freescale dot com 2010-06-09 08:59 --- Hi, Kyle Moffett, in testall.c, r9 is used by a register variable, however, in E500ABI guide, r9 should be used for parameter passing, this test case seems not reasonable. Harry He -- http

[Bug target/44364] Wrong code with e500 double floating point

2010-06-09 Thread harry dot he at freescale dot com
--- Comment #40 from harry dot he at freescale dot com 2010-06-09 09:23 --- with my toolchain (From CodeSourcery, 4.4-78), o1test gives correct behavior with built-in flags(-te500v2), but wrong behaviors with -fcaller-saves -O -fno-omit-frame-pointer -fno-dce -fno-split-wide-types

[Bug boehm-gc/41208] New: illegal instruction lwsync reported on e500

2009-09-01 Thread harry dot he at freescale dot com
instruction lwsync reported on e500 Product: gcc Version: 4.3.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: boehm-gc AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: harry dot he at freescale dot