<div dir="ltr">You can also use -frewrite-includes to avoid a full preprocessing (rather than -E). I'm not sure if this necessarily gets you exact warning reproducibility, but closer.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jan 5, 2020 at 8:26 AM Lubos Lunak via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Monday 30 of December 2019, Nehal J Wani via cfe-dev wrote:<br>
> - Is this behavior expected? Why does the warning throw up only when the<br>
> end user wants to do anything with the intermediate outputs? I ended up<br>
> here because this was failing my project when I was trying to use distcc.<br>
<br>
Some of Clang's warnings, such as this one, are disabled if the code comes <br>
from a macro expansion. This is why you see the warning only if you first <br>
expand the code.<br>
<br>
If your concern is just related to distributed compiling, either build <br>
without -Werror, or use icecc/icecream, which generally distributes the <br>
builds without preprocessing first.<br>
<br>
-- <br>
Lubos Lunak<br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
</blockquote></div>