This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

problem with posix_fadvise() on ia64

From: David Mosberger <davidm at napali dot hpl dot hp dot com>
To: libc-hacker at sources dot redhat dot com
Date: Tue, 2 Mar 2004 18:44:57 -0800
Subject: problem with posix_fadvise() on ia64
Reply-to: davidm at hpl dot hp dot com

There appears to be a problem with fadvise() on ia64: glibc contains
both posix_fadvise.o and posix_fadvise64.o:

$ nm -g --defined posix_fadvise*.o

posix_fadvise.o:
0000000000000000 T posix_fadvise

posix_fadvise64.o:
0000000000000000 W posix_fadvise
0000000000000000 T posix_fadvise64

The first comes from sysdeps/unix/sysv/linux/posix_fadvise.c and is
wrong for ia64.  The latter is generated based on
sysdeps/unix/sysv/linux/ia64/syscalls.list and seems to be fine.

The problem with the first stub is that it splits the 64-bit offset
argument into two separate 32-bit arguments, which makes no sense on
ia64.

I'm not sure what the best way to fix this is.  Compiling with
-D_FILE_OFFSET_BITS=64 works around the problem, but clearly that
shouldn't be necessary.

Thanks,

	--david

Follow-Ups:
- [PATCH] Fix posix_fadvise() on 64-bit architectures
  - From: Jakub Jelinek

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]