Hi all
I decided to start a separate thread for asking about potential candidate for
crowd-funding.
My personal wish-list is:
- support for array calculations / automatic loop parallelization via SSE, AVX,
etc.
Both static and dynamic arrays should supported.
Once implemented vector operat
> Hi all
>
> I decided to start a separate thread for asking about potential candidate
> for crowd-funding.
>
> My personal wish-list is:
> - support for array calculations / automatic loop parallelization via SSE,
> AVX, etc.
> Both static and dynamic arrays should supported.
> Once implemente
> I will leave the technical comments to the compiler developers.
>
>> BTW, is it possible to state the specific project when donating?
>
> Yes, if I recall correctly you can give a message when the paypal donate
> page appears. (just as you can state that you want to be in the hall of
> fame)
O
Am Mi., 19. Dez. 2018, 09:03 hat denisgolovan
geschrieben:
> My personal wish-list is:
> - support for array calculations / automatic loop parallelization via SSE,
> AVX, etc.
> Both static and dynamic arrays should supported.
> Once implemented vector operations on arrays (ala APL) might be
> The main problem here is to model what registers an instruction uses and
> modifies so that the register allocator of the surrounding function can take
> that into account accordingly... Maybe as a first step we could allow in
> lining
> for funcrions that have a register clause with the touched
>> - Custom/separate allocators for dynamic arrays (to avoid manually patching
>> compiler).
>
> Why do you need that?
Besides ordinary arrays I allocate/use arrays backed by mmaped files.
Existing functions taking arrays as arguments mostly remain working
transparently.
That's a huge win in c
El 19/12/18 a las 09:02, denisgolovan escribió:
Hi all
I decided to start a separate thread for asking about potential candidate for
crowd-funding.
My personal wish-list is:
- support for array calculations / automatic loop parallelization via SSE, AVX,
etc.
Both static and dynamic arrays
> On Dec 19, 2018, at 5:23 PM, Sven Barth via fpc-pascal
> wrote:
>
> A library as first step would be more useful. Later on one can think about
> integrating it into the language itself.
>
How does that work? I’ve been interested in coroutines for a while now but I
don’t understand how t
> On Dec 19, 2018, at 6:35 PM, Ryan Joseph wrote:
>
> How does that work? I’ve been interested in coroutines for a while now but I
> don’t understand how they function in the language. They would need to manage
> stack states and push/restore stacks, which is something a library can’t do
> r
Am Mi., 19. Dez. 2018, 13:18 hat Ryan Joseph
geschrieben:
>
>
> > On Dec 19, 2018, at 6:35 PM, Ryan Joseph
> wrote:
> >
> > How does that work? I’ve been interested in coroutines for a while now
> but I don’t understand how they function in the language. They would need
> to manage stack states
Am Mi., 19. Dez. 2018, 11:38 hat Martok
geschrieben:
> > The main problem here is to model what registers an instruction uses and
> > modifies so that the register allocator of the surrounding function can
> take
> > that into account accordingly... Maybe as a first step we could allow in
> linin
Hi,
On Wed, 19 Dec 2018, Ryan Joseph wrote:
> > On Dec 19, 2018, at 5:23 PM, Sven Barth via fpc-pascal
> > wrote:
> >
> > A library as first step would be more useful. Later on one can think
> > about integrating it into the language itself.
> >
>
> How does that work? I’ve been interested in co
> On Dec 19, 2018, at 9:28 PM, Karoly Balogh (Charlie/SGR)
> wrote:
>
> (After reading that old thread we had...)
>
> Actually, it can. The only thing you need to do is to allocate a stack
> first, then make the "coroutine" functions use it, which is basically
> boils down to how you pass you
Hi,
On Wed, 19 Dec 2018, Ryan Joseph wrote:
> > (After reading that old thread we had...)
> >
> > Actually, it can. The only thing you need to do is to allocate a stack
> > first, then make the "coroutine" functions use it, which is basically
> > boils down to how you pass your arguments and self
> On Dec 20, 2018, at 1:17 AM, Karoly Balogh (Charlie/SGR)
> wrote:
>
> No, that assembly function just does swapping of the stack and storing the
> caller's stack settings and setting up the coroutine's stack instead. The
> actual stack is allocated with the Win32 API function VirtualAlloc(),
15 matches
Mail list logo
