From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4 kernel & gcc code generation: a bug?
Date: 6 Feb 2001 23:46:28 -0800 [thread overview]
Message-ID: <95qugk$brs$1@cesium.transmeta.com> (raw)
In-Reply-To: <3A8108F8.2476.21D0F5@localhost>
Followup to: <3A8108F8.2476.21D0F5@localhost>
By author: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
In newsgroup: linux.dev.kernel
>
> You'll notice that %edx is not pushed at the start of the function.
> Unless the caller saves that, edx will be spilled. Depending on the
> level of optimization this can be bad. Am I wrong?
>
Yes. %eax, %edx and %ecx are defined as caller-saved registers. Each
function is free to clobber them at will.
Now, if you saw the same for %ebx, %ebp, %esi or %edi, that would be
bad.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-07 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 7:36 2.4 kernel & gcc code generation: a bug? Ulrich Windl
2001-02-07 7:46 ` H. Peter Anvin [this message]
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='95qugk$brs$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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