-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Incorrect string-merge results when code is compiled with clang #180
Comments
I cannot see the wrong output, what happens to be is
Do we speak about the same issue? |
Interesting. I still get output even under valgrind:
I just tried running in the OpenSUSE docker image and the test there didn't pass linker-diff validation:
We don't do anything special for |
If I edit the source file test arguments to be:
putting clang instead of gcc, the test fails thus:
Would they be a reproducer for this issue, to allow me to tinker with it and see what the cause it? |
Note this is about changing the linker wrapper that is used and does not influence what compiler is used for .o files creation. Plus, the error you face is caused by the fact you changed C++ wrapper with a C wrapper (instead of Please try this: diff --git a/wild/tests/sources/cpp-integration.cc b/wild/tests/sources/cpp-integration.cc
index ffcbf3c..385790b 100644
--- a/wild/tests/sources/cpp-integration.cc
+++ b/wild/tests/sources/cpp-integration.cc
@@ -16,6 +16,7 @@
//#Config:model-large:default
//#CompArgs:-mcmodel=large
//#LinkArgs:--cc=g++ -Wl,-z,now
+//#Compiler: clang
#include <iostream>
#include <string> |
OK, got it reproducing same output now. Thanks. |
When
program_name_29___cpp_integration_cc__
is compiled withclang
rather thangcc
, it fails. Apparently all the merged strings end up as the stringELF
. See #140. We should probably first add an option to allow overriding the compiler - i.e. #179.The text was updated successfully, but these errors were encountered: