-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
take test cases from libiberty #16
Comments
Why wouldn't it matter? |
My belief is that the "mere aggregation" clause permits the bundling of a GPL test case with an otherwise non-GPLd library. |
Ok, I'll take your word on that ;) |
Initial test import, not yet passing, in #43 |
Current log of failing tests:
|
FYI LLVM has a large set of demangler test cases in https://github.com/llvm-mirror/libcxxabi/blob/master/test/test_demangle.pass.cpp |
Be sure to update this file occasionally -- some demangler bug fixes and new tests recently landed in libiberty. |
Totally, although my priority right now is getting all the existing tests we've already imported passing :) |
Libiberty contains a good set of demangler test cases, including various manglings that have crashed the libiberty demangler. (There are still some other known crashers in gcc and gdb bugzilla though; and also at one point Gary Benson had a fuzzer...)
You can see the libiberty tests here:
https://gcc.gnu.org/viewcvs/gcc/trunk/libiberty/testsuite/
You want
demangle-expected
but there are also tests for Rust that might be interesting.Ian's demangler in Go (https://github.com/ianlancetaylor/demangle) uses this test suite as well, though it seems to be a bit behind libiberty master.
The tests are presumably GPL (no explicit license there, but in ancient times I extracted them from the gdb test suite into this file), but I think that shouldn't matter.
The text was updated successfully, but these errors were encountered: