version: 4.9.1
host compiler: gcc-4.8.2
host OS: Ubuntu 14.04
target: lm32-unknown-elf
Here's the problem I see:
tm@tm-VirtualBox:~/lm32-toolchain/lm32-gcc$ ../gcc-4.9.1/configure
--prefix=/home/tm/bin --target=lm32-uclibc-elf --enable-languges=c ;
make
...
checking if /home/tm/lm32-toolchain/lm3
target: mips-elf
version: 4.4.1
There's a problem where compiling code with -fno-delayed-branch still fills
branch delay slots.
[ubxju10]/home/jupiter/tmorita/dhrystone/test 1097 % cat minlib.c
#include
int printf(const char *format, ...)
{
register int a0 asm ("a0");
register
ard Sandiford
> Subject: Re: mips-elf-gcc -fno-delayed-branch problem
> To: "Toshi Morita"
> Cc: gcc@gcc.gnu.org
> Date: Thursday, May 19, 2011, 1:03 AM
> Toshi Morita
> writes:
> > There's a problem where compiling code with
> -fno-delayed-branch still
&g
The -O1 sounds like a reasonable choice. Thanks for looking at the problem.
Toshi
--- On Sat, 5/21/11, Richard Sandiford wrote:
> From: Richard Sandiford
> Subject: Re: mips-elf-gcc -fno-delayed-branch problem
> To: "Toshi Morita"
> Cc: gcc@gcc.gnu.org
> Date: Satu
Naveen H.S. wrote:
> SH2A, SH4 and SH4A FPU targets support mode switching i.e. switching
> between single precision and double precision. Double-precision FPU
> is also available for the above mentioned targets.
>
> The option "-mfmovd" is enabled by default for SH2A which generates
> "fmov.d"
This isn't a GCC question specifically - it's more of a C language question.
I'm involved in a discussion involving C language function pointers.
The other party claims calling functions through a function pointer is
"undefined behavior" because it's not specifically mentioned in the C language
