From: Nick Clifton <nickc@redhat.com>
To: aram bharathi <arambharathi@linuxmail.org>
Cc: Ian Lance Taylor <ian@airs.com>,
gcc@gcc.gnu.org, binutils@sourceware.org
Subject: Re: interworking problem
Date: Tue, 22 Feb 2005 14:45:00 -0000 [thread overview]
Message-ID: <421AF9A4.4030500@redhat.com> (raw)
In-Reply-To: <20050222042227.BEF75416119@ws5-2.us4.outblaze.com>
Hi Aram,
> i have gone through the a.out file after this error.
> that is producing full of arm instructions other than the main
> function(which is compiled for -mthumb).
> where should i change for this corresponding error.
It is not clear what question you are asking here.
Ian has pointed out that you should be compiling your program with the
-mthumb-interwork switch specified on the gcc command line.
> i have added one new add instruction in thumb mode. based on that
> i have written one sample program to emit the corresponding new
> instruction. gcc works fine. when i assemble the function it emits
> correct opcode. but when i give the same function to the ld it
> emits full of arm instructions instead of thumb instructions.
> which routine checks for this corresponding change.
Again this is not clear. Do you mean that when the linker is creating
the executable that it is inserting some ARM-encoded instructions into
the output, or that it is somehow magically transforming your
THUMB-encoded instructions into ARM-encoded instructions ?
Perhaps it would help if you could provide a *small* example program and
the command lines you use to compile it, as well as description of
what is wrong with the resulting executable.
Cheers
Nick
prev parent reply other threads:[~2005-02-22 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 12:56 aram bharathi
2005-02-22 14:45 ` Nick Clifton [this message]
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=421AF9A4.4030500@redhat.com \
--to=nickc@redhat.com \
--cc=arambharathi@linuxmail.org \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=ian@airs.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).