public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Szabolcs Nagy <Szabolcs.Nagy@arm.com>,
	 "libc-alpha\@sourceware.org" <libc-alpha@sourceware.org>,
	 nd <nd@arm.com>,  Siddhesh Poyarekar <siddhesh@gotplt.org>
Subject: Re: [PATCH] Deprecate 32-bit off_t support
Date: Tue, 08 Jan 2019 08:08:00 -0000	[thread overview]
Message-ID: <87h8ejd11y.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1901072216480.17868@digraph.polyomino.org.uk> (Joseph Myers's message of "Mon, 7 Jan 2019 22:17:41 +0000")

* Joseph Myers:

> On Mon, 7 Jan 2019, Florian Weimer wrote:
>
>> * Szabolcs Nagy:
>> 
>> > please do not recommend the use of a non-standard type
>> > in place of a standard one (off64_t is not even available
>> > with default feature test macros in posix headers).
>> 
>> What do you propose instead?  Mention int64_t and uint64_t only?
>
> Programs and libraries should use types such as off_t, and arrange to be 
> built with _FILE_OFFSET_BITS=64, which would make them unaffected by a 
> future change to the default.

If this concerns a public header file, is there a preprocessor check we
can recommend to add to the header file?  Something that causes an
#error if the ABI would not be correct?

Thanks,
Florian

  parent reply	other threads:[~2019-01-08  8:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 12:40 Florian Weimer
2019-01-04 12:46 ` Siddhesh Poyarekar
2019-01-04 12:50   ` Siddhesh Poyarekar
2019-01-04 12:58     ` Florian Weimer
2019-01-04 16:14       ` Siddhesh Poyarekar
2019-01-04 16:39   ` Joseph Myers
2019-01-04 13:16 ` Szabolcs Nagy
2019-01-04 13:46   ` Szabolcs Nagy
2019-01-07 18:26   ` Florian Weimer
2019-01-07 22:17     ` Joseph Myers
2019-01-08  0:06       ` Paul Eggert
2019-01-08  8:08       ` Florian Weimer [this message]
2019-01-17 21:29 ` Guillem Jover
2019-01-18 10:09   ` Florian Weimer
2019-01-18 14:12     ` Adhemerval Zanella

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=87h8ejd11y.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=Szabolcs.Nagy@arm.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=nd@arm.com \
    --cc=siddhesh@gotplt.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).