public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: James Lemke <jim@TheLemkes.ca>, gcc@gcc.gnu.org
Subject: Re: expanding builtins
Date: Mon, 27 Jun 2005 15:24:00 -0000	[thread overview]
Message-ID: <jevf3zrffs.fsf@sykes.suse.de> (raw)
In-Reply-To: <20050627142632.GG7663@sunsite.mff.cuni.cz> (Jakub Jelinek's message of "Mon, 27 Jun 2005 16:26:32 +0200")

Jakub Jelinek <jakub@redhat.com> writes:

> On Mon, Jun 27, 2005 at 10:11:50AM -0400, James Lemke wrote:
>> I have a situation where a structure is not properly aligned and I want
>> to copy it to fix this.
>> 
>> I'm aware that -no-builtin-memcpy will suppress the expansion of
>> memcpy() (force library calls) for a whole module.  Is it possible to
>> suppress the expansion for a single invocation?
>
> You can:
> #include <string.h>
> ...
> extern __typeof(memcpy) my_memcpy __asm ("memcpy");
>
> and use my_memcpy instead of memcpy in the place where you want to force
> library call.

Except that sometimes the function is actually called _memcpy at the
assembler level.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2005-06-27 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-27 14:12 James Lemke
2005-06-27 14:26 ` Jakub Jelinek
2005-06-27 15:24   ` Andreas Schwab [this message]
2005-06-27 15:30   ` James Lemke

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=jevf3zrffs.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jim@TheLemkes.ca \
    /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).