From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Florian Fainelli <florian@openwrt.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH] OCTEON: workaround linking failures with gcc-4.4.x 32-bits toolchains
Date: Mon, 2 Aug 2010 15:59:04 +0100 [thread overview]
Message-ID: <20100802145904.GA6123@linux-mips.org> (raw)
In-Reply-To: <4C50AC0C.9010507@caviumnetworks.com>
On Wed, Jul 28, 2010 at 03:15:40PM -0700, David Daney wrote:
> >executables by default, we will produce __lshrti3 in sched_clock() which is
> >never resolved so the kernel fails to link. Unconditionally use the inline
> >assembly version as suggested by David Daney, which works around the issue.
> >
> >CC: David Daney<ddaney@caviumnetworks.com>
> >Signed-off-by: Florian Fainelli<florian@openwrt.org>
>
> Acked-by: David Daney <ddaney@caviumnetworks.com>
Applied - but maybe we should just add lshrti3 instead? We already have
ashldi3, ashrdi3 and lshrdi3.
Ralf
next prev parent reply other threads:[~2010-08-02 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 22:13 [PATCH] OCTEON: workaround linking failures with gcc-4.4.x 32-bits toolchains Florian Fainelli
2010-07-28 22:15 ` David Daney
2010-08-02 14:59 ` Ralf Baechle [this message]
2010-08-02 16:51 ` David Daney
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=20100802145904.GA6123@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney@caviumnetworks.com \
--cc=florian@openwrt.org \
--cc=linux-mips@linux-mips.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