From: "Stephane Marchesin" <marchesin@icps.u-strasbg.fr>
To: linuxppc-dev@ozlabs.org, "David Woodhouse" <dwmw2@infradead.org>,
benh@kernel.crashing.org, paulus@samba.org,
henrik.sorensen@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: V4L2: __ucmpdi2 undefined on ppc
Date: Sun, 2 Mar 2008 19:48:45 +0100 [thread overview]
Message-ID: <6a89f9d50803021048v7a330bd6m82d553d80042c5aa@mail.gmail.com> (raw)
In-Reply-To: <6a89f9d50802060639j4b3a8b7u4e4e596b010ee353@mail.gmail.com>
On 2/6/08, Stephane Marchesin <marchesin@icps.u-strasbg.fr> wrote:
>
> We're hitting this i nouveau as well (http://nouveau.freedesktop.org),
> since we make extensive use ot 64 bit ints. Over time, we've had a
> number of reports on this issue, and at one point I read that it
> should be fixed in gcc. But recently, a nouveau user on PPC32 (Henrik
> in CC:) reported the issue again with gcc 4.2.3. Others have it on gcc
> 4.2.2 too:
> http://bugs.freedesktop.org/show_bug.cgi?id=10547
>
> So, the point of this email is to ask about the possibility of merging
> in one of the __ucmpdi2 patches, like David's which is kept below for
> reference. Most distros seem to ship with such a patch already, and it
> seems that other drivers hit this as well.
>
So, could we have that thing in main tree ? It's not like it's
untested, most distros carry that, and a couple of arches provide
their own ucmpdi2 implementation already. It's also such a small
function...
Stephane
next prev parent reply other threads:[~2008-03-02 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SOC.4.61.0612131359430.10721@math.ut.ee>
[not found] ` <1166053317.909.19.camel@praia>
[not found] ` <20061214195842.GA14041@athena.road.mcmartin.ca>
2006-12-17 13:29 ` V4L2: __ucmpdi2 undefined on ppc David Woodhouse
2008-02-06 14:39 ` Stephane Marchesin
2008-03-02 18:48 ` Stephane Marchesin [this message]
2008-03-02 21:53 ` Segher Boessenkool
2008-03-04 16:37 ` David Woodhouse
2008-03-04 16:58 ` Scott Wood
2008-03-04 20:32 ` Segher Boessenkool
2008-03-04 21:44 ` Paul Mackerras
2008-03-04 21:47 ` Scott Wood
2008-03-04 22:43 ` Segher Boessenkool
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=6a89f9d50803021048v7a330bd6m82d553d80042c5aa@mail.gmail.com \
--to=marchesin@icps.u-strasbg.fr \
--cc=benh@kernel.crashing.org \
--cc=dwmw2@infradead.org \
--cc=henrik.sorensen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).