From: David Miller <davem@davemloft.net>
To: harvey.harrison@gmail.com
Cc: bunk@kernel.org, wli@holomorphy.com, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: sparc vs. gcc 4.3
Date: Mon, 03 Mar 2008 14:02:03 -0800 (PST) [thread overview]
Message-ID: <20080303.140203.201465683.davem@davemloft.net> (raw)
In-Reply-To: <1204580471.22933.17.camel@brick>
From: Harvey Harrison <harvey.harrison@gmail.com>
Date: Mon, 03 Mar 2008 13:41:11 -0800
> Could you hide the asm inside an actual function and annotate the
> function with __used?
Won't work, the asm needs to be inlined because it needs to:
1) Know where local variables are located
2) Has to run in the context of the stack frame the
call site runs in so that the tail-call it's doing works
And actually all of this is why the sparc64 fix turned out to
be so invasive, and I'll need to do the same for sparc32
as a result.
next prev parent reply other threads:[~2008-03-03 22:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 19:26 Adrian Bunk
2008-03-03 21:03 ` David Miller
2008-03-03 21:41 ` Harvey Harrison
2008-03-03 22:02 ` David Miller [this message]
2008-03-03 23:02 ` David Miller
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=20080303.140203.201465683.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bunk@kernel.org \
--cc=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=wli@holomorphy.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
all inboxes | Powered by JetHome®