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: Fri, 11 Nov 2022 10:51:53 +0000	[thread overview]
Message-ID: <bug-107491-4-Omg0NeXMGp@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 #8 from Jakub Kulik <jakub.kulik at oracle dot com> ---
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 anything GODEBUG
related)?

As for the split stack, I will try looking into it and see if it works. Having
overhead might solve the issue with no linker support, but it's indeed pretty
wasteful (and might break what works currently)...

  parent reply	other threads:[~2022-11-11 10:51 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 [this message]
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

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-Omg0NeXMGp@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: link
Be 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).