Re: Avoiding stack buffer clear being optimised out

To: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
Subject: Re: Avoiding stack buffer clear being optimised out
From: Jonny Grant <jg@xxxxxxxx>
Date: Tue, 24 Jan 2023 13:52:51 +0000
Cc: gcc-help <gcc-help@xxxxxxxxxxx>
In-reply-to: <68c69b5a-e6e7-7021-5f98-37ba8f3c49eb@jguk.org>
References: <4366aeb5-7fdb-6fa4-b0f5-ebe74c1d4fb2@jguk.org> <CAH6eHdRLzrZO04axQ3ozEi=6y18p2L1ZMstq2TmKXLpCzycumw@mail.gmail.com> <68c69b5a-e6e7-7021-5f98-37ba8f3c49eb@jguk.org>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2

Probably other functions be "compiled out" like memset() is, would memcpy() be compiled out?
Jonny

Follow-Ups:
- Re: Avoiding stack buffer clear being optimised out
  - From: Jonathan Wakely via Gcc-help

References:
- Avoiding stack buffer clear being optimised out
  - From: Jonny Grant
- Re: Avoiding stack buffer clear being optimised out
  - From: Jonathan Wakely via Gcc-help
- Re: Avoiding stack buffer clear being optimised out
  - From: Jonny Grant