[ 
https://issues.apache.org/jira/browse/DISPATCH-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162992#comment-17162992
 ] 

Jiri Daněk commented on DISPATCH-1712:
--------------------------------------

https://travis-ci.org/github/apache/qpid-dispatch/jobs/710712573

Clang: when LTO is enabled, which PROTON-2208 enabled by default on Clang, it 
is necessary to have `llvm-10-dev` installed. Otherwise, compilation fails with

{noformat}
[ 40%] Linking C shared library libqpid-proton-core.so
/usr/bin/ld: /usr/lib/llvm-10/bin/../lib/LLVMgold.so: error loading plugin: 
/usr/lib/llvm-10/bin/../lib/LLVMgold.so: cannot open shared object file: No 
such file or directory
clang: error: linker command failed with exit code 1 (use -v to see invocation)
{noformat}

> Extend the CI with Ubuntu Focal, Aarch64, and Clang
> ---------------------------------------------------
>
>                 Key: DISPATCH-1712
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1712
>             Project: Qpid Dispatch
>          Issue Type: Test
>          Components: Tests
>    Affects Versions: 1.12.0
>            Reporter: Jiri Daněk
>            Priority: Major
>
> Dispatch is currently running all its CI jobs on Travis CI using Ubuntu 
> Xenial, AMD64, and GCC. It would make sense to me to extend the coverage.
> Ubuntu Focal contains newer versions of software. The CI may find 
> incompatibilities there.
> Aarch64 is weakly-ordered, so it may reveal some concurrency bugs. Travis has 
> it available https://docs.travis-ci.com/user/multi-cpu-architectures/
> Clang may print different diagnostics than gcc, and on aarch64 it supports 
> alternate algorithm for asan, which reports on overlapping but different set 
> of invalid memory accesses than regular asan 
> https://clang.llvm.org/docs/HardwareAssistedAddressSanitizerDesign.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to