From: Jakub Jelinek <jakub@redhat.com>
To: libc-hacker@sourceware.cygnus.com
Subject: changes to stdlib/longlong.h
Date: Tue, 23 Nov 1999 02:59:00 -0000 [thread overview]
Message-ID: <19991123120104.I515@mff.cuni.cz> (raw)
Hi!
What was the reason to update longlong.h from egcs which seem to have a
subset of the glibc longlong stuff?
E.g. libc longlong used to do arithmetics on UDWtype while
egcs's version does only USItype -> UDItype, ie. there is no support for
e.g. 128bit + 128bit etc. on 64bit architectures.
At least soft-fp addon relies on those operations on 64bit platforms which
are now no longer defined as it expect them.
1999-11-22 Ulrich Drepper <drepper@cygnus.com>
* stdlib/longlong.h: Add count_trailing_zeros back.
* stdlib/longlong.h: Update from latest egcs version.
Cheers,
Jakub
___________________________________________________________________
Jakub Jelinek | jakub@redhat.com | http://sunsite.mff.cuni.cz/~jj
Linux version 2.3.18 on a sparc64 machine (1343.49 BogoMips)
___________________________________________________________________
next reply other threads:[~1999-11-23 2:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-23 2:59 Jakub Jelinek [this message]
1999-11-23 7:14 ` Ulrich Drepper
1999-11-23 9:20 ` Jakub Jelinek
1999-11-23 9:26 ` Ulrich Drepper
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=19991123120104.I515@mff.cuni.cz \
--to=jakub@redhat.com \
--cc=libc-hacker@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).