Re^4: Calling HePV - "warning: dereferencing type-punned pointer will break strict-aliasing rules"

/usr/bin/perl /usr/share/perl5/vendor_perl/ExtUtils/xsubpp  -typemap /
+usr/share/perl5/ExtUtils/typemap -typemap typemap  Utils.xs > Utils.x
+sc && mv Utils.xsc Utils.c
Please specify prototyping behavior for Utils.xs (see perlxs manual)
gcc -c  -I/DBA/lua/5.2.1/include -Wall -Wno-strict-aliasing -O2 -g -pi
+pe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-stron
+g --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic
+   -DVERSION=\"1.0\" -DXS_VERSION=\"1.0\" -fPIC "-I/usr/lib64/perl5/C
+ORE"   Utils.c
Utils.xs: In function ‘perl_to_lua’:
Utils.xs:263:13: warning: dereferencing type-punned pointer will break
+ strict-aliasing rules [-Wstrict-aliasing]
             char *key = HePV (he, key_len);
             ^
Utils.xs:263:13: warning: dereferencing type-punned pointer will break
+ strict-aliasing rules [-Wstrict-aliasing]
Utils.xs:263:13: warning: dereferencing type-punned pointer will break
+ strict-aliasing rules [-Wstrict-aliasing]
Utils.xs:263:13: warning: dereferencing type-punned pointer will break
+ strict-aliasing rules [-Wstrict-aliasing]
Running Mkbootstrap for N2::Lua::Utils ()
[download]

It's 1000 lines of XS code. I'd have to trim it down a bit.

But in any case I think the answer is environmental, not in the code, as it compiles without warnings under Ubuntu 18.04, but WITH warnings under Oracle Linux Server 7.3.

Here's the full build output. And I see that -Wno-strict-aliasing is actually present in the GCC options! So why on earth are we still getting that warning?

Comment on Re^4: Calling HePV - "warning: dereferencing type-punned pointer will break strict-aliasing rules" Download Code

Replies are listed 'Best First'.
Re^5: Calling HePV - "warning: dereferencing type-punned pointer will break strict-aliasing rules" by syphilis (Archbishop) on Jul 27, 2018 at 00:12 UTC
And I see that -Wno-strict-aliasing is actually present in the GCC options! So why on earth are we still getting that warning? The "-Wall" enables the strict-aliasing warning. I think the "-Wno-strict-aliasing" would then disable that warning, but then there's a second "-Wall" switch which probably enables it again. You can edit the WriteMakefile() section of the module's Makefile.PL such that the flags are modified to give the behaviour you're after. (See the ExtUtils::MakeMaker documentation). I'm reluctant to be more specific because I'm not sure which flags are which. Output of `perl -V` should identify that for you. If both occurrences of "-Wall" are part of the same flagset, then I would remove the second occurrence. But if the second "-Wall" is in a different flagset (which is probably the case), then I would insert "-Wno-strict-aliasing" immediately after it. Cheers, Rob	[reply] [d/l]

Replies are listed 'Best First'.

Re^5: Calling HePV - "warning: dereferencing type-punned pointer will break strict-aliasing rules"
by syphilis (Archbishop) on Jul 27, 2018 at 00:12 UTC

And I see that -Wno-strict-aliasing is actually present in the GCC options! So why on earth are we still getting that warning?

perl -V

[reply]
[d/l]