http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60528
--- Comment #4 from Steve Ellcey <sje at gcc dot gnu.org> --- I have created a new bug for the incorrect csinh results and included a cutdown test case. It looks like a GCC optimization bug. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60604 I think this bug should stay open as a defect in that GCC should print out the same output regardless of whether the compiler itself was built as a 32 bit executable or as a 64 bit executable. It does not and while that turned out not to be the cause of my test failure but it is still wrong.
