-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Make generic CodeGen tests truly generic #1742
Comments
*** This bug has been marked as a duplicate of 556 *** |
This is not a duplicate of 556. bug 556 had to do with the mechanism to detect This bug is about getting tests in the right directory, a wholly different problem. |
Why do we even care about this? People shouldn't be running tests unless they have everything built. |
You're missing the point, Chris. Regardless of the targets they have specified as being built, if they run the BTW, I would expect that most users (not developers) would select to only |
You're confusing many different issues here reid.
There are tests that run multiple different targets. This is by design and not something that should -Chris |
There's no confusion.
So, package managers for operating system distros just "don't count" in your
Huh? The default is to link in every target configured to be built. The entire
The only thing that is changing is that such tests are being replicated so that |
Fine, go for it. |
This has been implemented. Only target-independent test cases should go in |
mentioned in issue #928 |
…5747430d6bced66b2c5ada [lldb] XFAIL TestMemoryHistory on Linux
Extended Description
The DejaGnu tests will now avoid running tests for targets that are not
configured. Unfortunately, the Generic test suite contains test cases for
specific targets. This causes false FAIL in test/CodeGen/Generic because the
target specific options are not supported by llc. For example, the -march=ppc32
option is not supported in a test case if PowerPC is not configured to be built.
This should be rectified by moving or copying the tests that use the -march
option from Generic to the appropriate target directories.
The text was updated successfully, but these errors were encountered: