This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Porting to H8S
- To: bartv at redhat dot com
- Subject: Re: [ECOS] Porting to H8S
- From: "hansi hansi" <hansi86 at hotmail dot com>
- Date: Fri, 09 Mar 2001 14:01:21
- Cc: ecos-discuss at sources dot redhat dot com
Thanks a lot
>From: Bart Veer <bartv@redhat.com>
>Reply-To: bartv@redhat.com
>To: hansi86@hotmail.com
>CC: ecos-discuss@sources.redhat.com
>Subject: Re: [ECOS] Porting to H8S
>Date: Fri, 9 Mar 2001 12:42:22 GMT
>
> >>>>> "Hansi" == hansi hansi <hansi86@hotmail.com> writes:
>
> >> > Another thing that I saw is that the GNUPro tools not supports
> >> > ELF with the H8. Is this a problem?
> >>
> >> That is likely to be a problem. Some of the compiler/linker
> >> functionality that eCos uses, e.g. constructor priority
> >> ordering, are relatively easy when using ELF image format but
> >> not with older formats.
>
> Hansi> Is the problem for a to old implementation of the compiler
> Hansi> or is the problem inside the COFF format. Do you think that
> Hansi> there is a way to make an port to the H8S?
>
>The problem is with COFF format. Things like constructor priority
>ordering and linker garbage collection are implemented using large
>numbers of linker sections. Older image formats like a.out and COFF
>limit the number of linker sections you can have, ELF does not. To
>port eCos to the H8 it would probably be easiest to implement ELF
>support in the compiler and binutils first, rather than try to modify
>eCos to work around tool limitations. For more information on what
>might be involved, see the binutils and gcc projects on
>sources.redhat.com.
>
>Bart
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.