From: Lei Zhang <zhanglei.april@gmail.com>
To: Luca Barbato <lu_zero@gentoo.org>
Cc: soc-admins@gentoo.org, gentoo-musl@lists.gentoo.org
Subject: [gentoo-musl] Re: [GSoC] native-clang: daily report 06/29
Date: Thu, 30 Jun 2016 23:40:33 +0800 [thread overview]
Message-ID: <CAOYuCc2AG7bOpVjUV_BdOZjehn51SdaPT4AAzKb5SxRnyLhkQw@mail.gmail.com> (raw)
In-Reply-To: <6ebcb95d-409a-cbb1-6980-cf8688901164@gentoo.org>
2016-06-30 15:48 GMT+08:00 Luca Barbato <lu_zero@gentoo.org>:
> On 29/06/16 17:52, Lei Zhang wrote:
>> Plan for today:
>> - investigate clang's poor performance
>> - study catalyst and stuff
>>
>> Progress:
>> - I find out that optimization flags are not correctly passed to
>> compiler when building the freestanding clang. The cause is a bit
>> complicated:
>>
>> clang has to be built in-tree (i.e. along with LLVM); compiler-rt can
>> be built out-of-tree, but it's a little inconvenient so I also built
>> it in-tree. This means clang, compiler-rt and LLVM are built
>> all-together. compiler-rt's sanitizer has some issue with musl, so I
>> disabled building the sanitizer via some option. It turns out this
>> option somehow leads cmake to forget passing optimization flags to
>> compiler. The solution is simple: build compiler-rt out-of-tree. Or I
>> can resolve the issue between compiler-rt's sanitizer and musl, when
>> I've got time...
>
> Sounds a good plan =)
I just found that compiler-rt is built as part of clang/LLVM in the
default ebuilds. Perhaps I should leave it that way: not to create a
new package for compiler-rt. That means compiler-rt still needs to be
built in-tree, and I'll have to deal with the optimization flag issue.
I also noticed that gcc's sanitizer doesn't work on the musl based
system, so is it forgivable to not support clang's sanitizer either?
(clang's sanitizer is implemented in compiler-rt)
Lei
next prev parent reply other threads:[~2016-06-30 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 15:52 [gentoo-musl] [GSoC] native-clang: daily report 06/29 Lei Zhang
2016-06-30 8:59 ` Jens Staal
2016-06-30 9:24 ` Lei Zhang
[not found] ` <6ebcb95d-409a-cbb1-6980-cf8688901164@gentoo.org>
2016-06-30 15:40 ` Lei Zhang [this message]
[not found] ` <8f6ced62-ed80-fc11-346c-fd72b1a1b3e6@gentoo.org>
2016-07-01 1:58 ` [gentoo-musl] " Lei Zhang
2016-07-01 5:01 ` Felix Janda
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=CAOYuCc2AG7bOpVjUV_BdOZjehn51SdaPT4AAzKb5SxRnyLhkQw@mail.gmail.com \
--to=zhanglei.april@gmail.com \
--cc=gentoo-musl@lists.gentoo.org \
--cc=lu_zero@gentoo.org \
--cc=soc-admins@gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox