grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: [ARM, IA64] Division on arm and ia64
Date: Fri, 08 Nov 2013 17:48:52 +0100	[thread overview]
Message-ID: <527D15F4.4010200@gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 617 bytes --]

Hello, all. ARM and ia64 apparently don't generically have opcode to
make division of pointer-sized integers. Alpha has the same property but
alpha port is in very sorry state anyway so it doesn't matter anyway.
Looking at libgcc code at functions at question, I see that they use
algorithm very similar to what we have in divmod64. IA64 version uses
FPU which probably worked more by luck since we don't do proper FPU
setup on any platform. Alpha version also uses FPU and probably doesn't
work. In my alpha port I redirected all division functions to
grub_divmod64. What do you think about attached patch?

[-- Attachment #1.2: div.diff --]
[-- Type: application/x-patch, Size: 5426 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]

                 reply	other threads:[~2013-11-08 16:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=527D15F4.4010200@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.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).