AM6421: there is a GCC attribute not working in R5F core.

Jaxon JIANG

Prodigy 80 points

Part Number: AM6421

Tool/software:

Hi there,

Thanks for your clear response.

I am interested in learning about the destructor attribute in the R5F core.

The destructor attribute does not execute when the program exits from the main() function.

However, the constructor attribute functions when entering the main() function.

Kindly provide a proper method for using the destructor attribute.

Jaxon

5 months ago

0 Ki 5 months ago

TI__Guru**** 472221 points

Hello Jaxon,

Are you using the GCC compiler?

Thanks

0 Jaxon JIANG 5 months ago in reply to Ki

Prodigy 80 points

Hello Ki,

My project type and tool-chain are as below.

Regarding this matter, do you have any recommendations on how to address it?

Jaxon

0 Ki 5 months ago in reply to Jaxon JIANG

TI__Guru**** 472221 points

Thank you for clarifying. I will bring this thread to the attention of the compiler experts for further comment.

0 George Mock 5 months ago in reply to Ki

TI__Guru**** 251120 points

Thank you for notifying us of this problem. I am able to reproduce the same behavior. I filed the entry EXT_EP-12714 to have this investigated.

Jaxon JIANG said:
provide a proper method for using the destructor attribute.

As a workaround, use the standard RTS function atexit, which is declared in <stlib.h>. For example:

    atexit(function_name_here);

Thanks and regards,

-George

0 Jaxon JIANG 5 months ago in reply to George Mock

Prodigy 80 points

Hi George,

Thank you for your solution. I'm glad to see TI addressing this issue.

Currently, it appears that only the unsupported __attribute__((destructor)) has been addressed with a workaround,

while __attribute__((destructor(x))) remains unsupported.

Do you have a better approach to resolve this?

Best regards,
Jaxon

0 George Mock 5 months ago in reply to Jaxon JIANG

TI__Guru**** 251120 points

Jaxon JIANG said:
__attribute__((destructor(x))) remains unsupported

That's correct.

Jaxon JIANG said:
Do you have a better approach to resolve this?

Only in a limited way. The functions registered with atexit are called in reverse order of registration, i.e. the function registered last will be executed first.

Thanks and regards,

-George

Processors

Processors forum

AM6421: there is a GCC attribute not working in R5F core.