| Summary: | provide a mechanism to suppress the compiling and linking of big.c. | ||
|---|---|---|---|
| Product: | [Technology] RTSC | Reporter: | Alan DeMars <ademars> |
| Component: | Core | Assignee: | Dave Russo <d-russo> |
| Status: | ASSIGNED --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | cring, dfriedland |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Alan DeMars
If using configuro, the --generationOnly flag may provide what you're looking for. Does that suffice? Alan is this still an issue? Can we close this bug? My thinking was that this would give us a simple path to achieving whole_program performance by including big.c in with the custom library sources. Is there a corresponding flag in the Pkg.addConfiguration() API that suppresses the compile and link of the big.c file? |