Re: [PATCH] newlib: undefine _FORTIFY_SOURCE
Mike Frysinger <[email protected]>
| Newsgroups | gmane.comp.lib.newlib |
|---|---|
| Message-ID | <YYspZHTVtEA6e0qh@vapier> |
On 08 Nov 2021 19:15, Keith Packard wrote: > Mike Frysinger <[email protected]> writes: > > Since newlib isn't prepared to build itself with _FORTIFY_SOURCE, and > > it's not clear if it's even useful, disable it when building the code. > > It is useful; I've caught a few library bugs when I turned this on for > picolibc. Fixing newlib to handle -D_FORTIFY_SOURCE could probably start > with the patches I did in picolibc, which mostly just #undef the various > mem and str functions before defining them. i'm not against making it work, but it doesn't now, so we should disable the logic if/until it's made to actually work. -mike
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEuQK1JxMl+JKsJRrUQWM7n+g39YEFAmGLKWQACgkQQWM7n+g3 9YEyiA/9Ee/DWWxH9Iz4RUHtuzzIuYP6V8ITJsNlIwTgH3+eJTQCIfgcTGQIToat wg3QttUIO8SyEFYav0rKEO4fp4I9DL6c4U6rpLOFMPin4r7/VoatPjX+FjFhomBQ 7sZ+HIxcu5exy1KgECkB6TFSMe45nuUibRjIVqYLVHVb8RHLn+Y5H7O9IMAKKlB9 CR/bcAH0OasO9Xu2fa8O/VClDH9JvARdPuQRA/CNXCIwOLWwPGi0uYPnfgLmm2Yd 6f3jU2vvph5yLSGnWN31nay2hOLYaiAttTsvrMuMsFyg0QI/MbW/+h5zozrXruWD MR71e0YywVBrM8kWX4UwT0Zad/sL8ieYSKqFLS8at3H/lapklhQ/CYqcEhcLPjBf R7TrwROVo14UwViL/RCMG3QbCEEYUquGp70kgJYh6XrekIt+LAHlHNsQynCqYRXD CdpBbHvMfCgnBJlfh0sFoXlMOP3G1LOaFR/+8Xqhd4weT2MyrLL3hcmrXMH8cjm9 7ALXO7kYwRy+AaHJkT1LH+pG/SBa7pqKN7WmsEp5UAFlWnDy/f0dcQC4QlPRgQpG mvpTJvwX02sA5eFwkUZmUsiPYfHys8iLMf9Ymikc6cIpKgvcBf2FJJ08HxTB8fHa XCvOuublDlY47c+xJuDwfIJLCfjBW+uPtncwfmnRkVN8N84mP9Q= =d2CU -----END PGP SIGNATURE-----