User Details
- User Since
- Jul 10 2015, 3:44 PM (370 w, 4 d)
Sun, Aug 14
I have tested this revision and it fixes the problem I was seeing
Fri, Aug 12
I am getting a compiler error on clang-15, can you confirm if this will work with clang-15 too
Mar 25 2022
I built this on top if 14.x branch and it fixes the problems, I was seeing and the warning is still emitted as expected.
I have submitted a github issue which seems to be related here https://github.com/llvm/llvm-project/issues/54456
Mar 10 2022
rebased
@MaskRay can you help in moving this forward ?
rebased
@peter.smith Can you help landing this changeset ? there has been no objections on it thus far.
Feb 11 2022
Feb 7 2022
I tested this patch and it fixes lldb build. Thanks for taking care of this,.
Aug 28 2021
I verified both patches together on latest 13.x branch and it fixes the issue I was seeing. So please apply both the fixes suggested in description to 13.x branch.
Aug 27 2021
This breaks a case where opt is used from installed locations especially in standalone cross-build environment we pass -DOPT_TOOL=${STAGING_BINDIR_NATIVE}/opt and it worked ok but now its expecting opt to be built along with openmp build and fails like below
Jun 23 2021
https://reviews.llvm.org/D104788 fixes it as well.
Jun 15 2021
Jun 14 2021
Jun 12 2021
ping,
Jun 3 2021
http://sprunge.us/FJzZXL is a file from harfbuzz and it warns
May 21 2021
May 20 2021
May 17 2021
LGTM
May 14 2021
Mar 25 2021
@MaskRay I dont find this in main branch yet, anything pending on me ?
Mar 24 2021
once you fix the clang-format issue reported this looks good to me.
@MaskRay how should be proceeed here
0073c293a401774ac96b4b3d27f05e13f379f98e has fixed it.
Can someone review this please?
this is because warning were disabled during cmake tests
it works with python3 too, perhaps it would be good to ask for python3 instead
Feb 25 2021
Feb 8 2021
I am still seeing build failures in NATIVE/llvm-config when I am cross building clang for say aarch64 on a x86_64 host. Even when I specify -DLLVM_ENABLE_TERMINFO=OFF, it still goes and pokes for these ncurses libs on build host and adds them to linker cmd. Since my target rootfs is set to not have these libs the final link fails to find -lterminfo rightly. Surprisingly, non NATIVE parts work ok and seem to respect LLVM_ENABLE_TERMINFO settings. Any insights ?
Feb 6 2021
Feb 4 2021
Can we get this on clang 12 release branch as well ?
Nov 17 2020
Nov 16 2020
it should have been after including syscall.h
Nov 14 2020
Add comments in source
this revision is not riscv32 specific. Let me know if this is ok
Aug 3 2020
Aug 2 2020
Fix formatting errors
Jan 7 2020
Jan 3 2020
this is now in master, and I am seeing build failures in cross-building clang, e.g. when building clang for arm on a x86_64 host. its resorting to finding, libz from buildhost instead of target sysroot ( using --sysroot) and failing in link step. e.g.
Dec 28 2019
Dec 11 2019
Dec 10 2019
LGTM now. I am testing it in yocto multilib SDK builds.
Dec 4 2019
Nov 25 2019
@AndreyChurbanov Can you push/commit this patch as well. As I dont have commit privs.
Nov 23 2019
Oct 7 2019
Oct 5 2019
@rengolin who can help committing this patch ?
Sep 12 2019
somehow when doing stage2 build, it is stubborn and does not respect any of PYTHON_EXECUTABLE. PYTHON_LIBRARY or PYTHON_INCLUDE_DIR that were passed with -D on cmake invocation even after they are added to -DDCLANG_BOOTSTRAP_PASSTHROUGH list. llvm finds its own python during stage2. in stage1 it respects the above settings.
Sep 9 2019
Sep 8 2019
one issue I now see is that when we have some thing like
Can we bring this to 9.x release branch as well please ?
Aug 4 2019
Aug 1 2019
Feb 15 2019
Jan 31 2019
Aug 26 2018
Can someone with commit access push this for me please ?
May 20 2018
Can this be backported to release_60 branch too please ?
May 15 2018
May 12 2018
Apr 21 2018
Aug 16 2017
This version works across all compilers.
Aug 2 2017
@EricWF yes please. I don't have push privileges.
Jul 31 2017
There is a proposed fix for glibc's assert here