On 18/2/22 16:36, Paolo Bonzini wrote:
On 2/18/22 02:46, Richard Henderson wrote:
I don't have gobjc/g++ installed, so ./configure defaulted to Clang to
compile these languages, but compiled C files using GCC. At the end
the
Clang linker is used (the default c++ symlink).
This is another
On 2/15/22 18:01, Philippe Mathieu-Daudé via wrote:
+
+case "$cpu" in
+ aarch64)
+write_c_skeleton;
+if compile_prog "$CPU_CFLAGS -Werror -mno-outline-atomics" "" ; then
+ CPU_CFLAGS="-mno-outline-atomics $CPU_CFLAGS"
+fi
+;;
Apart from the question of whether/how to work
On 2/18/22 02:46, Richard Henderson wrote:
I don't have gobjc/g++ installed, so ./configure defaulted to Clang to
compile these languages, but compiled C files using GCC. At the end the
Clang linker is used (the default c++ symlink).
This is another form of compiler mis-configuration.
If you
On 2/17/22 04:18, Philippe Mathieu-Daudé wrote:
On 16/2/22 17:42, Akihiko Odaki wrote:
On 2022/02/17 0:08, Philippe Mathieu-Daudé wrote:
On 16/2/22 11:19, Richard Henderson wrote:
These should have been supplied by libgcc.a, which we're supposed to be linking
against. Something is wrong with
On Wed, 16 Feb 2022 at 17:18, Philippe Mathieu-Daudé wrote:
> Thanks for the pointer. And the next section is
> https://clang.llvm.org/docs/Toolchain.html#atomics-library :)
>
>Clang does not currently automatically link against libatomic when
> using libgcc_s. You may need to manually
On 16/2/22 17:42, Akihiko Odaki wrote:
On 2022/02/17 0:08, Philippe Mathieu-Daudé wrote:
On 16/2/22 11:19, Richard Henderson wrote:
On 2/16/22 04:01, Philippe Mathieu-Daudé via wrote:
GCC 10.1 introduced the -moutline-atomics option on Aarch64.
This options is enabled by default, and triggers
On 2022/02/17 0:08, Philippe Mathieu-Daudé wrote:
On 16/2/22 11:19, Richard Henderson wrote:
On 2/16/22 04:01, Philippe Mathieu-Daudé via wrote:
GCC 10.1 introduced the -moutline-atomics option on Aarch64.
This options is enabled by default, and triggers a link failure:
Undefined symbols
On 16/2/22 11:19, Richard Henderson wrote:
On 2/16/22 04:01, Philippe Mathieu-Daudé via wrote:
GCC 10.1 introduced the -moutline-atomics option on Aarch64.
This options is enabled by default, and triggers a link failure:
Undefined symbols for architecture arm64:
On 2/16/22 04:01, Philippe Mathieu-Daudé via wrote:
GCC 10.1 introduced the -moutline-atomics option on Aarch64.
This options is enabled by default, and triggers a link failure:
Undefined symbols for architecture arm64:
"___aarch64_cas1_acq_rel", referenced from:
On Wed, Feb 16, 2022 at 2:01 AM Philippe Mathieu-Daudé wrote:
>
> GCC 10.1 introduced the -moutline-atomics option on Aarch64.
> This options is enabled by default, and triggers a link failure:
>
> Undefined symbols for architecture arm64:
> "___aarch64_cas1_acq_rel", referenced from:
>
GCC 10.1 introduced the -moutline-atomics option on Aarch64.
This options is enabled by default, and triggers a link failure:
Undefined symbols for architecture arm64:
"___aarch64_cas1_acq_rel", referenced from:
_qmp_migrate_recover in migration_migration.c.o
11 matches
Mail list logo
