On 08/08/2023 15:40, Siddhesh Poyarekar wrote:
On 2023-08-08 10:37, Jakub Jelinek wrote:
On Tue, Aug 08, 2023 at 10:30:10AM -0400, Siddhesh Poyarekar wrote:
Do you have a suggestion for the language to address libgcc, libstdc++,
etc. and libiberty, libbacktrace, etc.?
I'll work on this a bit and share a draft.
BTW, I think we should perhaps differentiate between production ready
libraries (e.g. libgcc, libstdc++, libgomp, libatomic, libgfortran,
libquadmath,
libssp) vs. e.g. the sanitizer libraries which are meant for debugging
and
Agreed, that's why I need some time to sort all of the libraries gcc
builds to categorize them into various levels of support in terms of
safety re. untrusted input.
Thanks,
Sid
Related to this, our coding standards should really reflect what we
consider good practice these days. eg. There are many library APIs
around that were once considered acceptable that frankly we would be
better uninventing.
R.
