On Mon, Nov 12, 2012 at 04:47:45PM +0000, Philip Hazel wrote:
> We are moving towards the next release: 8.32, which is rather an
> appropriate number, because it contains 32-bit support. The other major
> change is more Unicode compatibility for \X and for characters that have
> more than one "other case" (e.g. Greek Sigma). The RC is available here:
>
I tested 8.32-RC1 configured with --enable-pcretest-libreadline --enable-utf
--enable-unicode-properties --enable-pcre8 --enable-pcre16 --enable-pcre32
successfully with glibc Linux on following platforms:
ARMv6 --enable-jit
i686 --enable-jit
PPC --enable-jit
PPC64 --enable-jit
s390 --disable-jit
s390x --disable-jit
x86_64 --enable-jit
Compilation and all tests passed.
I will check MIPS later.
I noticed compilation on the PPC64 only (gcc-4.7.2) spits these warnings:
CC libpcre_la-pcre_ord2utf8.lo
pcre_jit_compile.c: In function 'compile_ref_matchingpath':
pcre_jit_compile.c:4796:3: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
pcre_jit_compile.c: In function 'compile_bracket_matchingpath':
pcre_jit_compile.c:5771:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
pcre_jit_compile.c:5821:7: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
pcre_jit_compile.c: In function '_pcre_jit_compile':
pcre_jit_compile.c:8136:1: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
CC libpcre16_la-pcre16_jit_compile.lo
In file included from pcre16_jit_compile.c:43:0:
pcre_jit_compile.c: In function 'compile_ref_matchingpath':
pcre_jit_compile.c:4796:3: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
pcre_jit_compile.c: In function 'compile_bracket_matchingpath':
pcre_jit_compile.c:5771:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
pcre_jit_compile.c:5821:7: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
pcre_jit_compile.c: In function '_pcre16_jit_compile':
pcre_jit_compile.c:8136:1: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
CC libpcre32_la-pcre32_jit_compile.lo
In file included from pcre32_jit_compile.c:43:0:
pcre_jit_compile.c: In function 'compile_ref_matchingpath':
pcre_jit_compile.c:4796:3: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
pcre_jit_compile.c: In function 'compile_bracket_matchingpath':
pcre_jit_compile.c:5771:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
pcre_jit_compile.c:5821:7: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
pcre_jit_compile.c: In function '_pcre32_jit_compile':
pcre_jit_compile.c:8136:1: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
Linking on the ARMv6 (gcc-4.5.4, binutils-2.22) warns about text relocation
which means some of source objects have been compiled without -fPIC:
CXXLD libpcrecpp.la
/usr/lib/gcc/armv6j-hardfloat-linux-gnueabi/4.5.4/../../../../armv6j-hardfloat-linux-gnueabi/bin/ld: warning: creating a DT_TEXTREL in a shared object.
But this looks like a bug in my toolchain because after running make V=1
I can see all three PCRE objects have been compiled with -fPIC.
-- Petr
