|
From: Crestez D. L. <cdl...@gm...> - 2015-04-20 12:34:02
|
On 04/03/2015 05:14 AM, Petar Jovanovic wrote: > Hi Florian, > > Sorry for not responding to this earlier. > Field _valEx is used on MIPS only for pipe system call when kernel can return an array of two file descriptors. Otherwise, this field is undefined (actually, it has a value that happened to be in v1 register, which can be an arbitrary value and it is not deterministic). Thus, comparing _valEx does not make sense for an arbitrary SysRes. > > Your yesterday's change r15060 breaks MIPS port in general, as comparing _valEx will fail immediately. MIPS support has been broken in trunk for two weeks. Does anyone have a fix for this incoming? Maybe it should be posted as a bug in the tracker. It's not clear how valEx should be treated for syscalls other than pipe() since it's left undefined by the linux syscall ABI. I think that simply defining that all other syscalls return zero in valEx would be an acceptable solution. Regards, Leonard |