On 11-Jun-2002, Fergus Henderson fjh@cs.mu.OZ.AU wrote:
On 11-Jun-2002, Manuel Carro boris@aaron.ls.fi.upm.es wrote:
It is possible that omiting the frame pointer (whose exact effecton the assembler output I really do not know) somehow affects the proper behavior of {long,set}jump. Note that this behavior is anyway not documented in the GCC manual --- maybe this kind of conduct is part of the lore in the C compiler arena.
Omitting the frame pointer should not have any effect on the behaviour of setjmp() and longjmp(). If it does, then that is a bug in GCC, which should be reported.
Sorry, I should have said "a bug in GCC and/or glibc".
Also note that the behaviour of longjmp() and setjmp() is documented in the C standard, and in the glibc manual -- that's why there's no need to document it in the GCC manual.