Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Lin <tesheng@andestech.com>
To: <paul.walmsley@sifive.com>, <palmer@sifive.com>,
	<linux-riscv@lists.infradead.org>
Cc: kclin@andestech.com, dslin1010@gmail.com, rick@andestech.com,
	alankao@andestech.com
Subject: Re: About __udivdi3
Date: Tue, 6 Aug 2019 09:37:24 +0800	[thread overview]
Message-ID: <20190806013723.GA5417@andestech.com> (raw)
In-Reply-To: <20190805055844.GE4292@andestech.com>

Cc: mailing list
On Mon, Aug 05, 2019 at 01:58:56PM +0800, Eric Lin wrote:
> Hi Palmer/Paul, 
> 
> Recently I encounter a problem that the output from __udivdi3 is wrong.
> The compiler will generate __udivdi3 library call when doing 64-bit
> over 64-bit division on 32-bit platform.
> 
> It seems __udivdi3 only supports 64-bit platform.
> Do you have any comments? Thanks.
> 
> Best Regards,
> Eric Lin  

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

       reply	other threads:[~2019-08-06  1:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190805055844.GE4292@andestech.com>
2019-08-06  1:37 ` Eric Lin [this message]
2019-08-06  2:13   ` About __udivdi3 Paul Walmsley
2019-08-06  2:59     ` Eric Lin
2019-08-06  3:01     ` Jim Wilson
2019-08-06  3:45       ` Nicolas Pitre
2019-08-06  8:31       ` Christoph Hellwig
2019-08-06 15:08         ` Palmer Dabbelt
2019-08-06 17:53           ` Paul Walmsley
2019-08-06 17:59             ` Palmer Dabbelt
2019-08-06 18:37           ` Nicolas Pitre

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=20190806013723.GA5417@andestech.com \
    --to=tesheng@andestech.com \
    --cc=alankao@andestech.com \
    --cc=dslin1010@gmail.com \
    --cc=kclin@andestech.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@sifive.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rick@andestech.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