Date: Tue, 13 May 2014 07:58:25 -0600 From: Warner Losh <imp@bsdimp.com> To: Dimitry Andric <dim@freebsd.org> Cc: FreeBSD ARM <freebsd-arm@FreeBSD.org>, Ian Lepore <ian@freebsd.org> Subject: Re: 11-CURRENT: clang/error: no member named 'VLD1d64TPseudoWB_fixed' in namespace 'llvm::ARM' Message-ID: <30ED030F-69E3-4E27-B492-3CBE30356DDE@bsdimp.com> In-Reply-To: <6F8FBC17-D8BF-4B78-A6E1-6FFEFCC14838@FreeBSD.org> References: <CADH-AwEoV90ZOk9gyAK6Jy1Y_OyDbWYB0njmYB2n%2BJ87=uFBmQ@mail.gmail.com> <1399946503.50937.9.camel@revolution.hippie.lan> <6F8FBC17-D8BF-4B78-A6E1-6FFEFCC14838@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On May 12, 2014, at 11:38 PM, Dimitry Andric <dim@freebsd.org> wrote: > On 13 May 2014, at 04:01, Ian Lepore <ian@freebsd.org> wrote: >> On Mon, 2014-05-12 at 21:51 -0400, Winston Smith wrote: >>> Cross compiling the tools for 11-CURRENT at r265941 yields: >>> >>> >>> /usr/src/FreeBSD-CURRENT/lib/clang/libllvmarmcodegen/../../../contrib/llvm/lib/Target/ARM/ARMBaseInstrInfo.cpp:3687:15: >>> error: >>> no member named 'VLD1d64TPseudoWB_fixed' in namespace 'llvm::ARM'; did you >>> mean 'VST1d64TPseudoWB_fixed'? >>> case ARM::VLD1d64TPseudoWB_fixed: >>> ~~~~~^~~~~~~~~~~~~~~~~~~~~~ >>> VST1d64TPseudoWB_fixed >>> ./ARMGenInstrInfo.inc.h:1969:5: note: 'VST1d64TPseudoWB_fixed' declared here >>> VST1d64TPseudoWB_fixed = 1953, >>> ^ >>> /usr/src/FreeBSD-CURRENT/lib/clang/libllvmarmcodegen/../../../contrib/llvm/lib/Target/ARM/ARMBaseInstrInfo.cpp:3704:15: >>> error: >>> no member named 'VLD1d64QPseudoWB_fixed' in namespace 'llvm::ARM'; did you >>> mean 'VST1d64QPseudoWB_fixed'? >>> case ARM::VLD1d64QPseudoWB_fixed: >>> ~~~~~^~~~~~~~~~~~~~~~~~~~~~ >>> VST1d64QPseudoWB_fixed >>> ./ARMGenInstrInfo.inc.h:1963:5: note: 'VST1d64QPseudoWB_fixed' declared here >>> VST1d64QPseudoWB_fixed = 1947, >>> ^ >>> 2 errors generated. >>> *** Error code 1 >> >> I suspect r265925 is a good suspect and reverting it will probably get >> you moving again for now. >> >> Dimitry, was there maybe an updated header file missing from this >> import? > > I don't think so, I built universe succesfully. I suspect that some of > the tblgen-generated headers are out of date, and must be regenerated. > Unfortunately, the dependency checking for these generated files does > not always pick up changes. > > Probably the easiest way to fix this is to blow away your /usr/obj, and > do a clean build. Any plans on fixing that problem with the build? Having stuff randomly fail really isn’t the FreeBSD way.[*] Warner [*] Yes, I know that there’s at least one bug still with my build refactor, but I plan on fixing that during BSDcan. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTciUBAAoJEGwc0Sh9sBEAp6YP/3G3oJERkousPvRA+Gv2Ac9w MrnZEyGuEQXSpof8Bm+dFCmFJytS3EMRyv/B4b1l6oUMFP6jG+zgTT4lQooAbhIp emUDEfe67gBV3XLPhEdFH4rXNHNvdx4d69r/J5KMlGcAoWpS/gOwj4L1J0J1JR/n 5cHiqj5e1mDFHMwvDjjOEG5YqrLhvZynmB7TRCLNi6oKkwosyJLRkaIzt182crg9 eY3wDN84ssU/nZV0NzBtTg+UELcehUMkmV/lo0O65DASjXn04gIz/tCBSt9IVsSd cOAc2HwJoST2DkzbYCcFMt+spi9EG1C2btultF4k0en8w/SPse2BxEuCFTFO0ady Iu5jV8swwowG4MgSaOIO+fsm4LT8X9CDnZ7y/wvTqFB0o65C0VtpwMOen6DLfdbu Vv4EkB9i+flEJpUKEoZOEfud+ifTyT+2vKbn4DYKyBS/LSt9YoypUI4tjU32SFQi 5eE3WXNMXca1FOMYC3KtQ/C05nC6g1gYj9oz1jnLGuBrfayDZ8bkUFlZyMVuQ0kk klKQ3BLLzRQ7ohZypuGP8+u+/CPTcqZcv+bGSfzyg74gBKHKXK0IOoGWwUC6gk47 QxoUp6FT2/l4bnza5cmoPiDXcykaoUurU4vWq+SilA1QNxlmkyH+gbW/L3nMK7wF sPLmuR7kTH2qHVEm0BIf =FBUy -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?30ED030F-69E3-4E27-B492-3CBE30356DDE>