Re: Merging Luc's master branch.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Mar 2, 2018 at 3:33 PM, Ramsay Jones
<ramsay@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> Note that I didn't get any unexpected failures - Chris mentioned
> some failures (on Linux?).

That is on the merge-luc-master branch. It is not part of the
0.5.2-RC1 release. So Luc is proposing make a 0.5.2 release
first before merging luc's master branch.

>
>> I've quickly checked and those workarounds doesn't have
>> a negative effect on my environments, so I'm fine with
>> them and to me they can even go into to current HEAD
>> (or upcoming release 0.5.2 if Chris is fine doing one).
>
> I don't think I would apply them as-is - I've been meaning
> to install LLVM on Linux again, so I can check these things
> out for myself. Also, I think these are platform specific
> (maybe!). ;-)

I am fine with either way. I should suggest hold it off for
0.5.2 because none of us have try those very strange flags
on Linux yet.

Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Newbies FAQ]     [LKML]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Trinity Fuzzer Tool]

  Powered by Linux