From: christophe barbe <christophe.barbe@lineo.fr>
To: Manoj Sontakke <manojs@sasken.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: which gcc version?
Date: Thu, 5 Apr 2001 13:50:21 +0200 [thread overview]
Message-ID: <20010405135021.A8969@pc8.inup.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0104050147290.23164-100000@weyl.math.psu.edu> <Pine.LNX.4.21.0104051930580.2687-100000@pcc65.sasi.com>
In-Reply-To: <Pine.LNX.4.21.0104051930580.2687-100000@pcc65.sasi.com>; from manojs@sasken.com on jeu, avr 05, 2001 at 16:09:14 +0200
Which kernel are you using ?
GFS use this kind of computation. And with kernel 2.2, a module divdi3.o provides all missing symbol like __divdi3.
Christophe
On jeu, 05 avr 2001 16:09:14 Manoj Sontakke wrote:
> hi
>
> On Thu, 5 Apr 2001, Alexander Viro wrote:
> > On Thu, 5 Apr 2001, Manoj Sontakke wrote:
> >
> > > Hi
> > > I am getting linker error "undefined reference to __divdi3".
> > > This is because c = a/b; where a,b,c are of type "long long"
> > > I understand this is gcc problem.
> > > I am doing this on a pentium with gcc -v = egcs-2.91.66
> >
> > Don't do it in the kernel. It has nothing to gcc version.
>
> Addition and subtraction works fine. The problem is with multiplication
> and division. I am doing this to avoid floating point calculation and
> doing fixed point calculation. The rage is large enough to need "long
> long" Any other way to achieve this?
>
> thanks
> manoj
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Christophe Barbé
Software Engineer
Lineo High Availability Group
42-46, rue Médéric
92110 Clichy - France
phone (33).1.41.40.02.12
fax (33).1.41.40.02.01
www.lineo.com
next prev parent reply other threads:[~2001-04-05 11:50 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-05 10:56 which gcc version? Manoj Sontakke
2001-04-05 5:48 ` Alexander Viro
2001-04-05 14:09 ` Manoj Sontakke
2001-04-05 11:37 ` Bart Trojanowski
2001-04-05 12:02 ` Matti Aarnio
2001-04-05 12:26 ` David Woodhouse
2001-04-05 12:31 ` Matti Aarnio
2001-04-05 13:09 ` Richard B. Johnson
2001-04-05 11:45 ` Matti Aarnio
2001-04-05 11:50 ` christophe barbe [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-23 12:53 Which " Roy Sigurd Karlsbakk
2001-11-23 12:57 ` Arjan van de Ven
2001-11-23 13:51 ` war
2001-11-23 19:43 ` J Sloan
2001-11-23 13:59 ` Anton Altaparmakov
2001-11-23 14:11 ` war
2001-11-23 15:14 ` Arjan van de Ven
2001-11-23 15:30 ` Gábor Lénárt
2001-11-23 15:34 ` Arjan van de Ven
2001-11-23 19:50 ` J Sloan
2001-11-23 20:34 ` John Jasen
2001-11-23 21:55 ` J Sloan
2001-11-24 3:08 ` John Jasen
2001-11-24 12:24 ` Paul G. Allen
2001-11-26 18:31 ` Alan Cox
2001-11-27 8:42 ` Ahmed Masud
2001-11-23 16:10 ` Anton Altaparmakov
2001-11-23 14:43 ` Anton Altaparmakov
2001-11-23 16:23 ` Jeff Garzik
2001-11-23 18:30 ` Daniel Phillips
2001-11-23 18:56 ` Anton Altaparmakov
2001-11-23 19:28 ` Daniel Phillips
2001-11-23 20:14 ` Andrew Morton
2001-11-23 20:24 ` Anton Altaparmakov
2001-11-23 20:35 ` Andrew Morton
2001-11-23 21:09 ` David Weinehall
2001-11-24 16:01 ` Luigi Genoni
2001-11-24 16:09 ` Daniel Phillips
2001-11-24 17:32 ` Luigi Genoni
2001-11-23 17:12 RaúlNúñez de Arenas Coronado
2001-11-23 18:02 ` M. Edward (Ed) Borasky
2001-11-23 18:14 ` Thorsten Glaser
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=20010405135021.A8969@pc8.inup.com \
--to=christophe.barbe@lineo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=manojs@sasken.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