public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bcallah at protonmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/99691] New: OpenBSD support for GDC Date: Sun, 21 Mar 2021 03:34:20 +0000 [thread overview] Message-ID: <bug-99691-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99691 Bug ID: 99691 Summary: OpenBSD support for GDC Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: bcallah at protonmail dot com Target Milestone: --- Created attachment 50441 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50441&action=edit OpenBSD support for GDC Hello -- Provided here is a patch demonstrating OpenBSD support for GDC. Some important notes and helps needed: * Iain, you'll notice that my druntime is different from the DMD druntime diff you saw on GitHub. I will do my best to sync the two, which will mean replacing what I've done for DMD with what I've done here for GDC, to make all lives easier. * I cannot get a shared libgphobos to work on OpenBSD. I get random crashes that I have not yet been able to track down. I do not know how to disable --enable-shared in libphobos's configure.ac without disabling it for all of gcc, which is not desirable. If that's a patch I have to carry until I can get a working shared libgphobos, that's fine. * I suspect libphobos will work on more than just x86_64 and i386 but as I've only been able to test on x86_64, I kept libphobos to just those 2 archs. I will submit further diffs for more platforms as I'm able to test. * The port is otherwise fairly straightforward and I am using this in production. Thanks! Happy to work with you to get this in.
next reply other threads:[~2021-03-21 3:34 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-21 3:34 bcallah at protonmail dot com [this message] 2021-03-21 7:20 ` [Bug d/99691] " ibuclaw at gdcproject dot org 2021-03-21 18:38 ` bcallah at protonmail dot com 2021-03-26 15:15 ` cvs-commit at gcc dot gnu.org 2021-04-19 17:28 ` cvs-commit at gcc dot gnu.org
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-99691-4@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).