public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: pb@nexus.co.uk
To: gcc-gnats@gcc.gnu.org
Subject: target/5700: [ARM, 2.95] __umodsi3 yields wrong answer
Date: Fri, 15 Feb 2002 06:16:00 -0000 [thread overview]
Message-ID: <20020215141527.5979.qmail@sources.redhat.com> (raw)
>Number: 5700
>Category: target
>Synopsis: [ARM, 2.95] __umodsi3 yields wrong answer
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Feb 15 06:16:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: pb@nexus.co.uk
>Release: 2.95 branch
>Organization:
>Environment:
>Description:
This code prints "40000000", which is clearly incorrect.
main()
{
unsigned long __umodsi3(unsigned long, unsigned long);
unsigned long a = __umodsi3(0xC0000000, 2);
printf("%x\n", a);
}
>How-To-Repeat:
>Fix:
Probably this change:
2000-08-22 Nick Clifton <nickc@redhat.com>
* config/arm/lib1funcs.asm (__umodsi3): Before performing any
restorative additions, test for bottom bits of IP being set,
rather than relying upon the RORs not matching.
(__modsi3): Ditto.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-02-15 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-15 6:16 pb [this message]
2002-04-23 8:11 rearnsha
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=20020215141527.5979.qmail@sources.redhat.com \
--to=pb@nexus.co.uk \
--cc=gcc-gnats@gcc.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 read-only IMAP folder(s) and NNTP newsgroup(s).