| To: | Kanoj Sarcar <kanoj@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: compiler problem |
| From: | Ralf Baechle <ralf@xxxxxxxxxxx> |
| Date: | Wed, 1 Mar 2000 00:46:06 +0100 |
| Cc: | linux-origin@xxxxxxxxxxx |
| In-reply-to: | <200002292346.PAA80931@xxxxxxxxxxxxxxxxxxx> |
| References: | <20000229235414.E1585@xxxxxxxxxxxxxx> <200002292346.PAA80931@xxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-origin@xxxxxxxxxxx |
On Tue, Feb 29, 2000 at 03:46:41PM -0800, Kanoj Sarcar wrote: > > Is this part of the binary compatibility execve(2) syscall? I wasted a lot > > of time because our MIPS compiler did die on my execve(2) compat syscall. > > Yes, this is so that 32 bit execs go to sys32_execve, instead of > sys_execve. The reason being that the argv[]/envp[] has to be > copied specially, since these entries are only 32bit large for > mips32. Ok, so it's what I already did observe in my kernel. I've got a workaround which seems to be stable but no fix for the compiler. Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: compiler problem, Kanoj Sarcar |
|---|---|
| Previous by Thread: | Re: compiler problem, Kanoj Sarcar |
| Indexes: | [Date] [Thread] [Top] [All Lists] |