From: "Roger Pau Monné" <roger.pau@citrix.com>
To: George Dunlap <george.dunlap@eu.citrix.com>,
xen-devel@lists.xenproject.org
Cc: Wei Liu <wei.liu2@citrix.com>, Olaf Hering <olaf@aepfle.de>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH 1/2] xen{trace/analyze}: don't use 64bit versions of libc functions
Date: Mon, 22 Jun 2015 11:59:55 +0200 [thread overview]
Message-ID: <5587DC9B.3050403@citrix.com> (raw)
In-Reply-To: <5587D094.9030304@eu.citrix.com>
El 22/06/15 a les 11.08, George Dunlap ha escrit:
> On 06/19/2015 09:58 AM, Roger Pau Monne wrote:
>> This is not needed, neither encouraged. Configure already checks
>> _FILE_OFFSET_BITS and appends it when needed, so that the right functions
>> are used. Also remove the usage of loff_t and O_LARGEFILE for the same
>> reason.
>
> Just so I understand -- are you saying that configure at the tools
> directory level will notice that Linux can handle 64-bit file operations
> and use them automatically?
Yes, according to the man page [1]:
"Over time, increases in the size of the stat structure have led to
three successive versions of stat(): sys_stat() (slot __NR_oldstat),
sys_newstat() (slot __NR_stat), and sys_stat64() (new in kernel 2.4;
slot __NR_stat64). The glibc stat() wrapper function hides these details
from applications, invoking the most recent version of the system call
provided by the kernel, and repacking the returned information if
required for old binaries. Similar remarks apply for fstat() and lstat()."
Roger.
[1] http://linux.die.net/man/2/fstat64
next prev parent reply other threads:[~2015-06-22 10:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 8:58 [PATCH 0/2] xen{trace/analyze}: fix build on FreeBSD Roger Pau Monne
2015-06-19 8:58 ` [PATCH 1/2] xen{trace/analyze}: don't use 64bit versions of libc functions Roger Pau Monne
2015-06-19 13:07 ` Wei Liu
2015-06-22 9:08 ` George Dunlap
2015-06-22 9:59 ` Roger Pau Monné [this message]
2015-06-22 10:09 ` George Dunlap
2015-06-22 14:48 ` Roger Pau Monné
2015-06-24 11:11 ` Roger Pau Monné
2015-06-24 13:02 ` Roger Pau Monné
2015-06-24 13:08 ` George Dunlap
2015-06-19 8:58 ` [PATCH 2/2] configure: check for argp Roger Pau Monne
2015-06-19 13:10 ` Wei Liu
2015-06-22 10:12 ` George Dunlap
2015-06-22 10:45 ` Wei Liu
2015-06-22 10:55 ` George Dunlap
2015-06-22 11:10 ` Wei Liu
2015-06-22 11:13 ` George Dunlap
2015-06-25 12:01 ` [PATCH 0/2] xen{trace/analyze}: fix build on FreeBSD Ian Campbell
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=5587DC9B.3050403@citrix.com \
--to=roger.pau@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=olaf@aepfle.de \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.