On 28/09/2023 12:55, Siddhesh Poyarekar wrote:
> +Security features implemented in GCC
> +
> +
[...]
> +
> +Similarly, GCC may transform code in a way that the correctness of
> +the expressed algorithm is preserved, but supplementary properties
> +tha
On 2023-10-04 11:49, Alexander Monakov wrote:
On Thu, 28 Sep 2023, Siddhesh Poyarekar wrote:
Define a security process and exclusions to security issues for GCC and
all components it ships.
Some typos and wording suggestions below.
I've incorporated all your and David's suggestions and
On Thu, 28 Sep 2023, Siddhesh Poyarekar wrote:
> Define a security process and exclusions to security issues for GCC and
> all components it ships.
Some typos and wording suggestions below.
> --- /dev/null
> +++ b/SECURITY.txt
> @@ -0,0 +1,205 @@
> +What is a GCC security bug?
> +=
Hi, Siddhesh
Thanks for working on this and fine-tuning the original proposed text. It
looks good to me. Minor grammatical nit below.
Thanks, David
On Thu, Sep 28, 2023 at 7:59 AM Siddhesh Poyarekar
wrote:
> On 2023-09-28 12:55, Siddhesh Poyarekar wrote:
> > Define a security process and exc
Ping!
On 2023-09-28 07:55, Siddhesh Poyarekar wrote:
Define a security process and exclusions to security issues for GCC and
all components it ships.
Signed-off-by: Siddhesh Poyarekar
---
SECURITY.txt | 205 +++
1 file changed, 205 insertions(
On 2023-09-28 12:55, Siddhesh Poyarekar wrote:
Define a security process and exclusions to security issues for GCC and
all components it ships.
Signed-off-by: Siddhesh Poyarekar
---
Sorry I forgot to summarize changes since the previous version:
- Reworded the introduction so that it doesn't
Define a security process and exclusions to security issues for GCC and
all components it ships.
Signed-off-by: Siddhesh Poyarekar
---
SECURITY.txt | 205 +++
1 file changed, 205 insertions(+)
create mode 100644 SECURITY.txt
diff --git a/SECURITY
