public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mfundarek at nds dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/4495] New: _POSIX_V6_ILP32_OFFBIG shouldn't be defined for __WORDSIZE == 32
Date: Fri, 11 May 2007 13:55:00 -0000	[thread overview]
Message-ID: <20070511145519.4495.mfundarek@nds.com> (raw)

in bits/environments.h: 

#if __WORDSIZE == 32
# define _POSIX_V6_ILP32_OFFBIG	1
# define _XBS5_ILP32_OFFBIG	1
#endif

then comment:

/* We optionally provide an environment with the above size but an 64-bit
   side `off_t'.  Therefore we don't define _XBS5_ILP32_OFFBIG.  */

The Open Group Base Specifications Issue 6 IEEE Std 1003.1, 2004 Edition:
_POSIX_V6_ILP32_OFFBIG
    The implementation provides a C-language compilation environment with 32-bit
int, long, and pointer types and an off_t type using at least 64 bits.

also from stdint.h chapter in POSIX specification:
If an implementation provides integer types with width 64 that meet these
requirements, then the following types are required: int64_t uint64_t

In particular, this will be the case if any of the following are true:
      The implementation supports the _POSIX_V6_ILP32_OFFBIG programming
environment and the application is being built in the _POSIX_V6_ILP32_OFFBIG
programming environment (see the Shell and Utilities volume of IEEE Std
1003.1-2001, c99, Programming Environments).
...

My understanding:
If _POSIX_V6_ILP32_OFFBIG is defined then 64bit types are available, off_t will
be at least 64bits long. Same probably applies to _XBS5_ILP32_OFFBIG. All this
seems to be confirmed by the _XBS5_ILP32_OFFBIG comment quoted.

Suggestion:
Either undef both of these macros or
#if __WORDSIZE == 32
# define _POSIX_V6_ILP32_OFFBIG	-1
# define _XBS5_ILP32_OFFBIG	-1
#endif

-- 
           Summary: _POSIX_V6_ILP32_OFFBIG shouldn't be defined for
                    __WORDSIZE == 32
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: mfundarek at nds dot com
                CC: glibc-bugs at sources dot redhat dot com


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2007-05-11 13:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-11 13:55 mfundarek at nds dot com [this message]
2007-05-23 10:23 ` [Bug libc/4495] " jakub 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=20070511145519.4495.mfundarek@nds.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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).