On 03/23/2015 11:14 AM, Peter Maydell wrote:
On 23 March 2015 at 14:52, John Snow wrote:
On 03/23/2015 09:11 AM, Peter Maydell wrote:
This is really working around a bug in either ccache or
in the way Fedora has configured ccache, so I kind of
feel it ought to be dealt with there. However I
On 23 March 2015 at 14:52, John Snow wrote:
> On 03/23/2015 09:11 AM, Peter Maydell wrote:
>> This is really working around a bug in either ccache or
>> in the way Fedora has configured ccache, so I kind of
>> feel it ought to be dealt with there. However I don't
>> object too much to our includin
On 03/23/2015 09:11 AM, Peter Maydell wrote:
On 19 March 2015 at 19:01, John Snow wrote:
Test if ccache is interfering with our life, and
disable its habit of trying to compile already pre-processed
versions of code if so.
In particular, clang has different semantic warnings based on
if the
On 19 March 2015 at 19:01, John Snow wrote:
> Test if ccache is interfering with our life, and
> disable its habit of trying to compile already pre-processed
> versions of code if so.
>
> In particular, clang has different semantic warnings based on
> if the warning arose from a macro or not. By t
On Thu, Mar 19, 2015 at 03:01:37PM -0400, John Snow wrote:
> +
> +# check if ccache is interfering with
> +# semantic analysis of macros
> +
> +ccache=no
> +cat > $TMPC << EOF
> +static const int Z = 1;
> +#define fn() ({ Z; })
> +#define TAUT(X) ((X) == Z)
>
Test if ccache is interfering with our life, and
disable its habit of trying to compile already pre-processed
versions of code if so.
In particular, clang has different semantic warnings based on
if the warning arose from a macro or not. By trying to build
preprocessed versions of code, we get mor
