From: Grant Grundler <grundler@parisc-linux.org>
To: Joel Soete <soete.joel@scarlet.be>
Cc: linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: in ccio_io_pdir_entry(),BUG_ON() seems to break gcc-4.2 optimization?
Date: Sun, 29 Jun 2008 14:52:42 -0600 [thread overview]
Message-ID: <20080629205242.GA7629@colo.lackof.org> (raw)
In-Reply-To: <4866BA91.9040607@scarlet.be>
On Sat, Jun 28, 2008 at 10:26:25PM +0000, Joel Soete wrote:
...
>> What's wrong with "ci" variable? It's just another register.
> well the idea is that "ci" variable is just there as a tmp variable just
> used in this asm code, right.
> so why not simply get rid of its declaration (btw save a line of code ;-))
> and just use a common temporay reg as r19?
No - don't do that. Let the compiler do the work of allocating registers.
It's really good at it. :) Much better than you and I combined. :)
All we need to do is tell the compiler we need a register.
cheers,
grant
next prev parent reply other threads:[~2008-06-29 20:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 6:28 in ccio_io_pdir_entry(),BUG_ON() seems to break gcc-4.2 optimization? Joel Soete
2008-06-28 20:23 ` Grant Grundler
2008-06-28 22:26 ` Joel Soete
2008-06-28 22:45 ` John David Anglin
2008-06-29 20:52 ` Grant Grundler [this message]
2008-06-30 18:28 ` Joel Soete
2008-07-02 4:28 ` Grant Grundler
2008-07-02 18:01 ` Joel Soete
2008-07-07 15:28 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2008-07-08 9:04 Joel Soete
2008-06-20 6:37 Joel Soete
2008-06-15 12:37 in ccio_io_pdir_entry(), BUG_ON() " rubisher
2008-06-16 11:37 ` in ccio_io_pdir_entry(),BUG_ON() " rubisher
2008-06-19 16:04 ` in ccio_io_pdir_entry(), BUG_ON() " Grant Grundler
2008-06-19 19:44 ` Joel Soete
2008-06-19 22:48 ` John David Anglin
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=20080629205242.GA7629@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=linux-parisc@vger.kernel.org \
--cc=soete.joel@scarlet.be \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.