Re: [PATCH 07/15] parisc: use generic sys_fanotify_mark implementation
John David Anglin <[email protected]>
| Newsgroups | gmane.comp.lib.glibc.alpha,gmane.linux.kernel.cross-arch,gmane.linux.kernel,gmane.linux.ports.sparc,gmane.linux.ports.sh.devel,gmane.linux.lib.musl.general,gmane.linux.ltp,gmane.linux.ports.parisc,gmane.linux.ports.mips,gmane.linux.ports.hexagon,gmane.linux.file-systems,gmane.linux.ports.ppc64.devel |
|---|---|
| Message-ID | <[email protected]> |
On 2024-06-21 4:54 a.m., John Paul Adrian Glaubitz wrote: > Hi, > > On Fri, 2024-06-21 at 08:28 +0200, Arnd Bergmann wrote: >> It's more likely to be related to the upward growing stack. >> I checked the gcc sources and found that out of the 50 supported >> architectures, ARGS_GROW_DOWNWARD is set on everything except >> for gcn, stormy16 and 32-bit parisc. The other two are >> little-endian though. STACK_GROWS_DOWNWARD in turn is set on >> everything other than parisc (both 32-bit and 64-bit). > Wait a second! Does that mean that on 64-bit PA-RISC, the stack is > actually growing downwards? If yes, that would be a strong argument > for creating a 64-bit PA-RISC port in Debian and replacing the 32-bit > port. No, the stack grows upward on both 32 and 64-bit parisc. But stack arguments grow upwards on 64-bit parisc. The argument pointer is needed to access these arguments. In 32-bit parisc, the argument pointer is at a fixed offset relative to the stack pointer and it can be eliminated. Dave -- John David Anglin [email protected]