On Mon, 19 Aug 2024, Eric Gallager via Gcc-cvs-wwwdocs wrote:
> This is an automated email from the git hooks/post-receive script. It was
> generated because a ref change was pushed to the repository containing
> the project "gcc-wwwdocs".
>
> The branch, python-formatting has been created
>
Snapshot gcc-12-20240822 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20240822/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Hello,
Do you need Building Estimates and Drawings?
We provide Residential and Commercial Estimates, Take-offs and Layout plans,
permit drawings/Architecture work.
Send plans for good budget and unmatched experience. Drop an email for any
samples, queries for your projects.
Thank you.
Mich
On 8/15/24 06:24, Michael Clark wrote:
Hi Folks,
*sending again with Thunderbird because Apple Mail munged the message*.
I wanted to share a seed of an idea I have been ruminating on for a
while, and that is being able to return alloca memory from a function.
I think it’s trivially possible
On 8/23/24 15:24, Michael Clark wrote:
On 8/15/24 06:24, Michael Clark wrote:
Hi Folks,
like I said this is crazy talk as alloca isn't even in the C standard.
but VLAs are, and the current implementation of VLAs depends on alloca.
one more thing. it doesn't require PT_GNU_STACK or writable s
On 8/23/24 15:46, Michael Clark wrote:
one more thing. it doesn't require PT_GNU_STACK or writable stacks like
GCC nested functions. 🙂 so I think it is safer but it does have safety
issues, mostly related to stack overflows but its going to need some
careful analysis with respect to ROP.
brai
Am Freitag, dem 23.08.2024 um 15:46 +1200 schrieb Michael Clark via Gcc:
> On 8/23/24 15:24, Michael Clark wrote:
> > On 8/15/24 06:24, Michael Clark wrote:
> > > Hi Folks,
> > >
> > like I said this is crazy talk as alloca isn't even in the C standard.
> > but VLAs are, and the current implement
On 8/23/24 15:57, Michael Clark wrote:
On 8/23/24 15:46, Michael Clark wrote:
one more thing. it doesn't require PT_GNU_STACK or writable stacks
like GCC nested functions. 🙂 so I think it is safer but it does have
safety issues, mostly related to stack overflows but its going to need
some care
