Hello,
I’m trying to build/test/run the latest lldb on the latest Red Hat Fedora, but
I’m seeing four failures. Is this expected? What operating system do the LLVM
build bots run? Thanks!
Dave
[1+3] Python script sym-linking LLDB Python API
[1+2] Preparing lit tests
[1+1] cd /home/dave/s/lc/cl
> On Mar 25, 2019, at 9:04 AM, Jan Kratochvil wrote:
>
> On Mon, 25 Mar 2019 12:05:33 +0100, David Zarzycki via lldb-dev wrote:
>> I’m trying to build/test/run the latest lldb on the latest Red Hat Fedora,
>> but I’m seeing four failures. Is this expected? What operating
> On Mar 25, 2019, at 12:26 PM, Jan Kratochvil
> wrote:
>
> On Mon, 25 Mar 2019 14:11:09 +0100, David Zarzycki via lldb-dev wrote:
>> 5.0.3-200.fc29.x86_64 (mockbu...@bkernel03.phx2.fedoraproject.org) (gcc
>> version 8.3.1 20190223 (Red Hat 8.3.1-2) (GCC)) #1 SMP Tue
> On Mar 26, 2019, at 3:07 AM, Jan Kratochvil wrote:
>
> On Mon, 25 Mar 2019 19:47:36 +0100, David Zarzycki via lldb-dev wrote:
>> Also, given that two of the test failures are Intel specific (the mxcsr
>> register write failures), what class of hardware do you use? My work
llvm.org/pr35043, so
> I'll rename the variables there and that should fix it. Not sure about
> the others.
>
> - Raphael
>
> Am Mo., 25. März 2019 um 12:06 Uhr schrieb David Zarzycki via lldb-dev
> :
>>
>> Hello,
>>
>> I’m trying to build/tes
One is expected to use `git llvm push`. For more information, please see:
https://llvm.org/docs/GettingStarted.html#for-developers-to-commit-changes-from-git
> On Sep 3, 2019, at 7:06 PM, David Greene via cfe-dev
> wrote:
>
> What is the expected way to do commits? Do we push directly to mas
> On Oct 14, 2019, at 9:15 PM, Renato Golin via llvm-dev
> wrote:
>
> On Fri, 11 Oct 2019 at 00:22, Tom Stellard via llvm-dev
> wrote:
>> With my latest changes in https://reviews.llvm.org/D67772 it is actually
>> possible
>> to create a new branch with git-llvm, so we could print a disclaim
I’d like to see it go away. For better and for worse, git is feature rich and
that makes maintaining a wrapper script difficult. Personally speaking, I had
to fix a git-llvm bug recently because it made flimsy assumptions about git
remote names and how upstream tracking repositories work.
> On
Hi Hans,
FYI – https://reviews.llvm.org/D72980
> On Jan 15, 2020, at 9:34 AM, Hans Wennborg via libcxx-dev
> wrote:
>
> Hello everyone,
>
> The release branch for LLVM 10 and its sub-projects was created from
> trunk at e26a78e70857273c83aaacd4aa0edb36effe70e3, and the trunk
> version was bu
