This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [Steven Woody] M16C development using GCC, Is It Possible?
DJ Delorie <dj@redhat.com> writes:
>> i heard that gcc is also a cross-compiler, so i want to get know if
>> it can be used as an M16C compiler?
>
> Yes. The target you want to use to build gcc et al is "m32c-elf".
>
> To compile for the m16c specifically, use "m32c-elf-gcc -mcpu=m16c ..."
thanks. is that a 4.02 option? i can not find them on my 3.4 gcc man page.
>
>> in GCC's home page, there is one item:
>>
>> 'July 20, 2005
>> Red Hat Inc has contributed a port for the Renesas R8C/M16C/M32C families'
>>
>> what that really means?
>
> It means that Red Hat Inc has modified gcc (and binutils and newlib)
> to support the r8c/m16c/m32c family of processors from Renesas, and
> given those changes to the FSF to be integrated into their official
> sources.
how it going on? have it been alreay available in 4.02?
>
> gdb and a simulator are still in progress.
that seem ok since i currently only need gcc. and, because i am new to the
field , i want to ask, what is a 'simulator'? run target excutable on host
computer?
>> and in this page
>> 'http://a15177702.alturo-server.de/gcc-m16c/200504191111.html', it said, GCC
>> M16C project is totally bugy.
>
> That's a different attempt to port gcc to m16c, and has nothing to do
> with what I did.
sorry, are you the author of the new m16c/gcc code? i noticed your domain name
is redhat.
>
>> (BTW: i need compile C++ not C only)
>
> Note that I haven't gotten around to supporting C++ yet. You can try
> to build it if you want, but I had deferred it due to other more
> important issues, and haven't had a chance to work on it. It might
> "just work", you never know ;-)
do you mean, the current m16c/gcc code never compiler c++ code? if so, that is
definitely a bad news to me, since our project based on EC++ (Embedded
C++). though you pointed that i could build for my self, but in fact i can not,
i know nothing about compiler writing :(
so, i am thinking another question. if i can write the code which can pass both
the current (3.4) g++ compiler and the IAR M16C C++ compiler, so my problem
will resolved. but is it possible of the idea? i think i can use some #ifdef
statements and move any IO into stubs. how different are these two compilers
in C++ syntax?
i like to heard any suggestion, and thank you in advance.
--
steven woody (id: narke)
Pepper...is hot and scorches, just like the sun
- Politiki kouzina (2003)