-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
compile options #520
Comments
No. Is there a project where it is a requirement? |
No requirement at all inside my code. echo " CC " src/libpcre2_8_la-pcre2_compile.lo;/bin/bash ./libtool --silent --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I./src "-I./src" -DPCRE2_CODE_UNIT_WIDTH=8 -fvisibility=hidden -mshstk -O2 -MT src/libpcre2_8_la-pcre2_compile.lo -MD -MP -MF src/.deps/libpcre2_8_la-pcre2_compile.Tpo -c -o src/libpcre2_8_la-pcre2_compile.lo The presence of -mshstk caught my eye and was wondering if it is a required flag. I am thinking of pulling the pcre2 source directly into my binary (no library) and thus need to provide the appropriate compile flags and we currently do not have -mshstk as a compile option and I'd like to keep it that way. |
That's odd. A simple ./configure on 10.44 gives just this:
|
There's this in the changelog:
I guess the user is using Intel CET? |
Shadow stack can be used as a security feature, and even jit supports it. Although I never tested it, the code was a contribution from Intel. However, it is not a mandatory feature for PCRE2, and there is no reason to be that way, ever. |
Is it a requirement to compile pcre2 source code with -mshstk (shadow stack)?
The text was updated successfully, but these errors were encountered: