public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Greg Hopkins <Greg.Hopkins@csr.com>
To: "Ángel González" <keisial@gmail.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: RE: ld --wrap option
Date: Fri, 13 Dec 2013 12:51:00 -0000	[thread overview]
Message-ID: <1875ABFC44A4C049BF86786B1EE9A6DD179BD9AC@SUNAMSEXM01.AMERICAS.ROOT.PRI> (raw)
In-Reply-To: <52AA5CD4.7090508@gmail.com>

Thanks, Ángel.  I can see how a "#define fn __wrap_fn", coupled with a "#undef fn" at fn definition would do the trick.

Regards,
Greg

-----Original Message-----
From: Ángel González [mailto:keisial@gmail.com] 
Sent: Thursday, December 12, 2013 6:03 PM
To: Greg Hopkins
Cc: gcc-help@gcc.gnu.org
Subject: Re: ld --wrap option

On 12/12/13 19:28, Greg Hopkins wrote:
> Resending due to urgent need.  Please help if you can.  Thank you.
>
> Regards,
> Greg
If you are trying to wrap the funcion from the same file where it's defined, there are a few easy tricks to wrap it, from the original function to #defining the name to the wrapper.
Although the best solution coulb be to move it to a separate file.




 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

  reply	other threads:[~2013-12-13 12:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12 18:29 Greg Hopkins
2013-12-12 22:48 ` Ian Lance Taylor
2013-12-12 23:00   ` Greg Hopkins
2013-12-13  1:03 ` Ángel González
2013-12-13 12:51   ` Greg Hopkins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-09 23:53 Greg Hopkins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1875ABFC44A4C049BF86786B1EE9A6DD179BD9AC@SUNAMSEXM01.AMERICAS.ROOT.PRI \
    --to=greg.hopkins@csr.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=keisial@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).