<div dir="ltr">Sure, can do. I know that tests don't currently pass on M1s on trunk:<div><a href="https://bugs.llvm.org/show_bug.cgi?id=46647">https://bugs.llvm.org/show_bug.cgi?id=46647</a> (check-llvm)<br></div><div><a href="https://bugs.llvm.org/show_bug.cgi?id=46644">https://bugs.llvm.org/show_bug.cgi?id=46644</a> (check-clang<br></div><div>check-lld is fine, haven't tried anything else yet. What would the goal be? Make sure the 11.0 branch isn't worse than trunk?</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Dec 1, 2020 at 2:15 PM Hans Wennborg <<a href="mailto:hans@chromium.org">hans@chromium.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">Nico has an M1 and I think he looked at building LLVM on it too.<br>
Perhaps he can help out.<br>
<br>
On Tue, Dec 1, 2020 at 7:49 PM Tobias Hieta <<a href="mailto:tobias@plexapp.com" target="_blank">tobias@plexapp.com</a>> wrote:<br>
><br>
> Thats a very good point.<br>
><br>
> Maybe someone with an M1 machine can take on the task of testing releases on those? I would happily do that but I don't have such a machine and can't afford one right now unfortunately.<br>
><br>
> -- Tobias<br>
><br>
> On Tue, Dec 1, 2020, 19:21 Hans Wennborg <<a href="mailto:hans@chromium.org" target="_blank">hans@chromium.org</a>> wrote:<br>
>><br>
>> Hmm, but unless you're doing this on an arm64 machine, you won't be<br>
>> able to run the tests in Phase2 and 3?<br>
>><br>
>> On Tue, Dec 1, 2020 at 4:36 PM Tobias Hieta <<a href="mailto:tobias@plexapp.com" target="_blank">tobias@plexapp.com</a>> wrote:<br>
>> ><br>
>> > Yeah you can pass -DCMAKE_OSX_ARCHITECTURES=arm64;x86_64 and it will<br>
>> > make fat binaries.<br>
>> ><br>
>> > But it seems like we should probably do two packages. That probably<br>
>> > needs to be implemented in the test-release in the following way:<br>
>> ><br>
>> > Build Phase1 for the host currently running on. Then build Phase2 and<br>
>> > 3 for the target (arm64) and compare those.<br>
>> ><br>
>> > Anything I am not thinking about here or missing?<br>
>> ><br>
>> > -- Tobias<br>
>> ><br>
>> > On Tue, Dec 1, 2020 at 4:32 PM Hans Wennborg <<a href="mailto:hans@chromium.org" target="_blank">hans@chromium.org</a>> wrote:<br>
>> > ><br>
>> > > I think the separate packages make the most sense.<br>
>> > ><br>
>> > > Also, how would one practically go about doing the fat binary<br>
>> > > approach? Is there some cmake magic that would make it<br>
>> > > straight-forward?<br>
>> > ><br>
>> > > On Tue, Dec 1, 2020 at 4:13 PM Tobias Hieta via Release-testers<br>
>> > > <<a href="mailto:release-testers@lists.llvm.org" target="_blank">release-testers@lists.llvm.org</a>> wrote:<br>
>> > > ><br>
>> > > > I just realized that we should probably make an arm64 build as well<br>
>> > > > for those new fancy mac's.<br>
>> > > ><br>
>> > > > What do people think is the best solution here, a fat universal build<br>
>> > > > that will be double the size (currently llvm+clang is already ~400MB<br>
>> > > > packed so it will be very big), or two separate builds?<br>
>> > > ><br>
>> > > > The pro of having two separate builds is that we can set the correct<br>
>> > > > default triple instead of a single one, the downside is that I need to<br>
>> > > > build it twice for every version.<br>
>> > > ><br>
>> > > > -- Tobias<br>
>> > > ><br>
>> > > > On Tue, Dec 1, 2020 at 4:03 PM Tobias Hieta <<a href="mailto:tobias@plexapp.com" target="_blank">tobias@plexapp.com</a>> wrote:<br>
>> > > > ><br>
>> > > > > Tom,<br>
>> > > > ><br>
>> > > > > MacOS build: clang+llvm-11.0.1-rc1-x86_64-apple-darwin.tar.xz<br>
>> > > > > with SHA256: c9ee87d7e42df8494a9f42993ed499479b3ce118c940a6e8907d075ceb913223<br>
>> > > > > is uploaded.<br>
>> > > > ><br>
>> > > > > The same tests as before failed:<br>
>> > > > ><br>
>> > > > > FAIL: libunwind :: libunwind_01.pass.cpp (69255 of 69302)<br>
>> > > > > FAIL: libunwind :: signal_frame.pass.cpp (69258 of 69302)<br>
>> > > > ><br>
>> > > > > I had to use the following patch to use Python 3:<br>
>> > > > ><br>
>> > > > > diff --git a/openmp/runtime/test/lit.cfg b/openmp/runtime/test/lit.cfg<br>
>> > > > > index 357b18a205d..96c0c3a1da7 100644<br>
>> > > > > --- a/openmp/runtime/test/lit.cfg<br>
>> > > > > +++ b/openmp/runtime/test/lit.cfg<br>
>> > > > > @@ -76,7 +76,7 @@ if config.operating_system == 'Darwin':<br>
>> > > > > cmd = subprocess.Popen(['xcrun', '--show-sdk-path'],<br>
>> > > > > stdout=subprocess.PIPE, stderr=subprocess.PIPE)<br>
>> > > > > out, err = cmd.communicate()<br>
>> > > > > - out = out.strip()<br>
>> > > > > + out = out.strip().decode()<br>
>> > > > > res = cmd.wait()<br>
>> > > > > if res == 0 and out:<br>
>> > > > > config.test_flags += " -isysroot " + out<br>
>> > > > ><br>
>> > > > > otherwise tests failed to run.<br>
>> > > > ><br>
>> > > > > On Thu, Nov 26, 2020 at 8:21 AM Tom Stellard via Release-testers<br>
>> > > > > <<a href="mailto:release-testers@lists.llvm.org" target="_blank">release-testers@lists.llvm.org</a>> wrote:<br>
>> > > > > ><br>
>> > > > > > Hi,<br>
>> > > > > ><br>
>> > > > > > I've tagged LLVM 11.0.1-rc1. Testers may begin testing and uploading<br>
>> > > > > > binaries. If you still have bugs you want fixed in LLVM 11.0.1, you<br>
>> > > > > > have until Dec. 8 to request backports. You can make these requests by<br>
>> > > > > > filing a bug at <a href="http://bugs.llvm.org" rel="noreferrer" target="_blank">bugs.llvm.org</a> and putting release-11.0.1 in the 'blocks'<br>
>> > > > > > field.<br>
>> > > > > ><br>
>> > > > > > -Tom<br>
>> > > > > ><br>
>> > > > > > _______________________________________________<br>
>> > > > > > Release-testers mailing list<br>
>> > > > > > <a href="mailto:Release-testers@lists.llvm.org" target="_blank">Release-testers@lists.llvm.org</a><br>
>> > > > > > <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers</a><br>
>> > > > _______________________________________________<br>
>> > > > Release-testers mailing list<br>
>> > > > <a href="mailto:Release-testers@lists.llvm.org" target="_blank">Release-testers@lists.llvm.org</a><br>
>> > > > <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers</a><br>
</blockquote></div>