On 25.02.2016 17:42, Michael David Crawford wrote:
I'm working at silencing build warnings. I figure this is a good way
to become familiar with the code base.
GCC warned that a variable "might be clobbered by 'longjmp' or
'vfork'". That's the first time I've ever seen that. The problem has
to do with that registers are restored by the setjmp that occurs after
longjmp.
It worked to declare that variable virtual. Somehow I find that
unsatisfying. My objective in declaring it virtual was to get the
variable stored on the stack rather than in a register.
There are more warnings just like this in PNGTranslator.c. When I
declare the variables virtual, it leads to fatal errors because some
of these variables are passed to subroutines whose arguments are not
declared virtual.
I could declare the arguments virtual but again this strikes me as
unsatisfying. Is there something better I could do?