From: Jonathan Larmour <jlarmour@redhat.com>
To: "Lewin A.R.W. Edwards" <larwe@larwe.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ARM Thumb - not working under Linux either
Date: Fri, 09 Feb 2001 13:48:00 -0000 [thread overview]
Message-ID: <3A846595.AA61BFFA@redhat.com> (raw)
In-Reply-To: <4.3.2.7.2.20010209152422.00b3e1a0@larwe.com>
"Lewin A.R.W. Edwards" wrote:
>
> Hello Jonathan,
>
> > > /tmp/ccSGafJS.s:544: Error: byte or halfword not valid for base register
> > > make[1]: *** [src/debug/dbg_gdb.o.d] Error 1
> >
> >It's a bug in gcc's reload. I've talked with people on the binutils list
>
> Good, glad to know it is a known/recogized problem and not the evil demon
> riding on my shoulder. And at least now I can build the CVS sources of
> eCos, which is a big step.
>
> Do you have any insight on why I can't get eCos compiled with Thumb
> interworking? It would be an acceptable workaround for me if I could have
> the OS in 32-bit mode and my app in Thumb mode, since the friskier parts
> are all in my app anyway. At the moment, we are only demoing the technology
> so it isn't vital to get everything tweaked to perfection; the final
> firmware doesn't have to ship until Q3 :)
I had a quick look. What you are seeing is messages like the following?
home/jlarmour/sourceware/test/arm-elf/H-i686-pc-linux-gnu/lib/gcc-lib/arm-elf/2.97/../../../../arm-elf/bin/ld:
_div_df.o(__divdf3): warning: interworking not enabled.
This object is actually from libgcc - part of the compiler. It has not been
built with -mthumb-interwork.
You probably need to edit (in your gcc sources) gcc/config/arm/t-arm-elf
and uncomment:
# MULTILIB_OPTIONS += mno-thumb-interwork/mthumb-interwork
# MULTILIB_DIRNAMES += normal interwork
# MULTILIB_EXCEPTIONS += *mapcs-26/*mthumb-interwork*
Then rebuild your compiler from scratch.
If that works, I'll add it to the thumb gcc building instructions.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
next prev parent reply other threads:[~2001-02-09 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 11:01 Lewin A.R.W. Edwards
2001-02-09 9:46 ` Jonathan Larmour
2001-02-09 12:47 ` Lewin A.R.W. Edwards
2001-02-09 13:48 ` Jonathan Larmour [this message]
2001-02-10 18:43 ` Lewin A.R.W. Edwards
2001-02-09 10:15 ` Bart Veer
2001-02-09 12:55 ` Lewin A.R.W. Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A846595.AA61BFFA@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=larwe@larwe.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).