> -Original Message-
> From: Sam James
> Sent: Thursday, August 15, 2024 6:30 AM
> To: Jiang, Haochen
> Cc: gcc-regress...@gcc.gnu.org; gcc-testresu...@gcc.gnu.org;
> gcc@gcc.gnu.org
> Subject: Re: gcc-regression script build fail info
>
> "Jiang, Haochen" writes:
>
> > Ping for this t
"Jiang, Haochen" writes:
> Ping for this thread.
>
> Any ideas? If no, I will change the generated info with command following
> if we take r15-1643 as example and see if it is clearer:
>
> head -26 makelog.r15-1643.x86_64.native | tail -7 > 1.log;
> grep -E "(error:|Error)" makelog.r15-1643.x86_
[To: s/gcc-patches/gcc/]
Hi,
Attached is a new revision of the proposal for WG14 for adding an
elementsof() operator (both the man(7) source, and the generated PDF).
v2.2:
- Rename lengthof => elementsof. Aaron found incompatible existing
functions called lengthof() in the wild.
- Requi
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 by hacking the epilogue to unlink the
f
[CC: s/gcc-patches@/gcc@/]
Hi Jens,
On Wed, Aug 14, 2024 at 05:44:57PM GMT, Jens Gustedt wrote:
> > However, strlen(3) came first, and we must respect it.
>
> Sure, string length, a dynamic feature, and array length are two features.
(Except that I've seen --and also written myself-- also stri
Hi!
Currently, I'm looking at PR115731. To summarize the issue, it is
possible for the user to, through coroutines, observe the closure type
of a lambda before it is completed. This closure type, in GCC, is
started before and finished after parsing the lambda body, meaning that
it is incomplete
