From: Stelian Pop <stelian@popies.net>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>,
v4l-dvb-maintainer@linuxtv.org, mchehab@infradead.org
Subject: Re: [v4l-dvb-maintainer] [PATCH] Fix __ucmpdi2 in v4l2_norm_to_name()
Date: Thu, 04 Jan 2007 13:53:14 +0100 [thread overview]
Message-ID: <1167915194.20853.18.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0701040357250.19252@shell4.speakeasy.net>
Le jeudi 04 janvier 2007 à 04:09 -0800, Trent Piepho a écrit :
> On Thu, 4 Jan 2007, Stelian Pop wrote:
> > This patch replaces a switch statement using 64 bit values with the
> > if/else equivalent in order to prevent a call __ucmpdi2 generated by
> > some versions of gcc (verified with gcc-4.1.2 20060928):
> >
> > drivers/built-in.o: In function `v4l2_norm_to_name':
> > (.text+0x71100): undefined reference to `__ucmpdi2'
> >
> > Signed-off-by: Stelian Pop <stelian@popies.net>
>
> It looks like there is a much better way to handle this problem here:
> http://lkml.org/lkml/2006/12/17/46
>
> Basically:
> A. Fix gcc so it doesn't call in __ucmpdi2 (already fixed?)
> B. Link in __ucmpdi2 from libgcc
> C. Write arch specific code to provide __ucmpdi2
Indeed, I didn't see that thread.
Linus, just make sure you apply a fix for this problem before 2.4.20
goes final...
Thanks and sorry for the noise.
Stelian.
--
Stelian Pop <stelian@popies.net>
next prev parent reply other threads:[~2007-01-04 12:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 11:10 [PATCH] Fix __ucmpdi2 in v4l2_norm_to_name() Stelian Pop
2007-01-04 12:09 ` [v4l-dvb-maintainer] " Trent Piepho
2007-01-04 12:53 ` Stelian Pop [this message]
2007-01-04 22:48 ` Andrew Morton
2007-01-04 22:59 ` Mauro Carvalho Chehab
2007-01-04 23:18 ` Andrew Morton
2007-01-07 11:44 ` Mauro Carvalho Chehab
2007-01-15 9:22 ` Stelian Pop
2007-01-04 23:19 ` Stelian Pop
2007-01-05 14:20 ` 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=1167915194.20853.18.camel@localhost.localdomain \
--to=stelian@popies.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=torvalds@osdl.org \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=xyzzy@speakeasy.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