From: <cutaway@bellsouth.net>
To: "Denis Vlasenko" <vda@ilport.com.ua>,
"Jesper Juhl" <juhl-lkml@dif.dk>,
"linux-kernel" <linux-kernel@vger.kernel.org>
Cc: "Andrew Morton" <akpm@osdl.org>,
"Jeff Garzik" <jgarzik@pobox.com>,
"Domen Puncer" <domen@coderock.org>
Subject: Re: [RFC] cleanup patches for strings
Date: Tue, 21 Jun 2005 10:38:12 -0400 [thread overview]
Message-ID: <01ff01c5766e$de750be0$2800000a@pc365dualp2> (raw)
In-Reply-To: <200506211606.59233.vda@ilport.com.ua>
Congratulations, you proved that a register push is faster than a 3 byte
memory push. I believe this is exactly what I said would happen if the
autovar pointer wound up being enregistered.
However, it is NOT what GCC will generate for pushing params to static
strings.
For that you're going to get a 5 byte PUSH imm32.
----- Original Message -----
From: "Denis Vlasenko" <vda@ilport.com.ua>
To: <cutaway@bellsouth.net>; "Jesper Juhl" <juhl-lkml@dif.dk>;
"linux-kernel" <linux-kernel@vger.kernel.org>
Cc: "Andrew Morton" <akpm@osdl.org>; "Jeff Garzik" <jgarzik@pobox.com>;
"Domen Puncer" <domen@coderock.org>
Sent: Tuesday, June 21, 2005 09:06
Subject: Re: [RFC] cleanup patches for strings
Took 9574 CPU cycles Took 8068 CPU cycles
> 40: ff 75 f8 pushl 0xfffffff8(%ebp)
> 43: 58 pop %eax
> 80: 53 push %ebx
> 81: 58 pop %eax
next prev parent reply other threads:[~2005-06-21 13:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 22:46 Jesper Juhl
2005-06-21 6:58 ` cutaway
2005-06-21 11:02 ` Denis Vlasenko
2005-06-21 13:08 ` cutaway
2005-06-21 13:06 ` Denis Vlasenko
2005-06-21 14:38 ` cutaway [this message]
2005-06-21 13:52 ` Denis Vlasenko
2005-06-21 13:20 ` Denis Vlasenko
2005-06-21 8:59 ` Alexey Dobriyan
2005-06-21 9:31 ` Jörn Engel
2005-06-21 20:47 ` Jesper Juhl
2005-06-21 9:04 ` Andrey Panin
2005-06-21 10:59 ` Denis Vlasenko
2005-06-21 21:24 ` Jean Delvare
2005-06-21 22:33 ` cutaway
2005-06-21 21:49 ` Jean Delvare
2005-06-21 23:11 ` cutaway
2005-06-22 0:16 ` Brian Gerst
2005-06-21 21:12 ` Horst von Brand
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='01ff01c5766e$de750be0$2800000a@pc365dualp2' \
--to=cutaway@bellsouth.net \
--cc=akpm@osdl.org \
--cc=domen@coderock.org \
--cc=jgarzik@pobox.com \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@ilport.com.ua \
/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
all inboxes | Powered by JetHome®