search for: no_return

On 10 October 2014 21:31, Jonathan Roelofs <jonathan at codesourcery.com> wrote: > Sounds like an arm-thumb interworking veneer, generated by the linker... the > real function should be called 'asan_handle_no_return' (with some number of '_' > prefixing it. I don't remember how many get added). It is a veneer which has just a jump and a word after it, which points to a place in memory that had which I believe was the implementation of the asan check. I was wondering if the no_return on tha...

On 10 October 2014 15:30, Evgeniy Stepanov <eugenis at google.com> wrote: > Could this be some kind of linker-generated compatibility magic? I'm not sure. Searching for "____asan_handle_no_return_veneer" on Google gets me this thread. :) I'm tempted to disable that test on ARM+Linux, since we use EHABI instead of SjLj... At least for now... --renato

...fix shadow char_size fix more shadow warning no need to check argument for _XkbFree() remove stray extern no need to check args for Xfree() fix memleak in error path fix memleak in error path no need to check XFree arguments mark _XDefaultIOError as no_return Fixes: warning: variable 'req' set but not,used wharms (3): add _X_UNUSED to avoid unused variable warnings remove empty line silence gcc warning assignment discards 'const' qualifier from pointer target type git tag: libX11-1.6.6 https://xorg.freedesktop....