On Mon, Feb 04, 2013 at 01:31:11AM +0000, Al Viro wrote: > Unless I'm misreading ocavr32.pdf, that should be (R12, R10:R11, R9, R8) and > (R12, R10:R11, R9:R8, stack) resp., so fadvise64 doesn't need a wrapper, but > fadvise64_64 does. And something like (s32, s32, s64, s64) would turn into > (R12, R11, R9:R8, stack, stack); AFAICS, we don't have anything that ugly...
Oh, yes, we do - fallocate(2). int fd, int mode, loff_t offset, loff_t len. On something like mips or sparc32 it packs nicely; on avr32 it doesn't. Could you confirm that I haven't misparsed the ABI? > Automating *that* is going to be interesting... I've not given up, but it's > not going to be fun ;-/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
