Hi!
On Thu, 23 Feb 2012 08:42:53 +0900, Kaz Kojima kkoj...@rr.iij4u.or.jp wrote:
Thomas Schwinge tho...@codesourcery.com wrote:
Kaz, is my understanding correct, that I simply use sh64-elf as target,
and again the sh-sim board? Should I be setting a specific CPU when
configuring GCC, or
Hi!
On Fri, 24 Feb 2012 00:08:00 +0900, Kaz Kojima kkoj...@rr.iij4u.or.jp wrote:
Thomas Schwinge tho...@codesourcery.com wrote:
/scratch/tschwing/FM_sh64-elf/src/gcc-mainline/libgcc/libgcc2.c: In
function '__powisf2':
Hello,
On Fri, 2012-02-24 at 22:23 +0100, Thomas Schwinge wrote:
Confirming that this patch makes GCC trunk buildable again.
Comparing to the 4.6 testsuite results, with trunk there are about 700
new execution failures in g++, gcc, libstdc++, about 100 ``compilation
failed to produce
Hi!
On Wed, 22 Feb 2012 20:29:11 +0100, I wrote:
On Wed, 22 Feb 2012 09:39:29 -0700, Kevin Buettner kev...@redhat.com wrote:
On Wed, 22 Feb 2012 15:52:03 +0100
Thomas Schwinge tho...@codesourcery.com wrote:
And, any quick suggestion for a sh64 sim testing configuration, too? My
Hi!
This is about sh and sh64 GDB sim testing for the whole toolchain. (I
also do have sh4a hardware available, where testing is working fine.)
Kaz, could you please have a look whether this looks basically sane, that
my assumptions and the results I'm getting are about right, etc.?
On Wed, 22
Thomas Schwinge tho...@codesourcery.com wrote:
This is about sh and sh64 GDB sim testing for the whole toolchain. (I
also do have sh4a hardware available, where testing is working fine.)
Kaz, could you please have a look whether this looks basically sane, that
my assumptions and the results
