public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub.kulik at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/107491] Gccgo stack not resizing on Solaris Date: Tue, 29 Nov 2022 14:44:44 +0000 [thread overview] Message-ID: <bug-107491-4-TvCN7u88hM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107491-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107491 --- Comment #12 from Jakub Kulik <jakub.kulik at oracle dot com> --- 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 already existing SetMaxStack() [1], although I do understand that that would be a bigger change and would make the code using it golang incompatible, which might be a problem. There is probably not much to do about this - I just wanted to mention this limitation. [1] https://pkg.go.dev/runtime/debug#SetMaxStack
prev parent reply other threads:[~2022-11-29 14:44 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-01 10:22 [Bug go/107491] New: GccGo " jakub.kulik at oracle dot com 2022-11-01 11:02 ` [Bug go/107491] Gccgo " ebotcazou at gcc dot gnu.org 2022-11-01 11:11 ` jakub.kulik at oracle dot com 2022-11-01 15:42 ` ian at airs dot com 2022-11-02 13:15 ` jakub.kulik at oracle dot com 2022-11-02 16:59 ` ian at airs dot com 2022-11-03 14:38 ` jakub.kulik at oracle dot com 2022-11-03 15:55 ` ian at airs dot com 2022-11-11 10:51 ` jakub.kulik at oracle dot com 2022-11-11 17:34 ` ian at airs dot com 2022-11-21 12:08 ` jakub.kulik at oracle dot com 2022-11-21 12:11 ` jakub.kulik at oracle dot com 2022-11-29 14:44 ` jakub.kulik at oracle dot com [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-107491-4-TvCN7u88hM@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).