Re: [llvm-dev] Upcoming upgrade of LLVM buildbot
Hello Galina! On 10/28/20 2:53 AM, Galina Kistanova via llvm-dev wrote: > llvm-zorg source code has been updated, and now is open for new changes. If > you have pending patches, please rebase them on top of the llvm-zorg master > and update your reviews on the Phabricator. I'll start reviewing them > shortly. Done [1]. The SPARC bot is patiently now for being added as a new worker ;-). > [1] https://reviews.llvm.org/D90148 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
[clang] [clang] LazyOffsetPtr: Use native pointer width (PR #111995)
glaubitz wrote: > cc @glaubitz (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113341) I can confirm that the patch from this PR fixes the GCC bootstrap on 32-bit PowerPC on Linux for me (GCC pr/target 113341). https://github.com/llvm/llvm-project/pull/111995 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
[clang] [clang] LazyOffsetPtr: Use native pointer width (PR #111995)
glaubitz wrote: Btw, if you submit a fix, it would be great if it could be backported to the 18 and 19 branches. https://github.com/llvm/llvm-project/pull/111995 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
[clang] [clang] Make LazyOffsetPtr more portable (PR #112927)
glaubitz wrote: > I appreciate it's not exactly a straightforward change given the discussion > it provoked, but any chance you'd be okay with a backport to 19? Clang isn't > really usable on ppc32 without this. We could pull it in just for ppc32 > downstream but we generally dislike doing conditional patching. WDYT? > > cc @mgorny I agree. It would be great if this fix could be backported. https://github.com/llvm/llvm-project/pull/112927 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
[clang] [Driver][Sparc] Default to -mcpu=v9 for 32-bit Linux/sparc64 (PR #109278)
@@ -125,7 +126,9 @@ std::string sparc::getSparcTargetCPU(const Driver &D, const ArgList &Args, return std::string(CPUName); } - if (Triple.getArch() == llvm::Triple::sparc && Triple.isOSSolaris()) + Distro Dist(D.getVFS(), Triple); + if (Triple.getArch() == llvm::Triple::sparc && + (Triple.isOSSolaris() || Dist.IsDebian() || Dist.IsGentoo())) glaubitz wrote: There is the very popular SPARC Leon CPU that is used by ESA among other important customers and that uses V8 as the baseline. And Linux is supported and actively maintained on Leon. https://github.com/llvm/llvm-project/pull/109278 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
[clang] [Driver][Sparc] Default to -mcpu=v9 for 32-bit Linux/sparc64 (PR #109278)
glaubitz wrote: > Just to be certain: the revised version of the patch is ok to commit? I think it would be good to get an ACK from at least one of the SPARC Leon maintainers. CC @andreas-gaisler https://github.com/llvm/llvm-project/pull/109278 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
