This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
New port m32r-linux
- From: Doug Evans <dje at transmeta dot com>
- To: Kazuhiro Inaoka <inaoka dot kazuhiro at renesas dot com>
- Cc: binutils at sources dot redhat dot com
- Date: Wed, 18 Jun 2003 23:54:44 -0700 (PDT)
- Subject: New port m32r-linux
- References: <00a001c3361f$9bb7b5a0$2569910a@hoku.renesas.com>
Kazuhiro Inaoka writes:
> Hello
>
> I am preparing porting of m32r-linux target GNU tools.
>
> At the first,
> I think that it needs new relocations (R_M32R_GOT24, R_M32R_26_PLTREL,
> R_M32R_GOT24 .. .etc).
> Now we have only m32r-elf target.
> Would you tell me the process of porting new targets if there are any
> policies?
>
> Do we need to keep the compatiblity of m32r-linux relocations with m32r-elf?
> I want to change relocation type form REL to RELA for porting linux form
> now.
> Please give me advices!
> Then I will create patches.
fwiw, imo, and all that ...
Having m32r-elf.o be incompatible with m32r-linux.o would be a
mistake. Don't go there. They must be compatible.
You can certainly choose to make m32r-linux RELA, leaving
making m32r-elf RELA (while still supporting REL) for another day.
The point is having a clear and simple upgrade path that is compatible
and is defined on day 1 and isn't an afterthought.
As for the process of porting new targets: use the standard operating
procedure of finding an existing target that is close to what you
want and then use it as boilerplate.
fwiw, imo, and all that.