mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Fangrui Song <i@maskray.me>
To: musl@lists.openwall.com
Cc: "Aodhnait Étaín" <aodhneine@protonmail.ch>
Subject: Re: [musl] Clang 10 errors during compiling musl 1.2.2
Date: Sat, 24 Apr 2021 14:07:53 -0700	[thread overview]
Message-ID: <20210424210753.tsfhaupqtvxztde6@gmail.com> (raw)
In-Reply-To: <20210424195041.GT2546@brightrain.aerifal.cx>

On 2021-04-24, Rich Felker wrote:
>On Sat, Apr 24, 2021 at 07:03:20PM +0000, Aodhnait Étaín wrote:
>> Hi,
>>
>> I tried to cross-compile musl 1.2.2 for RISC-V using clang 10 on Alpine
>> Linux in WSL. Sadly, it did not work, and instead failed during compiling
>> src/complex/catan.c.
>>
>> Linked below are output of configure and make, the preprocessed source
>> of catan.c and the run script.
>>
>> Compilation log: http://0x0.st/-mux.log
>> Preprocessed source: http://0x0.st/-mu3.c
>> Associated run script: http://0x0.st/-muY.sh
>>
>> I guess it has something to do with clang, so probably llvm-bugs would
>> be a more appropriate place to report it, but I'm still waiting for the
>> account registration confirmation on the llmv-project Bugzilla. So in
>> the meantime I decided to see if you peeps have any idea what's happening?
>
>Yes, this is surely a clang bug. But maybe someone here will have
>ideas about getting it fixed or know if it's already reported.
>
>Rich

I confirm clang 10.0.1 has the bug when compiling src/complex/catan.c. clang 11.0.0 from https://releases.llvm.org/ is good.

If your GCC installation is riscv64-linux-gnu-gcc, I recommend --target=riscv64-linux-gnu- or --target=riscv64-linux-gnu,
which matches the gcc executable name. --target=riscv64 is not recommended.

      reply	other threads:[~2021-04-24 21:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-24 19:03 Aodhnait Étaín
2021-04-24 19:50 ` Rich Felker
2021-04-24 21:07   ` Fangrui Song [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210424210753.tsfhaupqtvxztde6@gmail.com \
    --to=i@maskray.me \
    --cc=aodhneine@protonmail.ch \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).