https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114416
--- Comment #22 from Jakub Kulik ---
Eric and Rainer, thank you both very much for all that testing and the fix.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114416
--- Comment #11 from Jakub Kulik ---
> This is a bit of circular reasoning but, if the rule had been crystal clear,
> GCC would have implemented it at some point during the last quarter of
> century.
I see. I guess it's also not a common enough
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114416
--- Comment #10 from Jakub Kulik ---
Sorry for longer response.
I asked internally again and was told by a colleague who was in the room when
the spec was created, that: "the intent was (and is) that the individual
elements/atoms/fundamental ty
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114416
--- Comment #7 from Jakub Kulik ---
Hmm, I just realized that you referred to the same sections, so my previous
comment might not make it clearer...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114416
Jakub Kulik changed:
What|Removed |Added
CC||jakub.kulik at oracle dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107491
--- Comment #12 from Jakub Kulik ---
One thing that is still slightly limiting is that the stack size cannot be
changed e.g. for individual tests when running the libgo test suite.
It might be nice to have some exported interface, such as the a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107491
--- Comment #11 from Jakub Kulik ---
So, I looked into it and with the patch attached above seems to work as
expected. Stack can be resized like this `GODEBUG=minstacksize=32 ./test`.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107491
--- Comment #10 from Jakub Kulik ---
Created attachment 53935
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53935&action=edit
Proposed patch with configurable minimal stack size
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107491
--- Comment #8 from Jakub Kulik ---
Sure, this was just a quick first test. That said, GODEBUG is slightly more
complex - is there an example of a C code where GODEBUG variables are being
used you can point me to (I found only go sources with an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107491
--- Comment #6 from Jakub Kulik ---
So, I tested it with the following simple change and it works nicely:
--- gcc-12.2.0/libgo/runtime/proc.c
+++ gcc-12.2.0/libgo/runtime/proc.c
@@ -798,7 +798,15 @@ runtime_malg(bool allocatestack, bool si
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107491
--- Comment #4 from Jakub Kulik ---
Thanks for the confirmation.
-fsplit-stack on Solaris would be nice, but it's as simple as designating a TLS
accessible slot, right? We have our own linker on Solaris and don't use gold,
and I am not how feas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107491
--- Comment #2 from Jakub Kulik ---
That's what I thought, but I am not sure whether there is supposed to be a
different mechanism on other platforms or whether the 4MB stack cap per thread
is the maximum I can get on non Linux platform.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107491
Bug ID: 107491
Summary: GccGo stack not resizing on Solaris
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
13 matches
Mail list logo
