Re: [pcre-dev] Code testing tarball

Hi Petr,

thank you for the testing. Actually the PPC error was done by me, and I also noticed a few days ago (I changed a value to pcre_uint32 from long int, which is 64 bit long). There was an other error in JIT revealed on ARM (signed / unsigned load half issue), and you likely see it on MIPS.

pcre_dfa_exec.c:3026:19: warning: variable 'lcc' set but not used [-Wunused-but-set-variable]>
pcre_jit_compile.c:3581:3: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]>
pcre_jit_compile.c:4482:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]>
pcre_jit_compile.c:4532:7: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]>
pcre_jit_compile.c:6624:1: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]>
pcrecpp.cc:387:7: warning: variable 'lastend' set but not used [-Wunused-but-set-variable]>
pcretest.c:2161:14: warning: variable 'gn16ptr' set but not used [-Wunused-but-set-variable]>
pcretest.c:2160:14: warning: variable 'cn16ptr' set but not used [-Wunused-but-set-variable]>
pcregrep.c:1576:5: warning: variable 'pathlen' set but not used [-Wunused-but-set-variable]>
>
Other platforms (inluding intel architecures with JIT) show `unused variable'>
messages only.>
>
What can I do help you to solve this regression?

I will check these. To tell you truth I do really hate "dereferencing type-punned pointer" messages.

Other question: You said there are no UTF-16 variants of pcretest etc. Does it>
mean bundled test suite does not test UTF-16 library, it checks UTF-8 version>
only?>

No, it checks both. pcretest uses the 16 bit library if you pass -16 argument, and the testing environment is aware of that.

Regards,
Zoltan