From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Jim Meyering <jim@meyering.net>,
antoine.levitt@gmail.com
Subject: Re: md5 broken?
Date: Sat, 28 May 2011 09:09:58 -0700 [thread overview]
Message-ID: <4DE11E56.9040506@cs.ucla.edu> (raw)
In-Reply-To: <83fwnyc3v1.fsf@gnu.org>
On 05/28/11 07:10, Eli Zaretskii wrote:
> if it is decided to switch to "inline" everywhere, we
> should make sure it works with all the supported builds, not only with
> those that run `configure'.
Plain 'inline' has been in use for over a month,
and it builds on MS-DOS (according to the log for
bzr 104154), so it does appear that it works with
all supported builds.
The "extern inline" issue is that C99 has a different
semantics for "extern inline" than GCC traditionally did.
As long as we stay away from "extern inline" we shouldn't
have to worry about that porting problem. (This issue
applies equally to 'inline' and to 'INLINE'.)
By the way, thanks, Jim, for fixing the signed char bug
that I introduced. I really should have caught that.
next prev parent reply other threads:[~2011-05-28 16:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 9:32 md5 broken? Antoine Levitt
2011-05-28 12:23 ` Jim Meyering
2011-05-28 12:28 ` Antoine Levitt
2011-05-28 12:51 ` Eli Zaretskii
2011-05-28 13:32 ` Jim Meyering
2011-05-28 14:10 ` Eli Zaretskii
2011-05-28 16:09 ` Paul Eggert [this message]
2011-05-28 16:55 ` Eli Zaretskii
2011-05-28 19:12 ` Paul Eggert
2011-05-28 19:35 ` Eli Zaretskii
2011-05-28 22:47 ` INLINE -> inline (was: md5 broken?) Paul Eggert
2011-05-29 4:51 ` Eli Zaretskii
2011-05-29 8:05 ` INLINE -> inline Jim Meyering
2011-05-30 2:47 ` md5 broken? Ken Raeburn
2011-05-30 5:31 ` Paul Eggert
2011-05-31 4:22 ` Ken Raeburn
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=4DE11E56.9040506@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=antoine.levitt@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jim@meyering.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.