Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Thiago Adams <thiago.adams@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: transpiling to low level C
Date: Wed, 18 Dec 2024 16:43:59 -0300
Organization: A noiseless patient Spider
Lines: 17
Message-ID: <vjv8lv$2edrv$1@dont-email.me>
References: <vjlh19$8j4k$1@dont-email.me>
 <vjn9g5$n0vl$1@raubtier-asyl.eternal-september.org>
 <vjnhsq$oh1f$1@dont-email.me> <vjnq5s$pubt$1@dont-email.me>
 <vjp2f3$13k4m$2@dont-email.me> <vjr7np$1j57r$2@dont-email.me>
 <vjsdum$1rfp2$1@dont-email.me> <vjse6l$1rfp2$2@dont-email.me>
 <vjsf6g$1rlkq$1@dont-email.me> <vjsgdr$1rrvs$1@dont-email.me>
 <vjsi61$1rlkq$2@dont-email.me> <vjsk7q$1rrvs$2@dont-email.me>
 <vjv5ir$2ds8r$2@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 18 Dec 2024 20:43:59 +0100 (CET)
Injection-Info: dont-email.me; posting-host="0ecc45d771ee768cde30c5cfc52f49c4";
	logging-data="2570111"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+U1TOG9bS6NcYH5UYd+h2jqdFddTgsiN0="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:u0MPAYIErCZ+hl1B3nurjwNiqMc=
In-Reply-To: <vjv5ir$2ds8r$2@dont-email.me>
Content-Language: en-GB
Bytes: 2068

Em 12/18/2024 3:51 PM, BGB escreveu:
> 
> I took a different approach:
> In the backend IR stage, structs are essentially treated as references 
> to the structure.
> 
> A local structure may be "initialized" via an IR operation, in which 
> point it will be assigned storage in the stack frame, and the reference 
> will be initialized to the storage area for the structure.
> 
> Most operations will pass them by reference.
> 
> Assigning a struct will essentially be turned into a struct-copy 
> operation (using the same mechanism as inline memcpy).

But what happens with calling a external C function that has a struct X 
as parameter? (not pointer to struct)