EmbDev.net

Forum: ARM programming with GCC/GNU tools GCC Ident


von Ádám K. (akovacs)


Rate this post
useful
not useful
Hi!

I am searching for some space in Flash, and I the following is realised:
 .comment       0x00000000       0x1b
../lib/gcc/arm-elf/4.1.1/crtbegin.o
 .comment       0x00000036       0x1b
../lib/gcc/arm-elf/4.1.1/../../../../arm-
...

there are many object files containing the text "GCC: (GNU) 4.1.1
(WinARM)"

How can I disable it?

(I use gcc option -fno-ident in my sources.)

Thanks,
Ádám

von Clifford S. (clifford)


Rate this post
useful
not useful
Ádám Kovács wrote:
> Hi!
>
> I am searching for some space in Flash, and I the following is realised:
>  .comment       0x00000000       0x1b
> ../lib/gcc/arm-elf/4.1.1/crtbegin.o
>  .comment       0x00000036       0x1b
> ../lib/gcc/arm-elf/4.1.1/../../../../arm-
> ...
I have no idea what that means or where you got it from. What about it!?
Tell is what or where it is so we might interepret what you are
concerned about.

>
> there are many object files containing the text "GCC: (GNU) 4.1.1
> (WinARM)"
>
What appears in an object file and what appears in the binary are two
different things. Some information is there to help the linker and
debugger and are not incorporated into the ROM image. If you want to
find out what is where and how much space it takes, generate a link map
when you execute the linker.

von Ádám K. (akovacs)


Rate this post
useful
not useful
Clifford Slocombe wrote:
> Ádám Kovács wrote:
>> Hi!
>>
>> I am searching for some space in Flash, and I the following is realised:
>>  .comment       0x00000000       0x1b ../lib/gcc/arm-elf/4.1.1/crtbegin.o
>>  .comment       0x00000036       0x1b ../lib/gcc/arm-elf/4.1.1/../../../../arm-
>> ...
> I have no idea what that means or where you got it from. What about it!?
> Tell is what or where it is so we might interepret what you are
> concerned about.

Sorry there are lines from the *.map file.

>
>>
>> there are many object files containing the text "GCC: (GNU) 4.1.1
>> (WinARM)"
>>
> What appears in an object file and what appears in the binary are two
> different things. Some information is there to help the linker and
> debugger and are not incorporated into the ROM image. If you want to
> find out what is where and how much space it takes, generate a link map
> when you execute the linker.

You have right, I changed the linker script and the .comment section
will not appear in the binary.
(My first idea was to recompile the libc and the *.o-s with -fno-ident
option.)

von Clifford S. (clifford)


Rate this post
useful
not useful
Ádám Kovács wrote:
> Clifford Slocombe wrote:
>
> Sorry there are lines from the *.map file.
>
Ah! that makes much more sense on one line! ;-)

Please log in before posting. Registration is free and takes only a minute.
Existing account
Do you have a Google/GoogleMail account? No registration required!
Log in with Google account
No account? Register here.