> On 7 May 2021, at 8:33 pm, Ken Cunningham <ken.cunningham.web...@gmail.com>
> wrote:
>
> There is one issue with that.
>
> qt5-qtcreator needs clang-10 on arm for it’s libraries (that is actually the
> only reason why I initially fixed clang-10 to work on arm64 in the first
> place).
>
> qt5-qtcreator cannot (could not) use any newer clang when I checked six
> months ago.
>
> So — we still need clang-10 on arm64 even if we don’t use it as a compiler
> there.
We can at least though not bother building the openmpi versions for these
clangs, even if we have to keep clang10 around for arm until we can migrate the
above to clang11.
Cheers Chris
>
> K
>
>
>
>> On May 7, 2021, at 12:22 PM, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote:
>>
>> Hi,
>>
>> Another clean up suggestion is to remove all clangs apart from 11+ for
>> macOS11(arm). I just noticed the buildbots building the clang-9.0 version
>> for arm, but its worth noting that clang 9.0 and 10 are not reliable for
>> arm, I have seen them generate bad code, fail with ICEs, so really there is
>> little point in providing all but the clang11(and newer) version which is
>> the first version with reliable arm support.
>>
>> Chris
>>
>>>> On 7 May 2021, at 8:11 pm, Ken Cunningham
>>>> <ken.cunningham.web...@gmail.com> wrote:
>>>
>>> Yes, gcc7 works down to 10.4, both PPC and Intel and is the primary
>>> compiler there. I can see no need for openMPI to support any older gcc.
>>>
>>> clang-3.3, clang-3.4, and clang-3.7 should not be used for anything other
>>> than bootstrapping to newer clangs now.
>>>
>>>
>>> Ken
>>>
>>>
>>
>
