Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 324917 - Enable metaonly modules to declare generated fxns to avoid removal from configuro whole_program optimization
Summary: Enable metaonly modules to declare generated fxns to avoid removal from confi...
Status: RESOLVED WONTFIX
Alias: None
Product: RTSC
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Dave Russo CLA
QA Contact:
URL:
Whiteboard: target:3.30
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-09 20:21 EDT by Chris Ring CLA
Modified: 2014-01-22 17:32 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Ring CLA 2010-09-09 20:21:01 EDT 
If a metaonly module contributes a template (via @Template) for the generated C file, and that template generates a fxn, and the configuro flow is used on a TI target, _and_ a whole_program profile is used <phew!>, the fxn will be optimized out of the pre-linked library.  When that prelinked lib is linked into an app, the generated fxns won't be there when someone (like the app) tries to call them, and a linker error will result.

TI toolchains provide a #pragma FUNC_EXT_CALLED() to keep a fxn even though there are no external references to it.  If the metaonly module declares these 'extern fxns' in the .xdc file, XDC could use this pragma to keep these fxns in the pre-linked lib.
Comment 1 Dave Russo CLA 2014-01-22 17:32:25 EST 
whole program support has been deferred indefinitely and when it comes back there may be better way to create "partial links" of libraries.