This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Build problems; Please help
- To: "'gcc at gcc dot gnu dot org'" <gcc at gcc dot gnu dot org>
- Subject: Re: Build problems; Please help
- From: Jagat Brahma <jbrahma at riverdelta dot com>
- Date: Wed, 26 Jul 2000 19:50:09 -0400
Hi Nick,
>There are two ways to tell the assembler that is being given Thumb
>instructions - via a command line switch or via a pseudo op in the
>assembly source code itself. GAS supports both methods, but the
>command line switch is less flexible, since it implies that the entire
>source file only contains Thumb instructions, which would prohibit
>mixing ARM and Thumb instructions in the same file.
>
>Thus gcc prefers to use the pseudo op method. What it should be doing
>is placing a:
>
> .code 16
>
>pseudo op at the start of the assembly code for every function that it
>compiles. This in turn should tell the assembler to expect Thumb
>instructions and then everything should work.
I am learning...
>It would appear that in your case that this ".code 16" directive is
>not being emitted, and this is the real bug. Can you check the
>assembler output of gcc, so see what the function introduction looks
>like ?
I didn't see that directive (.code 16). I have attached the intermediate
files and the commands used to compile, with this mail so that you can
also take a look at the file. It did compile properly when I added that
directive before the function definition.
So that's the real Bug.
mail me if you need anything else
Happy Hacking
JP Brahma