public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Ulrich Drepper <drepper@redhat.com>
Cc: libc-hacker@sources.redhat.com
Subject: Re: INTERNAL_SYSCALL and function calls in arguments
Date: Sat, 10 Apr 2004 18:38:00 -0000	[thread overview]
Message-ID: <je4qrr1xvl.fsf@sykes.suse.de> (raw)
In-Reply-To: <407825B0.1010401@redhat.com> (Ulrich Drepper's message of "Sat, 10 Apr 2004 09:49:52 -0700")

Ulrich Drepper <drepper@redhat.com> writes:

> Andreas Schwab wrote:
>
>> Here is a patch to fix the INTERNAL_SYSCALL macro for x86_64 and ia64.
>> The definition on arm is probably also affected, but I can't test it.
>
> How does the generated code for all cases but the problematic one look
> like?  If more code is generated the change is no good.

Since the change only introduces temporary variables which the compiler
would create internally anyway, the compiler is perfectly capable to
optimize them away, and in all cases except sched_setaffinity the
generated code is virtually identical.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, 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:[~2004-04-10 18:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-09  7:15 Thorsten Kukuk
2004-04-09 13:45 ` Andreas Schwab
2004-04-10  7:34   ` Andreas Jaeger
2004-04-13 12:54     ` Kaz Kojima
2004-04-16 19:07       ` Ulrich Drepper
2004-04-10 16:50   ` Ulrich Drepper
2004-04-10 18:38     ` Andreas Schwab [this message]
2004-04-10 19:11       ` Ulrich Drepper
2004-04-10 22:04         ` Andreas Schwab
2004-04-13  0:28   ` Ulrich Drepper

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=je4qrr1xvl.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=drepper@redhat.com \
    --cc=libc-hacker@sources.redhat.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).