On Tue, Aug 11, 2015 at 8:38 PM Richard Smith wrote:
> Those files were parsed as part of building the output, and are legitimate
> dependencies of the compilation process; why do you want to suppress them
> from the .d file? (I think adding a whole bunch of -fno-*-deps flags is
> going in the wr
Those files were parsed as part of building the output, and are legitimate
dependencies of the compilation process; why do you want to suppress them
from the .d file? (I think adding a whole bunch of -fno-*-deps flags is
going in the wrong direction, and would like to understand if there's some
hig
Ah, so we need a flag -fno-module-map-file-deps, I assume...
On Tue, Aug 11, 2015 at 8:12 PM Richard Smith wrote:
> On Tue, Aug 11, 2015 at 4:57 AM, Manuel Klimek wrote:
>
>> I believe this breaks -fno-module-file-deps.
>>
>
> I don't think so; this affects which module map files end up in the
On Tue, Aug 11, 2015 at 4:57 AM, Manuel Klimek wrote:
> I believe this breaks -fno-module-file-deps.
>
I don't think so; this affects which module map files end up in the .d
file, not which .pcm files do.
> On Sun, Aug 9, 2015 at 6:47 AM Richard Smith via cfe-commits <
> cfe-commits@lists.llvm
I believe this breaks -fno-module-file-deps.
On Sun, Aug 9, 2015 at 6:47 AM Richard Smith via cfe-commits <
cfe-commits@lists.llvm.org> wrote:
> Author: rsmith
> Date: Sat Aug 8 23:46:57 2015
> New Revision: 244413
>
> URL: http://llvm.org/viewvc/llvm-project?rev=244413&view=rev
> Log:
> [module
