On (11/11/15 12:44), David Rientjes wrote:
[..]
> This can't possibly be correct, the warnings are legitimate and the result
> of the sigsetjmp() in the function. You may be interested in
> returns_twice rather than marking random automatic variables as volatile.
Hm, ok. I saw no probs with `int first' and `end' being volatile
static void walk_file(const char *name, const struct stat *st)
{
int first = 1;
for (...) {
if (sigsetjmp(sigbus_jmp, 1)) {
goto got_sigbus;
}
got_sigbus:
...
if (first && opt_list) {
first = 0;
print_foo();
}
}
}
the `end' is also looked fine.
ANSI C
§7.13.2.1
3 All accessible objects have values, and all other components of the abstract machine 249)
have state, as of the time the longjmp function was called, except that the values of
objects of automatic storage duration that are local to the function containing the
invocation of the corresponding setjmp macro that do not have volatile-qualified type
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
and have been changed between the setjmp invocation and longjmp call are indeterminate.
Thus, adding 'volatile' should do the trick. Isn't it?
I need to google more - is returns_twice actually prevents gcc from
`over-optimizing' (there are some bug reports that state that setjmp can
be screwed up by gcc) or it's actually because the programs that do setjmp
basically violate ANSI C standard and don't volatile-qualify the affected
variables. Any hint would be helpful.
-ss
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>