Re: [lldb-dev] LLVM Social - Paris: January 27th, 2016

Reminder: the next LLVM social in Paris will happen on January 27th, 2016. Everyone interested in LLVM, Clang, lldb, Polly, ... is invited to join. For this meetup, we will start with John Regehr giving us a talk about undefined behaviour and we will continue with our usual casual meeting. Event

Re: [lldb-dev] CFP for the 6th European LLVM conference on March 17-18, 2016 in Barcelona, Spain

Reminder: the deadline for submitting papers for the EuroLLVM is Monday. Kind regards, -- Arnaud On Sun, Dec 13, 2015 at 10:42 PM, Arnaud Allard de Grandmaison < arnaud.ad...@gmail.com> wrote: > We are pleased to announce the 6th European LLVM conference on March > 17-18, 2016 in Barcelona, Spa

Re: [lldb-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

Something is failing on 32bit Fedora 23 (compiler-rt?), test suite looks good. On Fri, Jan 22, 2016 at 2:52 PM, Brian Cain via cfe-dev < cfe-...@lists.llvm.org> wrote: > On Thu, Jan 21, 2016 at 8:31 PM, Eric Fiselier wrote: > >> >> On Thu, Jan 21, 2016 at 7:04 PM, Brian Cain via cfe-dev < >> cfe

Re: [lldb-dev] clang-format now supports return type on separate line

Agreed. My guidance has been that we go ahead and require submitters to use clang-format for patches, but to acknowledge that there may be cases where this produces undesirable results. Manual formatting to correct these issues is acceptable and should lead to discussions about concrete exampl

Re: [lldb-dev] clang-format now supports return type on separate line

By the way, one place where you are guaranteed to get undesirable results is where you have a large array formatted so that the columns line up. Like in our options tables in the CommandObjects. If you're using git, one way to avoid having clang-format touch these files is to commit that file by i

Re: [lldb-dev] clang-format now supports return type on separate line

Okay, thanks for the tip! On Fri, Jan 22, 2016 at 8:32 AM, Zachary Turner wrote: > By the way, one place where you are guaranteed to get undesirable results > is where you have a large array formatted so that the columns line up. > Like in our options tables in the CommandObjects. If you're usi

Re: [lldb-dev] LLDB test questions

Hi Ted! I hope you don't mind - I'm going to CC lldb-dev since there is some useful general info in here for others who are getting started with the test system. (And others can fact-check anything I may gloss over here). On Thu, Jan 21, 2016 at 2:00 PM, Ted Woodward wrote: > Hi Todd, > > > >

[lldb-dev] Ubuntu version-based fail/skip

Hey all, What do you think about having some kind of way of marking the (in this case, specifically) Ubuntu distribution for fail/skip test decorators? I've had a few cases where I've needed to mark tests failing on for Ubuntu where it really was only a particular release of an Ubuntu distribution

Re: [lldb-dev] [3.8 Release] Schedule and call for testers

On Fri, Dec 11, 2015 at 3:14 PM, Hans Wennborg wrote: > It's not quite time to start the 3.8 release process, but it's time to > start planning. > > Please let me know if you want to help with testing and building > release binaries for your favourite platform. (If you were a tester on > the previ

Re: [lldb-dev] lldb status at windows

Look like I miss something , but i cant debug simple program program compiled with clang from trunk (258016), msvc 2015 stdlib, from vs2015 x86 developer console . i use lldb from trunk #include "stdio.h" int main(int argc, char **argv) { printf("hello1\n"); printf("he

Re: [lldb-dev] lldb status at windows

When you compile, you need to use -fuse-ld=lld. Most people miss this step. That said, it's not supposed to hang, but it is supposed to not work. What's the command line you used with clang? On Fri, Jan 22, 2016 at 11:08 AM Red Skotina wrote: > Look like I miss something , but i cant debug si

Re: [lldb-dev] lldb status at windows

yes, i miss it. but anyway dont work d:\code\Unity_Unpacker\tests\test2>clang -v -fuse-ld=lld main.cpp clang version 3.9.0 (trunk 258509) Target: i686-pc-windows-msvc Thread model: posix InstalledDir: d:\code\llvm\build\bin "d:\\code\\llvm\\build\\bin\\clang.exe" -cc1 -triple i686-pc-windows-msv

Re: [lldb-dev] clang-format now supports return type on separate line

Apparently, you can also disable the formatting of a piece of code by a magic comment. Could be quite useful for those tables. From the docs: - Clang-format understands also special comments that switch formatting in a delimited range. The code between a comment // clang-format off or /* clang-

Re: [lldb-dev] lldb status at windows

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, recompile, and then it should work. Right now the problem is that lld-link.exe hasn't been compiled yet. On Fri,

Re: [lldb-dev] clang-format now supports return type on separate line

Oh neat, I didn't know about that. I'll play around with that when I have some time and see how the behavior works with respect to git clang-format (which formats diffs instead of entire files) On Fri, Jan 22, 2016 at 12:29 PM Pavel Labath wrote: > Apparently, you can also disable the formattin

Re: [lldb-dev] lldb status at windows

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,

Re: [lldb-dev] clang-format now supports return type on separate line

Wow, that’s a super handy feature and probably goes a long way toward alleviating concerns about tables. I have to say, I always feel good vibes about a source base when they have lint directives in comments. Shows they run lint as a matter of course. Sean > On Jan 22, 2016, at 12:29 PM, Pave

Re: [lldb-dev] clang-format now supports return type on separate line

I just tried the 'git clang-format' workflow on a gtest change I'll be committing soon. It worked just fine and is quite handy. On Fri, Jan 22, 2016 at 1:13 PM, Sean Callanan wrote: > Wow, that’s a super handy feature and probably goes a long way toward > alleviating concerns about tables. > I

[lldb-dev] [Bug 26261] New: gtest failure in PythonDataObjectsTest.TestPythonBytes on OS X 10.11

https://llvm.org/bugs/show_bug.cgi?id=26261 Bug ID: 26261 Summary: gtest failure in PythonDataObjectsTest.TestPythonBytes on OS X 10.11 Product: lldb Version: unspecified Hardware: Macintosh OS: MacOS X

[lldb-dev] [Bug 26265] New: [Windows] Evaluating arguments gives incorrect values except for frame 0

https://llvm.org/bugs/show_bug.cgi?id=26265 Bug ID: 26265 Summary: [Windows] Evaluating arguments gives incorrect values except for frame 0 Product: lldb Version: unspecified Hardware: PC OS: Windows NT

[lldb-dev] [3.8 Release] Release Candidate 1 source and binaries available

Hello everyone, Source and binaries for LLVM-3.8.0-rc1 are now available at http://llvm.org/pre-releases/3.8.0/ (Binaries for some platforms are still missing, but I figured it was time to get this out there.) Please try it, run tests, build your favourite projects, and *file bugs* about anythin

[lldb-dev] [Bug 26267] New: IncompleteModulesTestCase asserting in clang on Darwin with Xcode 7.3 Beta 1

https://llvm.org/bugs/show_bug.cgi?id=26267 Bug ID: 26267 Summary: IncompleteModulesTestCase asserting in clang on Darwin with Xcode 7.3 Beta 1 Product: lldb Version: unspecified Hardware: Macintosh OS: MacO

[lldb-dev] LLDB OS X buildbot/testbot details

Hi all, The llvm.org Green Dragon (i.e. Jenkins-based) LLDB OS X buildbot/testbot has received some improvements today. The Jenkins build now uses the xUnit plugin to process xUnit-based test suite results, which are displayed more usefully on the "build and test" page here