public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/90719] libphobos.phobos_shared/std/file.d FAILs on 32-bit Solaris Date: Wed, 29 Apr 2020 10:56:44 +0000 [thread overview] Message-ID: <bug-90719-4-xdYR5SjNbE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-90719-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90719 --- Comment #10 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #9 from ibuclaw at gcc dot gnu.org --- > (In reply to Rainer Orth from comment #8) [...] > Oops, I must have both misunderstood your original bug report (you mentioned > stat32_t) *and* the patch applied against the wrong struct. True, and the patch I'd attached didn't have enough context to fully see which struct it applied to. > Fix sent here: https://github.com/dlang/druntime/pull/3078 > > I'll downstream it (again) as soon as it's in. Great, thanks. > For GCC-11, I should really finish off some automated C header -> D conversion > tool, as you know all too well the pains of maintaining the current stdc and > sys packages in D runtime. Excellent idea: gccgo already does this with good success.
next prev parent reply other threads:[~2020-04-29 10:56 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-90719-4@http.gcc.gnu.org/bugzilla/> 2020-03-12 11:58 ` jakub at gcc dot gnu.org 2020-04-27 21:32 ` ibuclaw at gdcproject dot org 2020-04-27 21:34 ` cvs-commit at gcc dot gnu.org 2020-04-27 21:59 ` cvs-commit at gcc dot gnu.org 2020-04-27 22:01 ` ibuclaw at gdcproject dot org 2020-04-29 9:27 ` ro at gcc dot gnu.org 2020-04-29 10:21 ` ibuclaw at gcc dot gnu.org 2020-04-29 10:56 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2020-04-30 10:16 ` cvs-commit at gcc dot gnu.org 2020-05-16 20:54 ` cvs-commit at gcc dot gnu.org 2020-05-16 20:55 ` ibuclaw at gdcproject dot 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-90719-4-xdYR5SjNbE@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).