Hi LLVMdev, My recent commit r186623 caused buildbots for s390-linux and ppc64-linux to fail. I rolled back that commit, and I'm trying to fix to re-submit. Is there any good way to debug the issue which does not occur on my local x86-64 machine? I don't have S390 nor PPC64 machines. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130718/cb546103/attachment.html>
On Thu, Jul 18, 2013 at 4:29 PM, Rui Ueyama <ruiu at google.com> wrote:> Hi LLVMdev, > > My recent commit r186623 caused buildbots for s390-linux and ppc64-linux to > fail. I rolled back that commit, and I'm trying to fix to re-submit. > > Is there any good way to debug the issue which does not occur on my local > x86-64 machine? I don't have S390 nor PPC64 machines.If it's failing on S390 and PPC64 in particular, your code probably accidentally depends on the host endianness. (Looking at the commit in question seems to confirm that.) -Eli
Yes, it's very likely. It'd be very convenient if we could send a patch to buildbots for testing without actually submitting. On Thu, Jul 18, 2013 at 4:38 PM, Eli Friedman <eli.friedman at gmail.com>wrote:> On Thu, Jul 18, 2013 at 4:29 PM, Rui Ueyama <ruiu at google.com> wrote: > > Hi LLVMdev, > > > > My recent commit r186623 caused buildbots for s390-linux and ppc64-linux > to > > fail. I rolled back that commit, and I'm trying to fix to re-submit. > > > > Is there any good way to debug the issue which does not occur on my local > > x86-64 machine? I don't have S390 nor PPC64 machines. > > If it's failing on S390 and PPC64 in particular, your code probably > accidentally depends on the host endianness. (Looking at the commit > in question seems to confirm that.) > > -Eli >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130718/55b4f666/attachment.html>