I've been putting together a patch to bring that back and I've just posted it
as http://reviews.llvm.org/D16679.
From: Nikola Smiljanic [mailto:popiz...@gmail.com]
Sent: 28 January 2016 02:00
To: Daniel Sanders
Cc: James Molloy; Ismail Donmez; Ben Pope; cfe-dev; openmp-dev
(openmp-...@lists.llvm
Hello all,
we are running into limitations of the current module download/caching
system. A simple android application can link to about 46 megabytes
worth of modules, and downloading that with our current transfer rates
takes about 25 seconds. Much of the data we download this way is never
actual
This is all fixed up by r259028. Change comments for r259027 contain some
changes to the build requirements for Xcode OS X builds.
These boil down to essentially:
* OS X 10.9 is the minimum deployment version now, up from 10.8. This is
driven by the LLVM/clang cmake-based build.
* Cmake is now
On Thu, Jan 28, 2016 at 9:28 AM, Todd Fiala via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> This is all fixed up by r259028. Change comments for r259027 contain some
> changes to the build requirements for Xcode OS X builds.
>
> These boil down to essentially:
> * OS X 10.9 is the minimum deploy
Yeah, we poked around at it for a while here.
This is the issue I hit:
-- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB
-- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB - Failed
-- Looking for __atomic_fetch_add_4 in atomic
-- Looking for __atomic_fetch_add_4 in atomic - not found
CMake Error at c
(7.3 beta 2 is public, but I was primarily focusing on on 7.2 and 7.3 beta
1).
On Thu, Jan 28, 2016 at 11:09 AM, Todd Fiala wrote:
> Yeah, we poked around at it for a while here.
>
> This is the issue I hit:
>
> -- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB
> -- Performing Test HAVE_CXX_ATOMIC
That could be a reasonable way to do it. Now that I think about it,
unittest2 already gives us a generic skip where we can put the logic in
that we want. Not sure why that didn't occur to me earlier as I've done
that very thing in the past. (I think I've conditioned myself to use our
custom decor
I'd prefer to avoid calling the unittest2 functions. We already do that in
a couple places, but if we could centralize on one place where we call
unittest2 decorators it would really make it easier to customize our own
decorators. For example, I have a short-term goal of adding an option to
dotes
https://llvm.org/bugs/show_bug.cgi?id=26363
Bug ID: 26363
Summary: lldb 3.8.0.rc1 fails to build out of llvm tree
Product: lldb
Version: 3.8
Hardware: PC
OS: All
Status: NEW
Severity: normal
Prio
Hi,
On mac OS, I am having difficulty understanding the launch debugger events
sequence of lldb. I used the following code to play around LLDB. I found,
for some binaries, debugger will enter stopped/paused mode, waiting for my
further input, print stack shows:
dbg> bt
* thread #1: tid = 0x15153e,
10 matches
Mail list logo
