Thank you, Ian. The toolchain is an internally-developed, gcc-based, one, tied to a proprietary DSP ASIC. As for moving the calls, I've been trying to avoid such brute-force methods, relying on the power of the toolchain options, some standard; some more esoteric. As a last resort, I may have to go the brute force way. Regards, Greg -----Original Message----- From: Ian Lance Taylor [mailto:iant@xxxxxxxxxx] Sent: Thursday, December 12, 2013 3:49 PM To: Greg Hopkins Cc: gcc-help@xxxxxxxxxxx Subject: Re: ld --wrap option On Thu, Dec 12, 2013 at 10:28 AM, Greg Hopkins <Greg.Hopkins@xxxxxxx> wrote: > Resending due to urgent need. Please help if you can. Thank you. > > -----Original Message----- > > I am using the ld --wrap option of a gcc-based toolchain, and the option is working as advertised, except for the cases where wrapped functions are called from within the modules in which they (the real) functions are defined. An ojbdump of the final executable disassembly shows all calls from outside of the defining module correctly resolve to __wrap_function_name, (which is currently written to then call __real_function_name to complete the execution threads.) However, for any particular function_name, all calls to function_name from within its defining module go directly to the target, "real", function, bypassing the wrapper construct. > > Is there a gcc compiler/assembler/linker option to force all symbols to be undefined until link stage, which I believe would then cause all such bypassing calls to correctly link to the wrapper functions? I've tried --undefined=function_name; that didn't work; the intramodules direct calls still occurred. I also tried --defsym=function_name=__wrap_function_name, and that resulted in an infinitely loop branch-to-self in the target function. This is going to be an assembler option, not a compiler one. It's going to be target-specific, and you didn't mention the target. I'm not aware of any option to do this, but the place to ask would be on the mailing list for whatever assembler you are using. Why can't you just move the calls to a different compilation unit? Ian To report this email as spam click https://www.mailcontrol.com/sr/MZbqvYs5QwJvpeaetUwhCQ== . Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom More information can be found at www.csr.com. Follow CSR on Twitter at http://twitter.com/CSR_PLC and read our blog at www.csr.com/blog
