similar to: Targetting Tricore in LLVM toolchain

Hi Devs, I am planning to start working on Tricore backend in LLVM Toolchain with the hope of upstreaming it. This particular mail is about enquiring whether someone is already doing this job or not. If someone already started work, I would also like to contribute/help to complete it soon. thank you ./kamlesh

Who maintains apt.llvm.org? On 11/27/18 9:25 AM, Andrew Kelley wrote: > ---------- Forwarded message --------- > From: Andrew Kelley <superjoe30 at gmail.com> > Date: Mon, Nov 26, 2018 at 10:38 AM > Subject: apt.llvm.org has the wrong binaries/headers for llvm-toolchain-xenial-7 > To: LLVM Dev <llvm-dev at lists.llvm.org> > > > This build worked on Nov 24 and

It appears that there was an out-of-band patch from Samuel Thibault: https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/blob/7/debian/patches/D54378-hurd-triple.diff Although the patch was approved here https://reviews.llvm.org/D54378 Is this patch going to land in 7.0.1 or 8? kristopher > Here's further proof: > > wget >

Hi Lei, > On Jun 20, 2015, at 11:21 AM, Lei Yang <yltt1234512 at gmail.com> wrote: I am sorry it has taken me so long to test this workflow. > Hi, > > Kunaal and I have completed a prototype of the first part of our GSoC project (implement a new doc toolchain). Our goal is to implement a doc toolchain for short how-to docs and lower the barrier for new comers to contribute.

On Thu, Jul 09, 2015 at 02:11:26AM +0530, kunaal jain wrote: > On Thu, Jul 9, 2015 at 1:19 AM, Brian (bex) Exelbierd <bex at pobox.com> > They have both a private git (with gerrit) and a github repo.A If you > open a PR on github it is closed by a bot with instructions to submit > the PR via gerrit to their private repo.A When the PR is resolved and >

On 4 August 2015 at 14:21, kunaal jain <kunaalus at gmail.com> wrote: > Hi, > > The basic toolchain is up and running. I encourage community to test > this workflow once. It is an addition to the existing contributing > mediums. > > Site: http://clown-olga-13325.bitballoon.com/ > Contributing Docs repo : https://github.com/kunaaljain/test-centos-docs > > ==AIM==

Hi LLVM developers, As PR35281 mentioned: $ llvm-objcopy -O binary llvm-cortex-m7.elf llvm-cortex-m7.bin llvm-objcopy: 'llvm-cortex-m7.elf': The file was not recognized as a valid object file. if (ELFObjectFile<ELF64LE> *o = dyn_cast<ELFObjectFile<ELF64LE>>(&Binary)) https://github.com/llvm-mirror/llvm/blob/master/tools/llvm-objcopy/llvm-objcopy.cpp#L200

Hi! Kunaal and I had an IRC chat last Wednesday at UTC 0600. We discussed about the new docs toolchain. The first part of the chat log is about the workflow, here is the summary: 1. user write on local text editor / on github or a web based editor 2. the PR is created on github, and the info is synced to a reviewing platform, where staff discussed about, tag and accept the file 3. if the PR is

On 17/05/16 18:07, Tim Northover wrote: > Yes, it looks like we'd need to conditionally compile these functions > in ARM mode and use the v6 barrier instead of dmb ("mcr p15, #0, r0, > c7, c10, #5" I believe) to support the ARM1176JZF-S in RPi. You'd > probably also want the build system to use an explicit -march=armv6 or > something so you're not at the mercy

On Thu, Jul 9, 2015 at 1:19 AM, Brian (bex) Exelbierd <bex at pobox.com> wrote: > Hi Lei, > > Hi, I am Kunaal the other GSoC student working on this toolchain. > On Jun 20, 2015, at 11:21 AM, Lei Yang <yltt1234512 at gmail.com> wrote: > > > I am sorry it has taken me so long to test this workflow. > Thanks a lot! We need testers and input from community.

Hi, Kunaal and I have completed a prototype of the first part of our GSoC project (implement a new doc toolchain). Our goal is to implement a doc toolchain for short how-to docs and lower the barrier for new comers to contribute. This is the workflow of the prototype: 1. Contributor creates a new pull request on GitHub 2. A corresponding issue is automatically created on Pagure 3. Staff and

On 17/05/16 22:38, Tim Northover wrote: > Compiler-rt is the equivalent of libgcc, and Clang can use the > existing host's libgcc quite happily so it's really not that important > unless you're trying to build a GNU-free environment for whatever > reason. > Thanks Can you tell me how I would go about telling the cmake buildsystem (which is what the Debian packaging

Hello Dear Team, I wanted to know in which version of LLVM Tricore architecture is supported. I have LLVM 2.8 with me which has no support for Tricore. Basically I wanted to add Aurix target support. Could you please help me. Best Regards / Mit freundlichen Grüßen Minal Kulkarni Knorr Bremse Technology Center India Survey No.276, Village Mann, Hinjewadi, Phase II, Tal.Mulshi, Pune - 411

Hi, The basic toolchain is up and running. I encourage community to test this workflow once. It is an addition to the existing contributing mediums. Site: http://clown-olga-13325.bitballoon.com/ Contributing Docs repo : https://github.com/kunaaljain/test-centos-docs ==AIM== Initial Idea : http://wiki.centos.org/GSoC/2015/Ideas#docs-toolchain The CentOS Project needs more short-form

I wanted confirm answer from you guys. Request you to provide authentic information on this. Best Regards / Mit freundlichen Grüßen Minal Kulkarni Knorr Bremse Technology Center India Survey No.276, Village Mann, Hinjewadi, Phase II, Tal.Mulshi, Pune - 411 057. Maharashtra , India. Phone: +91 9028098122 Mobile: mailto:minal.kulkarni at knorr-bremse.com

Hi, unfortunately, my build somehow hangs when linking clang binary and my system is in an unusable state. My toolchain is clang-3.8, gold-1.11 and LLVMgold.so from binutils v2.26.1 (both selfmade) and LTO-flag is enabled. My buildsystem uses cmake-3.6.0 and ninja-1.7.1 (both prebuilt). I have 52 last steps left in my 3rd build. My Linux-kernel is v3.13.0-92 from official Ubuntu repositories.

Hi, As discussed earlier about the workflow, I and Kunaal will need a server space to host Bugzilla, a test repository at Github + a git repository at git.centos.org <http://git.centos.org/>. This is temporary, required for development and testing. Please let us know how do we obtain the same? We need it to get started on our project. Thanks! Regards, Lei -------------- next part

Looks like the PlatformToolsets are cached in the .suo file. If you move it out of the way or delete it, VS will re-scan for toolsets. I'm not sure what other user state is stored there, though. That's annoying. =/ On Tue, Dec 3, 2013 at 6:37 AM, Kelly Sommers <kell.sommers at gmail.com>wrote: > Thanks for the reply Reid! I took a look at that script and found that the >

Hi, peter green wrote: > On 18/05/16 04:50, Tim Northover wrote: > If you don't need/want the various Sanitizer runtimes (e.g. you don't > support sanitizers or already have versions provided with GCC) then > it's as easy as not downloading compiler-rt or removing it from the > projects/ directory before running CMake. The build should carry on > quite happily

llvm-toolchain-3.8 seems to have problems on debian armel and raspbian. On raspbian it builds but our armv7 contamination checker blocked it from entering the repo. Further investigation showed that "compiler-rt" was being built with -march=armv7 . I was able to remove the -march with some build-system hacker but then I got a failure on