Re: octave w/ fsanitize=undefined

[John W. Eaton]

On 04/13/2017 08:03 PM, Dmitri A. Sergatskov wrote:
> I compiled a recent tip with fsanitize=undefined
> Running make check results in few errors:
>
> libinterp/corefcn/graphics.cc-tst
> ...................libinterp/corefcn/graphics.h:5174:41: runtime error:
> load of value 53, which is not a valid value for type 'bool'
>  PASS     41/41
>
> libinterp/corefcn/typecast.cc-tst
> ...................../libinterp/corefcn/typecast.cc:80:15: runtime
> error: null pointer passed as argument 2, which is declared to never be null
>  PASS     59/59
>
> libinterp/dldfcn/symbfact.cc-tst
> ....................../liboctave/array/Sparse.h:526:57: runtime error:
> load of value 80, which is not a valid value for type 'bool'
>  PASS      4/4
>
> general/isequal.m
> ...................................../liboctave/array/idx-vector.cc:623:19:
> runtime error: null pointer passed as argument 2, which is declared to
> never be null
>  PASS     60/60
>
> io.tst
> ......................................................../libinterp/corefcn/ls-mat5.cc:2418:12:
> runtime error: null pointer passed as argument 1, which is declared to
> never be null
> ../libinterp/corefcn/ls-mat5.cc:2419:13: runtime error: null pointer
> passed as argument 1, which is declared to never be null
>  PASS    142/142
>
> Not sure how serious are those -- but hopefully this info of some interest.

Maybe that last one explains the io.tst failure when using LTO?

I'll try to check them out, but help is also welcome, especially in 
determining exactly which tests show the errors.

Maybe we should add a buildbot configuration for this option to help us 
avoid creating these kinds of problems in the future.

jwe