Linaro LLVM engagement

[Virendra Kumar Pathak]

Hi All,

I am interested in understanding Linaro LLVM activity.
I have already gone through
https://wiki.linaro.org/WorkingGroups/ToolChain/LLVM.

Could you please guide me on below questions.

1. On which LLVM & clang version, linaro is actively working now ?
2. Where can I find the latest "linaro-llvm" source code & binary? I could
not find any official git repo for "linaro-llvm" at https://git.linaro.org/.
3. Could you please explain Linaro LLVM working model? How
similar/different it is when compared with Linaro-GCC engagement.
4. Certain links (e.g Roadmap) at
https://wiki.linaro.org/WorkingGroups/ToolChain/LLVM ask for login
credentials. Any comment on how to obtain the permission?

Thanks in advance for your time.

[Adhemerval Zanella]

Post by Virendra Kumar Pathak
Hi All,
I am interested in understanding Linaro LLVM activity.
I have already gone through https://wiki.linaro.org/WorkingGroups/ToolChain/LLVM.
Could you please guide me on below questions.
1. On which LLVM & clang version, linaro is actively working now ?
2. Where can I find the latest "linaro-llvm" source code & binary? I could not find any official git repo for "linaro-llvm" at https://git.linaro.org/.
3. Could you please explain Linaro LLVM working model? How similar/different it is when compared with Linaro-GCC engagement.
4. Certain links (e.g Roadmap) at https://wiki.linaro.org/WorkingGroups/ToolChain/LLVM ask for login credentials. Any comment on how to obtain the permission?
Thanks in advance for your time.

Hi Virendra,

I try to answer the question and Ryan/Renato may correct me if I am wrong:

1. On which LLVM & clang version, linaro is actively working now ?

We currently work only on master with mainly focusing new enablement and
bugfixes. We do not currently focus neither on maintaining or backports
for older releases.

2. Where can I find the latest "linaro-llvm" source code & binary? I could
not find any official git repo for "linaro-llvm" at https://git.linaro.org/.

Because there is none at git.linaro.org. We do not track the devel internally,
but rather use the already clang/llvm infra (maillist, repo, review tools, etc.)

3. Could you please explain Linaro LLVM working model? How similar/different
it is when compared with Linaro-GCC engagement.

It is similar on the aspect we try to work as much as possible on master, but
we not aim to provide a toolchain suite based on LLVM (like we do for GCC).

4. Certain links (e.g Roadmap) at https://wiki.linaro.org/WorkingGroups/ToolChain/LLVM
ask for login credentials. Any comment on how to obtain the permission?

You will need to ask either to Ryan Arnold <***@linaro.org> or Renato
Golin <***@linaro.org>. The 'Roadmap' is a link to the old issue
tracking we used and I am not sure how it the procedure (if any) to give
access to the one we are using now.

But I can talk with current projects we are working at Linaro now, since they
are pretty much public. Currently we are focusing on general ARM and AArch64
fixes and development, we are closing the sanitizer work (asan, msan, tsan,
lsan, and dfsan), and on the new linker.

[Renato Golin]

On 17 December 2015 at 18:14, Adhemerval Zanella

Post by Virendra Kumar Pathak
1. On which LLVM & clang version, linaro is actively working now ?
We currently work only on master with mainly focusing new enablement and
bugfixes. We do not currently focus neither on maintaining or backports
for older releases.

That's correct.

If you want to backport patches to previous releases, we'll have to do
that upstream and wait for the next point-release to come out. Our job
is to make sure the backports work well on ARM and AArch64, and we
will run the same validation as we always do.

Linaro doesn't have infrastructure to do a private release. We can't
test all back-ends, so we can't afford to support a side product.

Post by Virendra Kumar Pathak
2. Where can I find the latest "linaro-llvm" source code & binary? I could
not find any official git repo for "linaro-llvm" at https://git.linaro.org/.
Because there is none at git.linaro.org. We do not track the devel internally,
but rather use the already clang/llvm infra (maillist, repo, review tools, etc.)

Precisely. *Everything* we do is upstream.

If you need a special feature, please create a bug on LLVM's bugzilla
and copy one of us. If the feature is private/sensitive, members can
create bugs on our internal system instead.

However, since we cannot afford supporting a side product, *all*
features will be ultimately implemented upstream.

Post by Virendra Kumar Pathak
3. Could you please explain Linaro LLVM working model? How similar/different
it is when compared with Linaro-GCC engagement.
It is similar on the aspect we try to work as much as possible on master, but
we not aim to provide a toolchain suite based on LLVM (like we do for GCC).

The main difference is how the LLVM community works, which is
completely different than GCC's with respect to how patches are
accepted, features implemented, releases validated and used.

That's the reason we can't afford to support Linaro-LLVM in the same
way we do Linaro-GCC. The expectations and overall usage are
completely different.

Post by Virendra Kumar Pathak
4. Certain links (e.g Roadmap) at https://wiki.linaro.org/WorkingGroups/ToolChain/LLVM
ask for login credentials. Any comment on how to obtain the permission?
tracking we used and I am not sure how it the procedure (if any) to give
access to the one we are using now.

Our roadmap is not public. We can, however, divulge the upstream
focus, as Adhemerval did below. We should, however, have a
public-facing webpage with all possible upstream information, and
you're not the first one to ask.

I'll start working on that first thing next year, following Linaro's
guidelines, which I believe so far have been scarce on that subject.

Post by Virendra Kumar Pathak
But I can talk with current projects we are working at Linaro now, since they
are pretty much public. Currently we are focusing on general ARM and AArch64
fixes and development, we are closing the sanitizer work (asan, msan, tsan,
lsan, and dfsan), and on the new linker.

We're also working on the debugger (LLDB) for AArch64 and ARM,
integrated assembler support, libc++ and compiler-rt, as well as most
ARM and AArch64 validation for continuous integration and releases.


cheers,
--renato