From: Ken Raeburn <raeburn@raeburn.org>
To: Paul Eggert <eggert@CS.UCLA.EDU>
Cc: Eli Zaretskii <eliz@gnu.org>,
antoine.levitt@gmail.com, Jim Meyering <jim@meyering.net>,
emacs-devel@gnu.org
Subject: Re: md5 broken?
Date: Sun, 29 May 2011 22:47:18 -0400 [thread overview]
Message-ID: <1C295C48-99BF-48A4-8B5C-9BE8353467BE@raeburn.org> (raw)
In-Reply-To: <4DE11E56.9040506@cs.ucla.edu>
On May 28, 2011, at 12:09, Paul Eggert wrote:
> 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'.)
My understanding is that the traditional GCC and C99 interpretations for "inline" and "extern inline" are basically reversed. So "inline" is just as much a problem as "extern inline" -- although we seem to have been getting away with "inline" for a while in intervals.c and elsewhere (unless we're defining it away on more platforms than I would hope necessary). Even so, I generally consider "static inline" to be the only safe form, unless you want to jump through hoops to figure out or force the interpretation of "inline" or "extern inline" with your particular compiler.
Ken
next prev parent reply other threads:[~2011-05-30 2:47 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
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 ` Ken Raeburn [this message]
2011-05-30 5:31 ` md5 broken? 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1C295C48-99BF-48A4-8B5C-9BE8353467BE@raeburn.org \
--to=raeburn@raeburn.org \
--cc=antoine.levitt@gmail.com \
--cc=eggert@CS.UCLA.EDU \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).