On Mon, Mar 06, 2017 at 10:17:36PM +0000, Ramsay Jones wrote: > Hi Luc, Christopher, Hi, > ... > > So, this looks like a cygwin specific toolchain problem. I also assumed that > the 'backend/loop.c' test had the same problem (but I admit to never having > checked properly!). > > ... > > So, again, this seems like a cygwin specific llvm tool problem. > > ... > > TEST Loops (backend/loop.c) > error: actual error text does not match expected error text. > error: see backend/loop.c.error.* for further investigation. > --- backend/loop.c.error.expected 2017-03-06 21:57:27.695953300 +0000 > +++ backend/loop.c.error.got 2017-03-06 21:57:30.636386100 +0000 > @@ -0,0 +1,2 @@ > +assertion "ctype" failed: file "sparse-llvm.c", line 312, function: val_to_value > +.././sparsec: line 35: 8900 Aborted (core dumped) $DIRNAME/sparse-llvm $SPARSEOPTS > $TMPLLVM That's surprising as it appears that you have linearized code that is different that what we have on Linux (one of the type/symbol is NULL). It whould be very interesting to: 1) show the result of test-linearize on the file 2) replace the assert with a check followed with a dump of the offending pseudo (show_pseudo()) and ideally the corresponding instruction (show_instruction()). > Note that 'backend/loop2.c' now also fails and, with the exception of > the 'backend/hello.c' test, they now fail with an assert. Odd. > I don't have time to look into this further tonight (I'm guessing that > you are not seeing this on linux), so I just wanted to let you know > about it. > > ATB, > Ramsay Jones No, nothing like that on Linux. Dibyendu, are you seeing something like this on your environment? Thanks to reporting this, alas as such I can't really do something about it. -- Luc Van Ooostenryck -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
