From: Florian Fainelli <florian@openwrt.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
wuzhangjin@gmail.com,
Richard Sandiford <rdsandiford@googlemail.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Handle removal of 'h' constraint in GCC 4.4
Date: Thu, 28 May 2009 18:00:03 +0200 [thread overview]
Message-ID: <200905281800.05772.florian@openwrt.org> (raw)
In-Reply-To: <4A1EB116.6080404@caviumnetworks.com>
Le Thursday 28 May 2009 17:43:18 David Daney, vous avez écrit :
> Wu Zhangjin wrote:
> > Hi,
> >
> > On Thu, 2009-05-28 at 13:31 +0200, Florian Fainelli wrote:
> >> Le Saturday 27 December 2008 16:19:40 Richard Sandiford, vous avez
écrit :
> >>> "Maciej W. Rozycki" <macro@linux-mips.org> writes:
> >>>> On Wed, 17 Dec 2008, David Daney wrote:
> >>>>> This is an incomplete proof of concept that I applied to be able to
> >>>>> build a 64 bit kernel with GCC-4.4. It doesn't handle the 32 bit
> >>>>> case or the R4000_WAR case.
> >>>>
> >>>> The R4000_WAR case can use the same C code -- GCC will adjust code
> >>>> generated as necessary according to the -mfix-r4000 flag. For the
> >>>> 32-bit case I think the conclusion was the only way to get it working
> >>>> is to use MFHI explicitly in the asm.
> >>>
> >>> No, the same sort of cast, multiply and shift should work for 32-bit
> >>> code too. I.e.:
> >>>
> >>> usecs = ((uint64_t)usecs * lpj) >> 32;
> >>>
> >>> It should work for both -mfix-r4000 and -mno-fix-r4000.
> >>
> >> Any updates on this ?
> >
> > I have updated it to this PATCH, could you help to review it?
>
> FWIW, Ralf also has a patch, that I have tested, that takes a slightly
> different approach.
Are you refering to this one: "MIPS: Rewrite <asm/div64.h> to work with gcc
4.4.0." ? If so, it does not solve the problem for 32-bits kernels.
>
> In any event, it would be nice if one of the patches were merged to
> 2.6.30 before it is released. GCC-4.4 has been available for quite a
> while now. Not being able to build the kernel with it will become a
> larger issue as time goes by.
Definitively.
--
Best regards, Florian Fainelli
Email : florian@openwrt.org
http://openwrt.org
-------------------------------
next prev parent reply other threads:[~2009-05-28 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 2:24 [PATCH] MIPS: Handle removal of 'h' constraint in GCC 4.4 David Daney
2008-12-19 0:46 ` Maciej W. Rozycki
2008-12-27 15:19 ` Richard Sandiford
2009-05-28 11:31 ` Florian Fainelli
2009-05-28 14:31 ` Wu Zhangjin
2009-05-28 15:43 ` David Daney
2009-05-28 16:00 ` Florian Fainelli [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-24 23:04 David Daney
2009-02-25 1:25 ` Maciej W. Rozycki
2009-02-26 16:58 ` Ralf Baechle
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=200905281800.05772.florian@openwrt.org \
--to=florian@openwrt.org \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=rdsandiford@googlemail.com \
--cc=wuzhangjin@gmail.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 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.