Thanks a lot, Ian, I can build it with clang now with a few minor changes. On Tuesday, July 16, 2019 at 5:40:24 AM UTC+8, Ian Lance Taylor wrote: > > On Mon, Jul 15, 2019 at 7:39 AM Xiangdong Ji <xiang...@gmail.com > <javascript:>> wrote: > > > > I am trying to build gollvm on ARM with a few experimental changes, > looks like some ARM Neon intrinsics in > > libgo/runtime/aeshash.c are not supported by GCC 7/8, wondering if it > could be solved by any additional compile > > options, or should the latest gcc-9 or clang be used? > > The arm64 support in aeshash.c was added in GCC 9. In general there > is no expectation that the files in GCC 9 can be compiled by earlier > versions of GCC. Many times it will work, but not always, and this > may be a case where it fails (I haven't checked). It's not feasible > for us to ensure that files distributed with GCC 9 can be compiled by > earlier versions of GCC. > > In any case, if your goal is to build GoLLVM, then you should be > compiling this file with clang. And it sounds like you can do that. > So there doesn't seem to be much reason to compile it with GCC. I > understand that you are having trouble building GoLLVM, but it's not > clear to me why building this file with GCC rather than clang will > help with that. > > Ian >
-- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/acc6b2b7-4998-4059-aa75-bc5cf7c5fc8e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
