public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kallisti5 at unixzen dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/113143] Remove usage of ucontext.h Date: Wed, 27 Dec 2023 03:38:02 +0000 [thread overview] Message-ID: <bug-113143-4-GL9lhtjlKK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113143-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113143 --- Comment #9 from Alexander von Gluck <kallisti5 at unixzen dot com> --- Doing a little research, it looks like complaints of ucontext.h have come up before multiple times: Similar issue on OpenBSD a long time ago: https://gcc-help.gcc.gnu.narkive.com/Xx1bResV/can-t-build-go-support-in-gcc-4-8-1-on-openbsd muslc not supporting ucontext.h: https://wiki.musl-libc.org/open-issues (and a long list of google results) I guess the root questions of this bug are: 1. Should any and all references to ucontext.h be wrapped with a HAVE macro? (this seems to be what most folks do). Since (get/set/swap)context don't seem to be called on non-BSD platforms, this seems possible? 2. Should libgo double down and implement processor-specific calls for each architecture as called out by Ian in the above thread in 2013? "It's possible to fix this by writing processor-dependent functions that would serve the same purpose as the *context functions, and in fact that would be more efficient. But I have not actually done this." 3. Is the expectation that all platforms which libgo targets include ucontext.h compatibility libraries for calls no-longer standard in the posix specifications since 2008. (muslc pushed against this... i'd be interested if libgo compiles under musl systems)
next prev parent reply other threads:[~2023-12-27 3:38 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-26 3:43 [Bug go/113143] New: " kallisti5 at unixzen dot com 2023-12-26 3:48 ` [Bug go/113143] " kallisti5 at unixzen dot com 2023-12-26 4:48 ` ian at airs dot com 2023-12-26 13:13 ` kallisti5 at unixzen dot com 2023-12-26 23:16 ` ian at airs dot com 2023-12-27 2:31 ` kallisti5 at unixzen dot com 2023-12-27 2:34 ` kallisti5 at unixzen dot com 2023-12-27 2:40 ` pinskia at gcc dot gnu.org 2023-12-27 3:20 ` kallisti5 at unixzen dot com 2023-12-27 3:38 ` kallisti5 at unixzen dot com [this message] 2023-12-27 23:20 ` ian at airs dot com 2023-12-29 1:45 ` kallisti5 at unixzen dot com 2023-12-30 6:26 ` ian at airs 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-113143-4-GL9lhtjlKK@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).