[lldb-dev] lldb-vscode plugin information for Windows/Arm platform

Hi Greg, I intend to understand requirements to set up the lldb-vscode tool for Windows on Arm. I have been looking at your vscode readme from https://github.com/llvm/llvm-project/blob/cfae2c65dbbe1a252958b4db2e32574e8e8dcec0/lldb/tools/lldb-vscode/README.md If I understood correctly Windows on A

[lldb-dev] LLDB Windows on Arm64 buildbot

Hi, This is to notify that we are in process of setting up a LLDB Windows on Arm64 buildbot which will help share the load of maintenance of LLDB Windows platform support. Should you have any query or suggestions please feel free to contact us. Thanks! -- Omair Javaid www.linaro.org ___

Re: [lldb-dev] who is maintaining lldb-x86_64-debian

Hi Jan, On Thu, 2 Sept 2021 at 17:29, Jan Kratochvil wrote: > On Thu, 02 Sep 2021 12:42:37 +0200, Raphael “Teemperor” Isemann via > lldb-dev wrote: > > If this is about the TestGuiBasicDebug failures, then that test is also > > failing on other bots. I personally would vote to disable the test as

[lldb-dev] who is maintaining lldb-x86_64-debian

Hi There have been sporadic failures due to timeouts on lldb-x86_64-debian . I don't see Pavel maintingi it now. Does anyone know who's looking after this bot? Thanks! -- Omair Javaid www.linaro.org ___ lldb-

Re: [lldb-dev] [cfe-dev] [llvm-dev] Attn Buildbot Owners: Would you like your builder to test the release branch?

On Wed, 14 Apr 2021 at 20:41, Tom Stellard wrote: > On 4/14/21 5:50 AM, Omair Javaid wrote: > > Ping! > > > > Tom, any update on this? > > > > Yes, thanks for reminding me. The infrastructure is in place now, so > we can start adding more bots. Do you have a bot that you want to add? > > -Tom >

Re: [lldb-dev] [cfe-dev] [llvm-dev] Attn Buildbot Owners: Would you like your builder to test the release branch?

Ping! Tom, any update on this? On Mon, 15 Feb 2021 at 20:02, Nemanja Ivanovic wrote: > We are interested in doing this for PPC as well. Not likely for all of our > bots, but one or two select ones. > > On Fri, Feb 12, 2021 at 11:51 AM Tom Stellard via cfe-dev < > cfe-...@lists.llvm.org> wrote:

Re: [lldb-dev] [llvm-dev] [cfe-dev] Attn Buildbot Owners: Would you like your builder to test the release branch?

Hi Tom, We at Linaro are maintaining LLVM Arm/AArch64 buildbots and want a host buildbot for testing of release branches. Kindly share the steps to do this. Do we have to host separate builbots for tracking release branches or is it possible to track multiple branches by existing buildbots assumi

Re: [lldb-dev] RFC: AArch64 Linux Memory Tagging Support for LLDB

Hi Jason, I wanted to bring this to your attention that we are also working on pointer authentication support. We have so far only done register context changes to allow for enabling/disabling pointer authentication features and read/write pauth Cmask/Dmask registers when available. I am currently

[lldb-dev] [RFC] Support for AArch64/Arm64 scalable vector extension (SVE)

Hi, I am going to be starting work on implementing LLDB support for AArch64/Arm64 scalable vector extension (SVE) in coming weeks. For a quick walk through of SVE please read through this doc here: https://www.kernel.org/doc/Documentation/arm64/sve.txt In summary it allows hardware + kernel which

[lldb-dev] LLDB remote tests via LIT and specifying threads check-lldb

Hi I am new to LIT and looking to run lldb testsuite in remote target configuration via lit (ninja check-lldb). Also I am looking to restrict check-lldb to run a specified number of threads at a time, something similar to LLDB_TEST_THREADS=8 used with dotest.py. Please share remote testing setup i

[lldb-dev] LLDB testsuite failing to import lldb python module

Hi, I am trying to run lldb testsuite on arm hardware with lldb and lldbserver binaries cross compiled on x86_64 builder. I have lldb-server running on my arm hardware. Also i have lldb source tree checkout and liblldb and lldb binaries places in lib and bin folders respectively. I am ablle to c

Re: [lldb-dev] Patch to fix REPL for ARMv7 & ARMv6 on linux

Hi Will, I dont understand REPL and thus the benefits it will have by making change to architecture name. I would not recommend to drop any information that we get from the host operating system. LLDB maintains core information alongwith triple in ArchSpec, may be you can parse triple to reflect