Cross Compiler Input

Question

What are the limitations of inputting a bare metal cross-compiler ... as if it does not compile programs with pointers or mullocks ... or something that will require more than the basic equipment ... also how can you find these restrictions.

I also wanted to ask ... I built a cross-compiler for target mips. I need to create a mips executable using this cross-compiler ... but I can’t find where the executable is ... as it has 1 executable which I found mipsel-linux-cpp which should compile, compile and bind and then create a.out, but it does not do this ...

However ./cc1 gives the mips assembly ........

There is an installation folder that has a gcc executable that uses the i386 build and then gives exe ... I don't understand how gcc exe can give i386 and not the mips build when I specified the target as mips ....

Please help them really unable to understand what is happening ...

I followed the stage. 1. Installed binutils 2.19 2. gcc configured for mips .. (g ++, core)

Answer 1

I would suggest that you should start two separate questions.

GNU - , GNU. - GCC Newlib C, syscall, . , - . . - - UART stdin/stdout/stderr, . , -, printf(), . sysck()/sbrk_r() syscall - , malloc() .

GNU ++ Newlib . ++, C ( crt0.s) , . , , , SDRAM, , MMU ..; , .

MIPS, , "Building Bare Metal ARM with GNU" , , - , Newlib.

, mipsel-linux-cpp, " ", Linux. ", ", , , , . , , . , , (-nostdlib), , , . , , GNU-ARM, , , , , Windows, ( , , Cygwin)

Answer 2

, - .

. MIPS. , , - , " " . -. , . , , , , , , .

, , - , , . , , , , , . . , , .

- C , . C - . , C . , , , . , C .

, - . . , , , , , C . , - C , . (, , -), C. , printf ( "hello world" ); .

, - , . - - , , . , . , , .

, . . , , , . . Stackoverflow - , . ! ;

C

,

Linux -