public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "richard at metafoo dot co.uk" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15366] New: Per C11 and C++11, <stdint.h> should not look at __STDC_LIMIT_MACROS or __STDC_CONSTANT_MACROS
Date: Sat, 13 Apr 2013 00:32:00 -0000	[thread overview]
Message-ID: <bug-15366-131@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=15366

             Bug #: 15366
           Summary: Per C11 and C++11, <stdint.h> should not look at
                    __STDC_LIMIT_MACROS or __STDC_CONSTANT_MACROS
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: unassigned@sourceware.org
        ReportedBy: richard@metafoo.co.uk
                CC: drepper.fsp@gmail.com
    Classification: Unclassified


glibc's <stdint.h> follows C99, which says that in C++, certain macros should
only be defined if __STDC_LIMIT_MACROS or __STDC_CONSTANT_MACROS is defined.
However, the C++ committee decided that they didn't want this behavior, and
explicitly overruled this in the C++11 standard (the first to provide
<stdint.h>). Consequently C11 removed these rules. glibc has not been updated
to follow the C11 rules, and still checks for those macros being defined in C++
mode.

C++ implementations are currently working around this by wrapping glibc's
<stdint.h> with one which defines these macros first. These workarounds should
not be necessary; glibc should simply not be checking for these macros. Fix
would be to remove these lines from sysdeps/generic/stdint.h:

/* The ISO C99 standard specifies that in C++ implementations these
   macros should only be defined if explicitly requested.  */
#if !defined __cplusplus || defined __STDC_LIMIT_MACROS

... plus the corresponding #endif and the corresponding lines for
__STDC_CONSTANT_MACROS.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2013-04-13  0:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13  0:32 richard at metafoo dot co.uk [this message]
2013-04-13  1:25 ` [Bug libc/15366] " ppluzhnikov at google dot com
2013-04-15 22:58 ` ppluzhnikov at google dot com
2013-04-15 23:32 ` ppluzhnikov at google dot com
2013-05-21 14:17 ` ondra at iuuk dot mff.cuni.cz
2014-06-13 18:26 ` fweimer at redhat dot com

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=bug-15366-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).