On Wed, Oct 19, 2016 at 4:21 PM Tim Hammerquist wrote:
> On Wed, Oct 19, 2016 at 4:09 PM, Eric Christopher
> wrote:
>
>
> On Wed, Oct 19, 2016 at 3:34 PM Tim Hammerquist wrote:
>
> I was mistaken.
>
> The system toolchain builds stage1 llvm, clang & co.
> The system toolchain builds lldb contai
On Wed, Oct 19, 2016 at 4:09 PM, Eric Christopher
wrote:
>
> On Wed, Oct 19, 2016 at 3:34 PM Tim Hammerquist wrote:
>
>> I was mistaken.
>>
>> The system toolchain builds stage1 llvm, clang & co.
>> The system toolchain builds lldb containing the llvm/clang/etc bits.
>> The system toolchain buil
On Wed, Oct 19, 2016 at 3:34 PM Tim Hammerquist wrote:
> I was mistaken.
>
> The system toolchain builds stage1 llvm, clang & co.
> The system toolchain builds lldb containing the llvm/clang/etc bits.
> The system toolchain builds gtest test programs.
>
The stage1 compiler builds the python test
I was mistaken.
The system toolchain builds stage1 llvm, clang & co.
The system toolchain builds lldb containing the llvm/clang/etc bits.
The system toolchain builds gtest test programs.
The stage1 compiler builds the python test inferiors.
On Wed, Oct 19, 2016 at 3:28 PM, Eric Christopher
wrot
On Wed, Oct 19, 2016 at 3:26 PM Tim Hammerquist wrote:
> The LLDB job in llvm.org will build a stage1 RA with
> llvm+clang+libcxx+compiler-rt using the system compiler, and use the new
> compiler to build lldb.
>
> By default, this is kicked off automatically when a clang stage1 RA is
> successfu
The LLDB job in llvm.org will build a stage1 RA with
llvm+clang+libcxx+compiler-rt using the system compiler, and use the new
compiler to build lldb.
By default, this is kicked off automatically when a clang stage1 RA is
successful, but can be manually triggered to build HEAD, or any revision
desi
>From chatting with Tim it sounds like at least one lldb bot uses the ToT
compiler - we should probably verify that not only does it use that to
build lldb but uses it for the tests. That'll get us at least some testing
here.
-eric
On Wed, Oct 19, 2016 at 12:55 PM Greg Clayton via lldb-dev <
lldb
I believe we are good, but it would be good to verify via testing once a
compiler becomes available.
Greg
> On Oct 19, 2016, at 12:19 PM, Ted Woodward via lldb-dev
> wrote:
>
> This might affect us. Do we handle it correctly?
>
> https://reviews.llvm.org/D16697
>
> --
> Qualcomm Innovatio
This might affect us. Do we handle it correctly?
https://reviews.llvm.org/D16697
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
Linux Foundation Collaborative Project
___
lldb-dev
> On Oct 18, 2016, at 10:14 PM, Chunseok Lee via lldb-dev
> wrote:
>
> I have noticed that lldb-mi stopped after executing "-target-select remote".
> My execution step is like:
> -
> $ lldb-server g --platform=remote-linux "*:1234"
>
> $ lldb-mi
> (g
Hi!
I think it's okay that remote target is stopped when you connect to it.
Just skip it.
On Wed, Oct 19, 2016 at 8:14 AM, Chunseok Lee via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> I have noticed that lldb-mi stopped after executing "-target-select
> remote".
> My execution step is like:
> -
> On Oct 18, 2016, at 6:43 PM, Clayton, Greg wrote:
>
> > On Oct 18, 2016, at 7:48 AM, Giusti, Valentina
> wrote:
> >
> > Hi Greg,
> >
> > Thanks a lot for your reply, please find below my answers.
> >
> >> You can install new python commands that can do the job to work out
> >> the details.
> >>
12 matches
Mail list logo
