public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/115295] [15 regression] Various gdc testsuite regressions
Date: Tue, 11 Jun 2024 19:15:43 +0000 [thread overview]
Message-ID: <bug-115295-4-7CGNhWfJr3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115295-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115295
--- Comment #3 from Iain Buclaw <ibuclaw at gcc dot gnu.org> ---
(In reply to Alexandre Oliva from comment #2)
> Ugh, it looks like D deviates from one of the fundamental assumptions behind
> the change, namely, that for each named source file, the compiler would
> attempt to generate one (set of) output files, so when not linking, an
> explicitly named output file would be rejected by the compiler.
>
> I suppose we could make the new behavior of omitting additional sources in
> compile tests dependent on the input language.
This is because D (and at a glance Go and Rust too) sets this setting in
lang-specs.h
```
int combinable; /* If nonzero, compiler can deal with
multiple source files at once (IMA). */
```
next prev parent reply other threads:[~2024-06-11 19:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 19:33 [Bug d/115295] New: " ro at gcc dot gnu.org
2024-05-30 19:34 ` [Bug d/115295] " ro at gcc dot gnu.org
2024-05-31 14:55 ` ro at gcc dot gnu.org
2024-06-11 16:06 ` aoliva at gcc dot gnu.org
2024-06-11 19:15 ` ibuclaw at gcc dot gnu.org [this message]
2024-06-12 2:03 ` aoliva at gcc dot gnu.org
2024-06-12 2:21 ` pinskia 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-115295-4-7CGNhWfJr3@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: link
Be 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).