[llvm-dev] Linux/ARM: Segfault issue when we build clang sources including __thread variable using -O2 flag

Geunsik Lim via llvm-commits llvm-commits at lists.llvm.org
Tue May 17 22:20:54 PDT 2016


> Maybe the build system is suppressing stdout for some reason?
I think that the build system does not suppress stdout at build-time if I
append "verbose" option.
So, I am analyzing the build process of CoreCLR  to know why we can not see
the 'std::cout' message while compiling
CoreCLR with clang/llvm(including your patch)



On Wed, May 18, 2016 at 12:09 PM, Tim Northover <t.p.northover at gmail.com>
wrote:

> On 17 May 2016 at 19:22, Geunsik Lim <leemgs at gmail.com> wrote:
> > It's strange. I could not see the "[DEBUG] ****" message while compiling
> > CoreCLR  with Clang/LLVM for Linux/ARM. Is it right? Can you give me an
> > opinion?
>
> That strongly suggests something is wrong. That function ought to be
> called hundreds of times while building the source, regardless of the
> changed outcome after my patch. Maybe the build system is suppressing
> stdout for some reason?
>
> I'd be happy to look at the various clsload.cpp.o files produced
> (there is more than 1 and I can't actually remember which had the
> problem I'm afraid) and tell you if the TLS accesses are sane.
>
> Cheers.
>
> Tim.
>



-- 
http://leemgs.fedorapeople.org
Don't try to avoid pain if you fail.
If you decided to face the challenges in life,
you can gain a lot by giving your best.
Cheolsang Jeong's Book & life
--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20160518/2014291c/attachment.html>


More information about the llvm-commits mailing list