This is the mail archive of the libffi-discuss@sourceware.org mailing list for the libffi project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Question] LIBFFI for SH4 (SH-Superh-Elf) Platform


Do you have the ability to run the libffi testsuite on your machine? I
recommend starting there.

GCC will define __SH4__ for you if you are actually targeting an sh4
device. Does sh4gcc call sh-elf-gcc with -m4? This will set __SH4__ for you.

Anthony


김원순(Edward Kim) wrote:
> I missed one thing..
> My First compile Options are shown below..
> Compiling D:\Work\src\libffi\build/debug.c
> sh4gcc -g -O0 -fno-strict-aliasing -DOS21_RUNTIME -DST40_OS21
> -mruntime=os21_d -Dhmp
> -DST_7109 -DARCHITECTURE_ST40 -DST_OS21 -ID:\Work\src\app/util
> -ID:\Work\src\include -IC:\STM\OSPlusR2.2.2/INCLUDE
> -ID:\Work\src\libffi\build
> -o debug.o -c D:\Work\src\libffi\build/debug.c
> My Second Trial is shown below
> Compiling D:\Work\src\libffi\build/debug.c
> sh4gcc -g -O0 -fno-strict-aliasing -DOS21_RUNTIME -DST40_OS21
> -mruntime=os21_d -Dhmp
> -DST_7109 -DARCHITECTURE_ST40 -DST_OS21 *-D__SH4__
> *-ID:\Work\src\app/util
> -ID:\Work\src\include -IC:\STM\OSPlusR2.2.2/INCLUDE
> -ID:\Work\src\libffi\build
> -o debug.o -c D:\Work\src\libffi\build/debug.c
> Would you please let me know which one is good choice..?
> Thanks..
> Regards
> Edward
>
> ------------------------------------------------------------------------
> *From:* 김원순(Edward Kim) [mailto:wskim@i-winix.com]
> *Sent:* Tuesday, June 16, 2009 9:42 AM
> *To:* 'libffi-discuss@sources.redhat.com'
> *Cc:* 'green@redhat.com'
> *Subject:* [Question] LIBFFI for SH4 (SH-Superh-Elf) Platform
>
> Dear All
> Recently, I had downloaded latest source / build tree from
> ftp://sources.redhat.com/pub/libffi/
> The version was libffi-3.0.8.
> After compiling build tree, and during debugging,
> I've got a report from my co-workers.
> He said there might be an erroneous data handling between native
> C-code & Java Code.
> He also said, Java code got a variable with the value
> 0x000000640000008E, but the native one was 0x011001100389.
> Those should be the same one, however the result wasn't.
> Now I have a question, & I'd like to get an advice to port & make
> right build tree.
> My system is as follows.
> CPU : STi7101 (SH4 architectured),
> CPU manufacturer : ST Microelectronics (STM)
> Operating System : OS21 (RTOS from STM)
> Compiler : ST customized gcc.
> My previous build
> Used target platform : SH in build tree.
> Thanks in advance for your help..
> Best Regards
> Edward Kim


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]