public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/93038] Missing dependencies in depfile for imported files at compilation time Date: Sat, 21 Mar 2020 23:13:49 +0000 [thread overview] Message-ID: <bug-93038-4-m1YALLrjlU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93038-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93038 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Iain Buclaw <ibuclaw@gcc.gnu.org>: https://gcc.gnu.org/g:4a01f7b1e73e98a86520d8a825ddd3777faa7c33 commit r10-7320-g4a01f7b1e73e98a86520d8a825ddd3777faa7c33 Author: Iain Buclaw <ibuclaw@gdcproject.org> Date: Sun Mar 22 00:10:17 2020 +0100 d: Fix missing dependencies in depfile for imported files (PR93038) A new field for tracking imported files was added to the front-end, this makes use of it by writing all such files in the make dependency list. gcc/d/ChangeLog: 2020-03-22 Iain Buclaw <ibuclaw@gdcproject.org> PR d/93038 * d-lang.cc (deps_write): Add content imported files to the make dependency list. gcc/testsuite/ChangeLog: 2020-03-22 Iain Buclaw <ibuclaw@gdcproject.org> PR d/93038 * gdc.dg/fileimports/pr93038.txt: New test. * gdc.dg/pr93038.d: New test.
next prev parent reply other threads:[~2020-03-21 23:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93038-4@http.gcc.gnu.org/bugzilla/> 2020-03-13 21:00 ` ibuclaw at gcc dot gnu.org 2020-03-13 21:17 ` pierrick.bouvier at posteo dot net 2020-03-21 23:13 ` cvs-commit at gcc dot gnu.org [this message] 2020-03-21 23:47 ` ibuclaw at gdcproject dot org 2020-03-22 12:20 ` 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-93038-4-m1YALLrjlU@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).