From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Yann Droneaud <ydroneaud@opteya.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v3] Add _FORTIFY_SOURCE implementation documentation [BZ #28998]
Date: Fri, 6 Jan 2023 07:27:11 -0500 [thread overview]
Message-ID: <6c4f8d66-872e-f7f3-0bfc-b5ea2b175aa1@sourceware.org> (raw)
In-Reply-To: <03eac5f2-67ad-b3d6-4dcf-f88948d731c5@opteya.com>
On 2023-01-05 16:04, Yann Droneaud wrote:
>> +The @code{_FORTIFY_SOURCE} macro may be defined by users to control
>> +hardening of calls into some functions in @theglibc{}.
>
> Macro must be defined before header inclusion.
>
Thanks, I changed this to:
The @code{_FORTIFY_SOURCE} macro may be defined by users to control
hardening of calls into some functions in @theglibc{}. The definition
should be at the top of the source file before any headers are included
or at the pre-processor commandline using the @code{-D} switch.
Sid
next prev parent reply other threads:[~2023-01-06 12:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 16:25 [PATCH] " Siddhesh Poyarekar
2022-12-15 16:35 ` Andreas Schwab
2022-12-15 16:37 ` Siddhesh Poyarekar
2022-12-22 12:56 ` Siddhesh Poyarekar
2022-12-22 13:08 ` Sam James
2023-01-03 14:43 ` Siddhesh Poyarekar
2023-01-04 23:49 ` Jeff Law
2022-12-22 13:35 ` Florian Weimer
2022-12-22 14:19 ` Siddhesh Poyarekar
2022-12-22 14:22 ` Siddhesh Poyarekar
2022-12-22 15:32 ` [PATCH v2] " Siddhesh Poyarekar
2022-12-22 16:04 ` [PATCH v3] " Siddhesh Poyarekar
2023-01-03 14:29 ` [ping][PATCH " Siddhesh Poyarekar
2023-01-05 21:04 ` [PATCH " Yann Droneaud
2023-01-06 12:27 ` Siddhesh Poyarekar [this message]
2023-01-09 15:32 ` Florian Weimer
2023-01-10 13:03 ` Siddhesh Poyarekar
2023-01-11 6:45 ` Sam James
2023-01-10 13:40 ` [PATCH v4] " Siddhesh Poyarekar
2023-01-10 15:00 ` Florian Weimer
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=6c4f8d66-872e-f7f3-0bfc-b5ea2b175aa1@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=ydroneaud@opteya.com \
/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: link
Be 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).