Looks like it's https://bugs.llvm.org/show_bug.cgi?id=release-12.0.0
On Wed, Jan 27, 2021 at 9:58 AM Kadir Çetinkaya via cfe-dev <
cfe-...@lists.llvm.org> wrote:
> Is there a canonical bug for 12.0.0 release blockers where we can make
> cherry-pick requests (I couldn't find any)?
>
> On Wed, Jan
Looks like it's http://llvm.org/PR39393
On Tue, Oct 22, 2019 at 1:09 PM Nico Weber wrote:
> I'm unable to push. I filed https://bugs.llvm.org/show_bug.cgi?id=43761
>
> What's the github meta bug bug # ?
>
> On Tue, Oct 22, 2019 at 12:57 PM Tom Stellard via lldb-dev <
> lldb-dev@lists.llvm.org> w
I'm unable to push. I filed https://bugs.llvm.org/show_bug.cgi?id=43761
What's the github meta bug bug # ?
On Tue, Oct 22, 2019 at 12:57 PM Tom Stellard via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> On 10/22/2019 09:08 AM, Tom Stellard via Openmp-dev wrote:
> > Hi,
> >
> > We're getting ready
I've used it every now and then. It seems to work well enough for simple
things (stepping through assembly and looking at registers iirc – but maybe
it was stepping through code and looking at variables).
On Fri, Aug 23, 2019 at 7:36 PM Jonas Devlieghere via lldb-dev <
lldb-dev@lists.llvm.org> wro
Awesome :) Thanks much for working on this!
On Fri, Mar 8, 2019 at 4:01 PM Zachary Turner via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> It's been a long time coming and a lot of work to get here, but Host is
> now dependency free. While this may not be enforced in the Xcode project
> (unless
(I wanted to ask about another update, but it looks like there was one
posted to llvm-dev today:
http://lists.llvm.org/pipermail/llvm-dev/2019-January/128840.html
Mentioning this for others who subscribe to cfe-dev or similar but not
llvm-dev.)
On Mon, Dec 10, 2018 at 1:58 PM Nico Weber wrote:
>
Thanks for the update!
On Mon, Dec 10, 2018 at 1:55 PM Tom Stellard wrote:
> On 12/10/2018 10:38 AM, Nico Weber wrote:
> > Here's another question about the current status of this. It's close to
> two months after the official monorepo was supposed to be published. Can
> someone give an update?
Here's another question about the current status of this. It's close to two
months after the official monorepo was supposed to be published. Can
someone give an update? Is this on hold indefinitely? Are there concrete
issues that people are working on and this will happen as soon as those are
resol
What's the status here?
Can someone keep https://llvm.org/docs/Proposals/GitHubMove.html updated
with the current status of things?
And once things are usable, probably update
https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo
as well.
On Wed, Oct 24, 2018 at 4:
On Thu, Jan 12, 2017 at 1:18 PM, Vadim Chugunov via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> I was referring to this: https://support.microsoft.com/en-us/help/
> 2999226/update-for-universal-c-runtime-in-windows. Granted, it was
> probably marked as non-critical, so some users may have skipp
On Tue, Sep 20, 2016 at 4:37 PM, Ted Woodward via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
>
> From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of
> Zachary Turner via lldb-dev
> Sent: Tuesday, September 20, 2016 12:47 PM
>
> > This kind of philisophical debate is probably worth
On Tue, Feb 23, 2016 at 1:21 PM, Tamas Berghammer via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Yes we already have a disk cache on the host. I agree with you that
> waiting 30s at the first startup shouldn't be an issue in general (Pavel
> isn't sharing my opinion). The only catch is that in c
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
On Fri, Jan 22, 2016 at 3:30 PM, Zachary Turner via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Under llvm/tools also checkout lld. So your directories should look like
> this:
>
> llvm
> \-- tools
> \-- clang
> \-- lldb
> \-- lld
>
> Then re-run cmake to generate build files again,
One possible approach is to never run a built executable directly, but to
copy it to some other place (e.g. my-exe.exe -> my-exe-run-13.exe) and only
run the copied executable. Then rebuilding the original won't fail.
On Thu, Oct 15, 2015 at 9:10 AM, Oleksiy Vyalov via lldb-dev <
lldb-dev@lists.ll
15 matches
Mail list logo
