On 01/15/2018 04:46 PM, Jakub Jelinek wrote:
Hi!
As the testcase shows, calls to member_vec_dedup and qsort are just guarded
by the vector being non-NULL, which doesn't mean it must be non-empty,
so we can't do (*member_vec)[0] on it. Fixed by the second hunk, the
rest is just a small cleanup to use the vec.h methods.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
Ok I'm a little surprised we get this case, but I think we've both found
other strange boundary cases here. thanks.
nathan
--
Nathan Sidwell
