Thanks. We are close to branching an RTEMS release.
Sounds like this will be a good thing to switch to
immediately after that.
--joel
Paul Brook wrote:
We chose arm-elf as the starting point years. If we need to
move to arm-eabi as the starting point that is OK. We usually
just chose the CPU
> We chose arm-elf as the starting point years. If we need to
> move to arm-eabi as the starting point that is OK. We usually
> just chose the CPU-coff or CPU-elf as a starting point
> for CPU-rtems.
I highly recommend switching to the EABI.
If you want to support recent (Thumb-2) CPUs I'd expe
Paul Brook wrote:
arm-rtems4.9-gcc -mfpu=neon -mfloat-abi=softfp -mcpu=arm7tdmi -c
test_neon.c
#if !defined(__ARM_NEON__)
#error "Neon not supported"
#endif
void neon_code(void)
{
asm volatile ("vldr d18,[fp,#-32]");
}
Works fine here. Either your assembler is busted, or there is some
Paul Brook wrote:
On Wednesday 06 August 2008, Joseph S. Myers wrote:
On Wed, 6 Aug 2008, Joel Sherrill wrote:
$ arm-rtems4.9-gcc -mfpu=neon -mfloat-abi=softfp -mcpu=arm7tdmi -c
test_neon.c /tmp/ccBzigjD.s: Assembler messages:
/tmp/ccBzigjD.s:13: Error: selected processor does not supp
On Wednesday 06 August 2008, Joseph S. Myers wrote:
> On Wed, 6 Aug 2008, Joel Sherrill wrote:
> > $ arm-rtems4.9-gcc -mfpu=neon -mfloat-abi=softfp -mcpu=arm7tdmi -c
> > test_neon.c /tmp/ccBzigjD.s: Assembler messages:
> > /tmp/ccBzigjD.s:13: Error: selected processor does not support `vldr
> > d1
> arm-rtems4.9-gcc -mfpu=neon -mfloat-abi=softfp -mcpu=arm7tdmi -c
> test_neon.c
>
> #if !defined(__ARM_NEON__)
> #error "Neon not supported"
> #endif
>
> void neon_code(void)
> {
> asm volatile ("vldr d18,[fp,#-32]");
> }
Works fine here. Either your assembler is busted, or there is something
On Wed, 6 Aug 2008, Joel Sherrill wrote:
> $ arm-rtems4.9-gcc -mfpu=neon -mfloat-abi=softfp -mcpu=arm7tdmi -c
> test_neon.c /tmp/ccBzigjD.s: Assembler messages:
> /tmp/ccBzigjD.s:13: Error: selected processor does not support `vldr
> d18,[fp,#-32]'
>
>
> So with that combination of options gcc
Joseph S. Myers wrote:
On Wed, 6 Aug 2008, Joel Sherrill wrote:
I see the code for arm_neon_ok. If I can make that test fail,
we are in business. I tried the cpp part of the following code
and it doesn't trip for:
arm-rtems4.9-gcc -mfpu=neon -mfloat-abi=softfp -mcpu=arm7tdmi -c test_neon.
On Wed, 6 Aug 2008, Joel Sherrill wrote:
> I see the code for arm_neon_ok. If I can make that test fail,
> we are in business. I tried the cpp part of the following code
> and it doesn't trip for:
>
> arm-rtems4.9-gcc -mfpu=neon -mfloat-abi=softfp -mcpu=arm7tdmi -c test_neon.c
>
> But when I a
Joseph S. Myers wrote:
On Wed, 6 Aug 2008, Joel Sherrill wrote:
Hi,
I have just posted the first gcc test results
for arm-rtems to gcc-testresults.
C/C++: http://gcc.gnu.org/ml/gcc-testresults/2008-08/msg00608.html
Ada: http://gcc.gnu.org/ml/gcc-testresults/2008-08/msg00601.html
There were
On Wed, 6 Aug 2008, Joel Sherrill wrote:
> Hi,
>
> I have just posted the first gcc test results
> for arm-rtems to gcc-testresults.
> C/C++: http://gcc.gnu.org/ml/gcc-testresults/2008-08/msg00608.html
> Ada: http://gcc.gnu.org/ml/gcc-testresults/2008-08/msg00601.html
>
> There were a lot (2116
Hi,
I have just posted the first gcc test results
for arm-rtems to gcc-testresults.
C/C++: http://gcc.gnu.org/ml/gcc-testresults/2008-08/msg00608.html
Ada: http://gcc.gnu.org/ml/gcc-testresults/2008-08/msg00601.html
There were a lot (2116) of "unexpected failures"
for C, but most (1997 by gre
12 matches
Mail list logo
