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] Allow to run unittests before main() Date: Thu, 16 Dec 2021 07:19:26 +0000 [thread overview] Message-ID: <bug-103728-4-QfEyZRPtvy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103728-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103728 --- Comment #2 from Pierrick Bouvier <pierrick.bouvier at posteo dot net> --- Problem with command line approach is that it implies to patch all our scripts, which is *really* boring. At this point, manually adding rt_options string in all binaries is easier. Alas, there is no environment variable for controlling this. When unittests semantic was changed in dmd, from what I read, dmd maintainers were not open to keep an "old" mode as a compiler option. I understand it's not the role of gdc to control this, but I still think it could be useful to offer a flag (that automatically generates rt_options symbol).
next prev parent reply other threads:[~2021-12-16 7:19 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-15 8:22 [Bug d/103728] New: " pierrick.bouvier at posteo dot net 2021-12-15 22:57 ` [Bug d/103728] " ibuclaw at gdcproject dot org 2021-12-16 7:19 ` pierrick.bouvier at posteo dot net [this message] 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-QfEyZRPtvy@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).