-
Notifications
You must be signed in to change notification settings - Fork 198
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
Consider move TUNE_CCARGS:remove = "-mbranch-protection=standard"
to conf file
#998
Comments
#963 reported this issue and fixing C++ runtime was enough to solve that case. However if you are seeing more issues with it then we might want to use it globally infact for all the distros using clang + gcc to build packages will show similar issue on arm64. Can you add a package where this happens and removing it helps ? |
Here is an example vsomip. You can see that Boost is used to load the configuration file with 'try-catch'. Sure I can remove |
I am seeing the same in my distro. We had to revert again foundriesio/meta-lmp#1500 and apply our fix globally
|
#999 doesn't work, I tried ... :( |
I was hoping it would work, this way it becomes more difficult and perhaps applying the ' |
I have finished my tests and unfortnly the #999 doesn't fix the runtimes exceptions. |
On aarch64 the handling of runtime exception is broken when build with clang. There is currently a fix for libcxx on the layer but it is not enough and this same fix needs to be applied globally. First fix attempt just include libcxx: kraj#963 kraj#968 Remaining reported issue: kraj#998 Signed-off-by: Jose Quaresma <[email protected]>
On aarch64 the handling of runtime exception is broken when build with clang. There is currently a fix for libcxx on the layer but it is not enough and this same fix needs to be applied globally. First fix attempt just include libcxx: kraj#963 kraj#968 Remaining reported issue: kraj#998 Signed-off-by: Jose Quaresma <[email protected]>
On aarch64 the handling of runtime exception is broken when build with clang. There is currently a fix for libcxx on the layer but it is not enough and this same fix needs to be applied globally. First fix attempt just include libcxx: kraj#963 kraj#968 Remaining reported issue: kraj#998 Signed-off-by: Jose Quaresma <[email protected]>
On aarch64 the handling of runtime exception is broken when build with clang. There is currently a fix for libcxx on the layer but it is not enough and this same fix needs to be applied globally. First fix attempt just include libcxx: #963 #968 Remaining reported issue: #998 Signed-off-by: Jose Quaresma <[email protected]>
On aarch64 the handling of runtime exception is broken when build with clang. There is currently a fix for libcxx on the layer but it is not enough and this same fix needs to be applied globally. First fix attempt just include libcxx: kraj#963 kraj#968 Remaining reported issue: kraj#998 Signed-off-by: Jose Quaresma <[email protected]> (cherry picked from commit ee30860) Signed-off-by: Jose Quaresma <[email protected]>
On aarch64 the handling of runtime exception is broken when build with clang. There is currently a fix for libcxx on the layer but it is not enough and this same fix needs to be applied globally. First fix attempt just include libcxx: kraj#963 kraj#968 Remaining reported issue: kraj#998 Signed-off-by: Jose Quaresma <[email protected]> (cherry picked from commit ee30860) Signed-off-by: Jose Quaresma <[email protected]>
fixed with #1000 |
On aarch64 the handling of runtime exception is broken when build with clang. There is currently a fix for libcxx on the layer but it is not enough and this same fix needs to be applied globally. First fix attempt just include libcxx: #963 #968 Remaining reported issue: #998 Signed-off-by: Jose Quaresma <[email protected]> (cherry picked from commit ee30860) Signed-off-by: Jose Quaresma <[email protected]>
On aarch64 the handling of runtime exception is broken when build with clang. There is currently a fix for libcxx on the layer but it is not enough and this same fix needs to be applied globally. First fix attempt just include libcxx: #963 #968 Remaining reported issue: #998 Signed-off-by: Jose Quaresma <[email protected]> (cherry picked from commit ee30860) Signed-off-by: Jose Quaresma <[email protected]>
Source: meta-clang MR: 158405 Type: Integration Disposition: Merged from meta-clang ChangeID: bff7fe1 Description: On aarch64 the handling of runtime exception is broken when build with clang. There is currently a fix for libcxx on the layer but it is not enough and this same fix needs to be applied globally. First fix attempt just include libcxx: kraj/meta-clang#963 kraj/meta-clang#968 Remaining reported issue: kraj/meta-clang#998 Signed-off-by: Jose Quaresma <[email protected]> (cherry picked from commit ee30860) Signed-off-by: Jose Quaresma <[email protected]> Signed-off-by: Jeremy A. Puhlman <[email protected]>
Source: meta-clang MR: 158188 Type: Integration Disposition: Merged from meta-clang ChangeID: 318e671 Description: On aarch64 the handling of runtime exception is broken when build with clang. There is currently a fix for libcxx on the layer but it is not enough and this same fix needs to be applied globally. First fix attempt just include libcxx: kraj/meta-clang#963 kraj/meta-clang#968 Remaining reported issue: kraj/meta-clang#998 Signed-off-by: Jose Quaresma <[email protected]> (cherry picked from commit ee30860) Signed-off-by: Jose Quaresma <[email protected]> Signed-off-by: Jeremy A. Puhlman <[email protected]>
Hi, why not place the changes to TUNE_CCARGS in the conf file?
This change should affect the global CFLAGS. If it's only set in
libcxx_git.bb
, other packages won’t be affected.I found that when building other packages, the cxx exception feature doesn’t work properly on aarch64.
It only works if
TUNE_CCARGS:remove:toolchain-clang = "${@bb.utils.contains('TUNE_FEATURES', 'aarch64', '-mbranch-protection=standard', '', d)}"
is added globally.
The text was updated successfully, but these errors were encountered: