These kinds of crashes typically happen when you have something like a use-after-destroy of a temporary, like a misuse of Twine or std::initializer_list.
On Thu, Oct 13, 2016 at 3:47 PM, Arnold Schwaighofer via cfe-commits < cfe-commits@lists.llvm.org> wrote: > Author: arnolds > Date: Thu Oct 13 17:47:03 2016 > New Revision: 284174 > > URL: http://llvm.org/viewvc/llvm-project?rev=284174&view=rev > Log: > Disable swiftcall test on windows: More brutal way to appease windows bots > > The backtrace on the bot does not give me any indication what is wrong. > The test case interestingly passes in stage2 of the build. > I don't have a way of debugging this. > > Disable the test on windows and hope if there is truly a bug in the code > that > was causing we will eventually run into this on other platforms. > > Modified: > cfe/trunk/test/CodeGen/64bit-swiftcall.c > > Modified: cfe/trunk/test/CodeGen/64bit-swiftcall.c > URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/test/ > CodeGen/64bit-swiftcall.c?rev=284174&r1=284173&r2=284174&view=diff > ============================================================ > ================== > --- cfe/trunk/test/CodeGen/64bit-swiftcall.c (original) > +++ cfe/trunk/test/CodeGen/64bit-swiftcall.c Thu Oct 13 17:47:03 2016 > @@ -3,6 +3,9 @@ > > // REQUIRES: aarch64-registered-target,x86-registered-target > > +// The union_het_vecint test case crashes on windows bot but only in > stage1 and not in stage2. > +// UNSUPPORTED: system-windows > + > #define SWIFTCALL __attribute__((swiftcall)) > #define OUT __attribute__((swift_indirect_result)) > #define ERROR __attribute__((swift_error_result)) > > > _______________________________________________ > cfe-commits mailing list > cfe-commits@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits >
_______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
