public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pierrick.bouvier at posteo dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/103728] New: Allow to run unittests before main() Date: Wed, 15 Dec 2021 08:22:42 +0000 [thread overview] Message-ID: <bug-103728-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103728 Bug ID: 103728 Summary: Allow to run unittests before main() Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: pierrick.bouvier at posteo dot net Target Milestone: --- With gdc-12, semantic of unittests will change to match dmd behavior. So far (<= gdc-11), option -funittest could be used to: - compile unittest - automatically run them before main >From gdc-12, semantic will be: - compile unittest - only run them For users using dub (test), it may sound like the good choice. But for all others (we use meson), this change is really a burden. --- >From this post: https://forum.dlang.org/thread/jrnyklhuqadormjmelae@forum.dlang.org someone suggested to use this: version (unittest) extern(C) __gshared string[] rt_options = [ "testmode=run-main" ]; It works well with gdc-12, but it is very cryptic and still hard to add in all our binaries (we have dozens). --- Would you consider to add an option -funittest-and-run-main (or similar), to allow for that thanks to a compiler switch? Thanks for your hard work on gdc and porting to new front-end.
next reply other threads:[~2021-12-15 8:22 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-15 8:22 pierrick.bouvier at posteo dot net [this message] 2021-12-15 22:57 ` [Bug d/103728] " ibuclaw at gdcproject dot org 2021-12-16 7:19 ` pierrick.bouvier at posteo dot net 2021-12-25 17:43 ` ibuclaw at gdcproject dot org 2021-12-26 10:18 ` pierrick.bouvier at posteo dot net 2021-12-26 10:19 ` pierrick.bouvier at posteo dot net
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-103728-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).