Re: [lldb-dev] [cfe-dev] RFC: Using GitHub Actions for CI testing on the release/* branches

2019-11-12 Thread Tom Stellard via lldb-dev
On 11/12/2019 10:03 AM, Jonas Devlieghere wrote: > Hey Tom, > > That sounds really useful. Would it be possible to include LLDB as > well? We have a subset of tests (unit & lit) that can be run without > Python/SWIG by passing LLDB_DISABLE_PYTHON=ON to CMake. > I can try to add an lldb builder.

Re: [lldb-dev] [cfe-dev] RFC: Using GitHub Actions for CI testing on the release/* branches

2019-11-12 Thread Jonas Devlieghere via lldb-dev
Hey Tom, That sounds really useful. Would it be possible to include LLDB as well? We have a subset of tests (unit & lit) that can be run without Python/SWIG by passing LLDB_DISABLE_PYTHON=ON to CMake. Thanks, Jonas On Tue, Nov 12, 2019 at 2:35 AM Hans Wennborg via cfe-dev wrote: > > On Tue, Nov

Re: [lldb-dev] RFC: Using GitHub Actions for CI testing on the release/* branches

2019-11-12 Thread Hans Wennborg via lldb-dev
On Tue, Nov 12, 2019 at 1:32 AM Tom Stellard via lldb-dev wrote: > > Hi, > > I would like to start using GitHub Actions[1] for CI testing on the release/* > branches. As far as I know we don't have any buildbots listening to the > release branches, and I think GitHub Actions are a good way for us

Re: [lldb-dev] Slow expression evaluation (ASTImporter is too eager?)

2019-11-12 Thread Jaroslav Sevcik via lldb-dev
Hi, thanks for the feedback, I did some more investigation and now I understand a bit better where the LayoutRecordType calls are coming from. They are initiated by Clang's code generation for types, which insists on generating full LLVM types for any complete RecordDecl (see https://github.com/l

Re: [lldb-dev] [llvm-dev] RFC: Using GitHub Actions for CI testing on the release/* branches

2019-11-12 Thread Diana Picus via lldb-dev
Hi Tom, This sounds very interesting! +1 from me. What does this imply for the release testers? Would it be possible / desirable for us to add self-hosted runners for other architectures? I'm assuming GitHub only provides x86, right? I totally missed any details about that in their docs, but it se

Re: [lldb-dev] [llvm-dev] RFC: Using GitHub Actions for CI testing on the release/* branches

2019-11-12 Thread James Henderson via lldb-dev
Although I've not had any Github Action experience, and despite being one who has raised objections to other parts of adopting github features, this sounds like a sensible idea. It seems odd to me that we don't already have some form of CI for our releases, so anything that improves on that is grea

Re: [lldb-dev] Identifying instructions that definitely access memory

2019-11-12 Thread Vangelis Tsiatsianas via lldb-dev
Hi Tatyana, Thank you for your reply! 🙂 If I understand correctly, TargetOpcode::G_{LOAD, STORE} do not cover x86’s mov instructions (and other relevant instructions of both x86 the rest of supported architectures) and such, which also access memory, however I will look into it more. Addition