public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug manual/28998] Document -D_FORTIFY_SOURCE Date: Thu, 24 Mar 2022 12:27:10 +0000 [thread overview] Message-ID: <bug-28998-131-1ffBOruPW9@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28998-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28998 Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adhemerval.zanella at linaro dot o | |rg --- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> --- It is documented briefly on manual/creature.texi: 303 @defvr Macro _FORTIFY_SOURCE 304 @standards{GNU, (none)} 305 If this macro is defined to @math{1}, security hardening is added to 306 various library functions. If defined to @math{2}, even stricter 307 checks are applied. If defined to @math{3}, @theglibc{} may also use 308 checks that may have an additional performance overhead. 309 @end defvr But there is no further explanation of exactly each level enables, the functions covered, and how it plays with compiler. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-03-24 12:27 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-24 11:58 [Bug manual/28998] New: " mliska at suse dot cz 2022-03-24 12:27 ` adhemerval.zanella at linaro dot org [this message] 2022-03-26 22:42 ` [Bug manual/28998] " sam at gentoo dot org 2022-08-02 13:24 ` mliska at suse dot cz 2022-08-02 22:43 ` siddhesh at sourceware dot org 2022-08-03 7:18 ` mliska at suse dot cz 2022-12-06 3:45 ` gandalf at winds dot org 2022-12-08 8:52 ` mliska at suse dot cz 2022-12-08 15:04 ` siddhesh at sourceware dot org 2023-01-10 15:23 ` cvs-commit at gcc dot gnu.org 2023-01-10 15:25 ` siddhesh at sourceware dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-28998-131-1ffBOruPW9@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).