all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 23261@debbugs.gnu.org
Subject: bug#23261: 25.0.92; Undefined behavior in lib/stdint.h
Date: Mon, 11 Apr 2016 00:23:15 -0700	[thread overview]
Message-ID: <570B50E3.7080704@cs.ucla.edu> (raw)
In-Reply-To: <m2oa9h4lng.fsf@gmail.com>

> Could we maybe just remove stdint.h completely?  It should always be
> provided by the standard C library.

Unfortunately stdint.h is not portable in practice, as many C implementations 
don't conform to C11 or even to C99. It sounds like your platform has a problem 
in this area. Emacs provides a replacement stdint.h on platforms that don't 
conform to the standards.

I don't observe a problem with my clang installation (clang 3.7.0 on Fedora 23 
x86-64). I configured with './configure CC=clang', and on my platform the system 
stdint.h was fine so lib/stdint.h was not created. Perhaps you could look in 
your config.log near the strings "checking whether stdint.h ..." and see why 
your clang has problems with its stdint.h, and debug what went wrong. Another 
possibility is to futz with your CFLAGS to cajole clang into not issuing the 
bogus warning. Yet another possibility is to switch to GCC.





  parent reply	other threads:[~2016-04-11  7:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-10 13:51 bug#23261: 25.0.92; Undefined behavior in lib/stdint.h Philipp Stephani
2016-04-10 15:05 ` Eli Zaretskii
2016-04-11  7:23 ` Paul Eggert [this message]
2016-04-11 16:17   ` Paul Eggert
2016-04-17 13:48     ` Philipp Stephani
2016-04-18  4:30       ` Paul Eggert

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=570B50E3.7080704@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=23261@debbugs.gnu.org \
    --cc=p.stephani2@gmail.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.
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.