public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@hack.frob.com>
To: Rich Felker <dalias@aerifal.cx>
Cc: Carlos O'Donell <carlos@redhat.com>,
	   GNU C Library <libc-alpha@sourceware.org>,
	   libc-ports@sourceware.org
Subject: Re: [RFC] Copy as much as you can during a 32-bit stat before returning EOVERFLOW?
Date: Tue, 26 Feb 2013 23:58:00 -0000	[thread overview]
Message-ID: <20130226235814.8B2A02C088@topped-with-meat.com> (raw)
In-Reply-To: Rich Felker's message of  Tuesday, 26 February 2013 18:48:49 -0500 <20130226234849.GH20323@brightrain.aerifal.cx>

> Stage 1: Change the default for _FILE_OFFSET_BITS to 64 on all
> targets, and make 32-bit off_t accessible only by explicitly
> requesting -D_FILE_OFFSET_BITS=32. This should help transition all the
> stragglers who are just straggling because they don't know better; the
> few who have fundamentally buggy code that's incompatible with 64-bit
> off_t can use the workaround (-D_FILE_OFFSET_BITS=32) until they get
> their acts together.

This makes library ABIs silently become incompatible with past builds.
That's a non-starter.

I'm somewhat sympathetic to the overall goal, but I'm not at all sure what
a viable migration path might be.

Regardless, don't hijack this thread for that subject.
Start your own thread.


Thanks,
Roland

      reply	other threads:[~2013-02-26 23:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26 19:55 Carlos O'Donell
2013-02-26 20:37 ` Paul Eggert
2013-02-26 22:59   ` Joseph S. Myers
2013-02-26 21:00 ` Roland McGrath
2013-02-26 23:05   ` Joseph S. Myers
2013-02-27 19:26   ` Carlos O'Donell
2013-02-26 23:49 ` Rich Felker
2013-02-26 23:58   ` Roland McGrath [this message]

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=20130226235814.8B2A02C088@topped-with-meat.com \
    --to=roland@hack.frob.com \
    --cc=carlos@redhat.com \
    --cc=dalias@aerifal.cx \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-ports@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).