Lines Matching refs:compiled

29 be structured such that certain object files are compiled with CFI
112 visibility <LTOVisibility>`, must be compiled with ``-flto`` or ``-flto=thin``
159 visibility <LTOVisibility>`, must be compiled with ``-flto`` or ``-flto=thin``
175 visibility <LTOVisibility>`, must be compiled with ``-flto`` or ``-flto=thin``
205 function which was either compiled with ``-fsanitize=cfi-icall`` enabled,
206 or whose address was taken by a function in a translation unit compiled with
209 If a function in a translation unit compiled with ``-fsanitize=cfi-icall``
210 takes the address of a function not compiled with ``-fsanitize=cfi-icall``,
212 unit not compiled with ``-fsanitize=cfi-icall``. This is technically a
215 Each translation unit compiled with ``-fsanitize=cfi-icall`` must be
217 shared library boundaries are handled as if the callee was not compiled with
227 Translation units compiled with the ``-fsanitize-cfi-icall-generalize-pointers``
229 applied across all functions compiled with ``-fsanitize=cfi-icall``.
248 was not compiled with ``-fsanitize=cfi-icall`` to take a CFI-valid address
280 Furthermore, it is occasionally necessary for code not compiled with
344 visibility <LTOVisibility>`, must be compiled with ``-flto`` or ``-flto=thin``