Debug information missing when -gc-section option is used
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GNU Arm Embedded Toolchain |
New
|
Undecided
|
Unassigned | ||
Bug Description
Hello,
Giving the files t1.c ,t2.c, t2.h which contain secure entry functions.
$cat t1.c
#include "t2.h"
int __attribute_
{
return func1(x);
}
int __attribute_
{
return func2(x);
}
int main()
{
return 0;
}
$cat t2.c
#include "t2.h"
int func1(int x)
{
return x + 3;
}
int func2(int x)
{
return x - 2;
}
$cat t2.h
#ifndef SECURE_FUNC_H_
#define SECURE_FUNC_H_
extern int func1(int x);
extern int func2(int x);
#endif /* SECURE_FUNC_H_ */
1. Compiling them with the following options:
-mcpu=cortex-m33 -mthumb -mfloat-abi=hard -mfpu=fpv5-sp-d16 -O0 -fmessage-length=0 -fsigned-char -ffunction-sections -fdata-sections -mcmse -g -c t2.c t1.c -Wunused -Wuninitialized -Wall -Wextra -Wmissing-
2. Then linking them with arm-none-eabi-gcc -mcpu=cortex-m33 -mthumb -mfloat-abi=hard -mfpu=fpv5-sp-d16 -O0 -fmessage-length=0 -fsigned-char -ffunction-sections -fdata-sections -mcmse -g -Wl,-section-
3. arm-none-
Search for func1 or func2 . There is no debug information for func1 and func2
But, if instead of the files t1.c and t2.c you are using the file t3.c (which contains the same functions but they are written in just one file), by repeating steps 1 to 3, the debug information for func1 and func2 is now present in the objdump dump file.
$cat t3.c
int func1(int x)
{
return x + 3;
}
int func2(int x)
{
return x - 2;
}
int __attribute_
{
return func1(x);
}
int __attribute_
{
return func2(x);
}
int main()
{
return 0;
}
I found the following patch from here: http://
Could you please let me know if it's a known issue or if you have any plans for fixing it?
Best Regards,
Darius Galis
| SRINATH PARVATHANENI (sripar01) wrote | #1 |
| Darius Galis (dariusg94) wrote | #2 |
| Darius Galis (dariusg94) wrote | #3 |
| SRINATH PARVATHANENI (sripar01) wrote | #4 |
| Alex Coplan (alecop) wrote | #5 |
Hi Darius,
Thanks for posting this.
I have tested the mentioned issue with latest GCC for t1.c and t2.c separate files and could not reproduce the issue and debug information for the functions func1 and func2 is available in the generated executable.
$ arm-none-eabi-gcc -mcpu=cortex-m33 -mthumb -mfloat-abi=hard -mfpu=fpv5-sp-d16 -O0 -fmessage-length=0 -fsigned-char -ffunction-sections -fdata-sections -mcmse -g -c t2.c t1.c -Wunused -Wuninitialized -Wall -Wextra -Wmissing-
t1.c:2:43: warning: no previous declaration for 'secure_func1' [-Wmissing-
2 | int __attribute_
| ^~~~~~~~~~~~
t1.c:6:43: warning: no previous declaration for 'secure_func2' [-Wmissing-
6 | int __attribute_
| ^~~~~~~~~~~~
$ arm-none-eabi-gcc -mcpu=cortex-m33 -mthumb -mfloat-abi=hard -mfpu=fpv5-sp-d16 -O0 -fmessage-length=0 -fsigned-char -ffunction-sections -fdata-sections -mcmse -g -Wl,-section-
$ arm-none-
<67> DW_AT_name : (indirect string, offset: 0x15a): func1
$ arm-none-
<4a> DW_AT_name : (indirect string, offset: 0x148): func2
$ arm-none-eabi-gcc -v
Using built-in specs.
Supported LTO compression algorithms: zlib
gcc version 11.0.0 20210107 (experimental)
$ arm-none-eabi-ld -v
GNU ld 2.35.50.20210107
Could you please include with which Embedded Toolchain you observed above issue. That might have been build with old binuilts.
Regards,
Srinath.