public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "soltys at ziu dot info" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/13575] SSIZE_MAX defined as LONG_MAX is inconsistent with SIZE_MAX, when __WORDSIZE != 64
Date: Tue, 10 Jan 2012 01:29:00 -0000	[thread overview]
Message-ID: <bug-13575-131-9Nwa2LbrtS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13575-131@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Michal Soltys <soltys at ziu dot info> 2012-01-10 01:29:02 UTC ---
@Joseph

Thanks for clarification about size_t/ssize_t sizes.

@Ulrich

But for ssize_t type, the definition comes from glibc headers, not gcc. Apart
from what Joseph clarified - what I meant in context of SSIZE_MAX was analogous
(even if regarding the very opposite thing now) as in:

http://sourceware.org/ml/libc-hacker/2002-08/msg00031.html

that solution seemed more proper with reference to how ssize_t
is defined in glibc headers, which for __WORDSIZE == 32 always comes down to
(int), unless overriden locally. If SSIZE_MAX constant is to accurately reflect
ssize_t type, then that would be more correct than just defaulting to LONG_MAX
unconditionally ?

Thanks for the reply, even if a rough one.

As the bug report somewhat mismatches the actual issue, would it be ok to open
proper one, with patch based on the old mailing post above ? If not, then just
ignore the reply and forget it.

-- 
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.


  parent reply	other threads:[~2012-01-10  1:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09 11:19 [Bug libc/13575] New: " soltys at ziu dot info
2012-01-09 11:57 ` [Bug libc/13575] " joseph at codesourcery dot com
2012-01-09 18:45 ` drepper.fsp at gmail dot com
2012-01-10  1:29 ` soltys at ziu dot info [this message]
2014-06-27 11:14 ` 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-13575-131-9Nwa2LbrtS@http.sourceware.org/bugzilla/ \
    --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).