ALLEGRO_THREAD stacksize

ALLEGRO_THREAD stacksize

Aldrik

Member #16,925

December 2018

Is it possible to set the stack size of an ALLEGRO_THREAD?

Edgar Reynaldo

Major Reynaldo

May 2007

I don't know what you mean. What is the stack size? You mean the heap vs stack stack?

You can't make an ALLEGRO_THREAD on the stack. It's an opaque data structure. You can only create and destroy them using al_create_thread and al_destroy_thread.

Eagle and Allegro 5 binaries | Older Allegro 4 and 5 binaries | Allegro 5 compile guide
King Piccolo will make it so Then I could just flip it with some sweet, sweet matrix math. In either case, I’ll ride this wagon until the wheels fall off. Thanks to those that keep it running

Peter Hull

Member #1,136

March 2001

I assume Aldrik means - is it possible to set the amount of memory allocated to a new thread's stack when it's created? (each thread has its own stack for subroutine returns and local variables, obvs)
This is possible with the underlying thread libraries (see http://man7.org/linux/man-pages/man3/pthread_attr_setstacksize.3.html and https://docs.microsoft.com/en-gb/windows/desktop/ProcThread/thread-stack-size for example) but AFAIK not exposed to the Allegro API.

SiegeLord

Member #7,827

October 2006

Sounds like a reasonable addition, pull requests welcome .

"For in much wisdom is much grief: and he that increases knowledge increases sorrow."-Ecclesiastes 1:18
[SiegeLord's Abode][Codes]:[DAllegro5]:[RustAllegro]

Peter Hull

Member #1,136

March 2001

SiegeLord, while you're here, what do you think of https://www.allegro.cc/forums/thread/617697 ?

SiegeLord

Member #7,827

October 2006

Peter Hull said:

SiegeLord, while you're here, what do you think of https://www.allegro.cc/forums/thread/617697 ?

We should be using UNICODE for things. We already do for most things, but somehow not joysticks. https://github.com/liballeg/allegro5/issues/397 is an issue that applies to this, fwiw.

"For in much wisdom is much grief: and he that increases knowledge increases sorrow."-Ecclesiastes 1:18
[SiegeLord's Abode][Codes]:[DAllegro5]:[RustAllegro]

Aldrik

Member #16,925

December 2018

I forked the allegro5 repo and am working on adding this feature. however, when I try to test it in a test project al_init fails (I think because of different versions?). Can anyone help me with this? I tried defining ALLEGRO_UNSTABLE in the test project but this didn't change anything.

Edgar Reynaldo

Major Reynaldo

May 2007

Aldrik,

When al_init fails, it's usually because the runtime is not the same version as the version used to compile with. So you may have old DLLs somewhere.

Aldrik

Member #16,925

December 2018

I have made a pull request regarding this issue. This is my first ever contribution to an open source project so feedback is appreciated.
https://github.com/liballeg/allegro5/pull/992

Peter Hull

Member #1,136

March 2001

I hesitate to say this but that 'pattern' of having an extended creation function ( al_create_thread_with_stacksize ) to go alongside the standard one ( al_create_thread ) is not consistent with other Allegro functions.

But the alternative is to follow displays and bitmaps, and have al_set_new_thread_option - which is more cumbersome! (given that there aren't many options available for creating threads beyond stack size and priority)

Code itself looks OK on first glance.

[edit] Hopefully Siegelord can comment.

Doctor Cop

Member #16,833

April 2018

I was set to work on it, it was for FileSystem as I remember it but I couldn't wrap my had around Win32 API. I'm still learning it so I can contribute.

Luck my liver, cause I have to digest it!