[lldb-dev] [Bug 27935] Linking CXX executable lldb-argdumper and lldb-mi fails
https://llvm.org/bugs/show_bug.cgi?id=27935 Vedran Miletic changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Vedran Miletic --- Fixed a while ago -- You are receiving this mail because: You are the assignee for the bug. ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] A typo on the "Testing LLDB" tutorial page?
Thanks for this, fixed with: % svn commit test.html Sendingtest.html Transmitting file data .done Committing transaction... Committed revision 294597. > On Feb 8, 2017, at 8:44 PM, Ramana via lldb-dev > wrote: > > On the "Testing LLDB" tutorial page, in the description under "RUNNING > TESTS -> Running the full test suite" section, should this > >> cmake -DLLDB_TEST_ARGS="-A i386 -C /path/to/custom/clang" -G Ninja >> ninja check-lldb > > be > >> cmake -DLLDB_TEST_USER_ARGS="-A i386 -C /path/to/custom/clang" -G Ninja >> ninja check-lldb > > Regards, > Ramana > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged
Hi, AArch64 good to go. f27db27da7f75a435d89ba63c8a762885fd86a1a clang+llvm-4.0.0-rc2-aarch64-linux-gnu.tar.xz Diana On 9 February 2017 at 01:33, Hans Wennborg via Release-testers wrote: > Hello testers, > > 4.0.0-rc2 was just tagged from the branch at r294535. > > There are still open relase blocking bugs and merge requests, so this > will not be the last release candidate, but we've had a lot of merges > since the last one, and I'd like to see what the testing looks like. > > The test-release.sh script was updated to also include lld. Make sure > you're using the latest version of the script (ideally from the > branch, but the trunk version is identical), and if lld causes any > problems, pass the "-no-lld" flag. > > Please build, test, and upload binaries to the sftp. Let me know what > comes up, and I'll publish your binaries plus source and docs when > they're ready. > > Thanks, > Hans > ___ > Release-testers mailing list > release-test...@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [llvm-dev] [4.0.0 Release] Release Candidate 2 has been tagged
(stage-3 check-all fails on macOS around libcxxabi but I think it is usual). I pushed: 9df4d8a9c74ccb1aaaf934f19a48d003917c9d81 rc2/clang+llvm-4.0.0-rc2-x86_64-apple-darwin.tar.xz — Mehdi > On Feb 8, 2017, at 4:33 PM, Hans Wennborg via llvm-dev > wrote: > > Hello testers, > > 4.0.0-rc2 was just tagged from the branch at r294535. > > There are still open relase blocking bugs and merge requests, so this > will not be the last release candidate, but we've had a lot of merges > since the last one, and I'd like to see what the testing looks like. > > The test-release.sh script was updated to also include lld. Make sure > you're using the latest version of the script (ideally from the > branch, but the trunk version is identical), and if lld causes any > problems, pass the "-no-lld" flag. > > Please build, test, and upload binaries to the sftp. Let me know what > comes up, and I'll publish your binaries plus source and docs when > they're ready. > > Thanks, > Hans > ___ > LLVM Developers mailing list > llvm-...@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [4.0.0] Release notes nag email
Dear everyone, It's time for the six-monthly release notes nag email in preparation for the upcoming release. As usual, the release notes are almost empty. Please help fill them with the work you've done in the past six months. The notes do get read by a lot of people, so I think they're worth some effort. If you made any interesting changes in the last six months, or know someone who did, please write something about it. You can commit directly the release notes on the branch, or send me a patch and I'll happily commit it for you. If you're responsible for the care of a specific target, please help give those notes some extra love. Here are some examples we might want to mention (thanks LLVM Weekly!). If you're cc'd on this email, you're mentioned below. - Adam, do you want to add a mention of opt-viewer? - Alex, do you want to put something about RISC-V in the notes? - Anastasia, do you want to write something about OpenCL? - Brendon, do you want to mention MachinePipeliner? IIUC, this is only used by Hexagon at the moment? - Dan, do you want to put in an update about WebAssembly? - David, do you want to write something about ADCE? - Davide, do you want to write something about NewGVN? - Dean, XRay started to land in this cycle. Do you want to mention it in the notes? - Dylan, do you want to include an AVR status update? - Eric, want to add a note about clang-change-namespace to the clang-tools-extra notes? - Gor, do you want to add the status of co-routines support? - Jacques, do you want to add a note about Lanai? - James, do you want to mention the switch range reduction through rotation (r277325) optimization? - Kate, do you want to mention the gread LLDB clang-formating or LLDB evolution in general? - Matthias, should we write something about MIR? It's used quite a bit now, is that new for this release? - Oren, do you want to add a note about the new x86 regcall and vectorcall conventions? - Quentin, there's been a lot of work on the global instructions selector. Should we put a status update in the notes? - Reid, do you want to include something about CodeView support? - Richard, want to add something about Modules TS? And C++ in general of course? - Sebastian, can you write something about GVNHoist? - Zach, do you want to add something about the clang-tidy VS plugin? Many thanks, Hans ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [4.0.0 Release] Release Candidate 2 has been tagged
On Wed, Feb 8, 2017 at 4:33 PM, Hans Wennborg wrote: > Hello testers, > > 4.0.0-rc2 was just tagged from the branch at r294535. > > There are still open relase blocking bugs and merge requests, so this > will not be the last release candidate, but we've had a lot of merges > since the last one, and I'd like to see what the testing looks like. > > The test-release.sh script was updated to also include lld. Make sure > you're using the latest version of the script (ideally from the > branch, but the trunk version is identical), and if lld causes any > problems, pass the "-no-lld" flag. > > Please build, test, and upload binaries to the sftp. Let me know what > comes up, and I'll publish your binaries plus source and docs when > they're ready. Windows is ready: 1f06e8b327509f36214a224423eb333d48e53be6 LLVM-4.0.0-rc2-win32.exe f23dcaaf0caf1496300a0e8c00c0f7815c4fb50f LLVM-4.0.0-rc2-win64.exe It was built with the attached batch file. build_llvm_400-rc2._bat_ Description: Binary data ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] Win64 lldb build broken, llvm::call_once and _mm_mfence
I'm happy as long as it builds :-) On Wed, Feb 8, 2017 at 2:26 PM, Zachary Turner wrote: > Should we do that now, as a way to fix this issue, or should we try to get > another fix in first so we have more time to think about using std > call_once? > > On Wed, Feb 8, 2017 at 2:19 PM Reid Kleckner wrote: >> >> I think we can. MSVC's std::once_flag default constructor is constexpr >> now. It still generates dynamic initialization code if you use it as a >> static local, but MSVC defaults to using thread safe static initialization, >> so that isn't a problem unless you disable it, which we don't. We disable it >> in compiler-rt (/Zc:threadSafeInit-), but that doesn't use this code. >> >> On Wed, Feb 8, 2017 at 1:18 PM, Zachary Turner wrote: >>> >>> Is this the right review? https://reviews.llvm.org/D5922 >>> >>> Being that this was over 2 years ago, I suspect it was when we were >>> supporting MSVC2012 and 2013. Now that we're requiring MSVC2015, is it time >>> to reconsider? I don't see any links to an MS Connect issue, so I don't know >>> what the original bug was to know if it has been fixed. >>> >>> >>> On Wed, Feb 8, 2017 at 1:03 PM Reid Kleckner wrote: It's a sad story. Read the comments and the review threads. It's hilarious. On Wed, Feb 8, 2017 at 1:00 PM, Zachary Turner via lldb-dev wrote: > > Why doesn't llvm::call_once() just use std::call_once on Windows? > > On Wed, Feb 8, 2017 at 12:40 PM Hans Wennborg > wrote: >> >> The Win64 lldb build seems broken (at 294367). >> >> I ran into this when trying to build the weekly snapshot >> (http://www.llvm.org/builds/) which includes LLDB these days. >> >> I suspect this might be related to Kamil's changes a few days ago. I >> see Pavel committed something to fix Darwin afterwards. >> >> Zach, do you know what's going on here? Do we have any buildbot >> coverage for this? >> >>Creating library lib\liblldb.lib and object lib\liblldb.exp >> lldbHost.lib(HostInfoWindows.cpp.obj) : error LNK2019: unresolved >> external symbo >> l "void __cdecl llvm::sys::_mm_mfence(void)" >> (?_mm_mfence@sys@llvm@@YAXXZ) refer >> enced in function "void __cdecl llvm::call_once> > 713e15728a6adc> >(struct llvm::once_flag &,class >> > 5728a6adc> &&)" >> (??$call_once@V@@$$V@ll >> >> vm@@YAXAEAUonce_flag@0@$$QEAV@@@Z) >> bin\liblldb.dll : fatal error LNK1120: 1 unresolved externals >> LINK failed. with 1120 > > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > >> > ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged
On 9 Feb 2017, at 01:33, Hans Wennborg via Release-testers
wrote:
>
> 4.0.0-rc2 was just tagged from the branch at r294535.
Building on FreeBSD 10 at least didn't crash this time, and lld built just
fine. :) I uploaded the following:
SHA256 (clang+llvm-4.0.0-rc2-i386-unknown-freebsd10.tar.xz) =
0725eed8060a1a9983432a547a51c78e155584575120e449c41bebd80eb64652
SHA256 (clang+llvm-4.0.0-rc2-amd64-unknown-freebsd10.tar.xz) =
0b71197a3288b4c7c54f12497b4907257eda71d9be0cb26f9497b25539b5a3c3
On i386-freebsd10 there were some interesting test results:
Unexpected Passing Tests (1):
lldb :: Expr/TestCallStdStringFunction.test
Failing Tests (4):
LLVM :: tools/llvm-xray/X86/convert-with-debug-syms.txt
lldb :: Expr/TestCallStopAndContinue.test
lldb :: Expr/TestCallUserAnonTypedef.test
lldb :: Expr/TestCallUserDefinedFunction.test
On amd64-freebsd10 the lldb failures didn't occur, but the 'unexpected passing'
one did, as did the one xray failure.
The xray failure looks like this:
FAIL: LLVM :: tools/llvm-xray/X86/convert-with-debug-syms.txt (31351 of 33866)
TEST 'LLVM ::
tools/llvm-xray/X86/convert-with-debug-syms.txt' FAILED
Script:
--
/home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/llvm-xray
convert -m
/home/dim/llvm-4.0.0/rc2/llvm.src/test/tools/llvm-xray/X86/Inputs/elf64-sample-o2.bin
-y
/home/dim/llvm-4.0.0/rc2/llvm.src/test/tools/llvm-xray/X86/Inputs/naive-log-simple.xray
-f=yaml -o - 2>&1 | /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0
.0-rc2.obj/./bin/FileCheck
/home/dim/llvm-4.0.0/rc2/llvm.src/test/tools/llvm-xray/X86/convert-with-debug-syms.txt
--
Exit Code: 1
Command Output (stderr):
--
/home/dim/llvm-4.0.0/rc2/llvm.src/test/tools/llvm-xray/X86/convert-with-debug-syms.txt:13:15:
error: expected string not found in input
; CHECK-NEXT: - { type: 0, func-id: 2, function: {{.*foo.*}}, cpu: 37, thread:
84697, kind: function-enter,
^
:11:2: note: scanning from here
- { type: 0, func-id: 2, function: 'foo(void)', cpu: 37, thread: 84697,
^
:19:2: note: possible intended match here
- { type: 0, func-id: 3, function: main, cpu: 37, thread: 84697, kind:
function-exit,
^
--
The lldb test failures look like this:
FAIL: lldb :: Expr/TestCallUserAnonTypedef.test (32116 of 32394)
TEST 'lldb :: Expr/TestCallUserAnonTypedef.test' FAILED
Script:
--
/home/dim/llvm-4.0.0/rc2/Phase2/Release/llvmCore-4.0.0-rc2.install/usr/local/bin/clang++
/home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/Inputs/anonymous-struct.cpp
-g -o
/home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserAnonTypedef.test.tmp
&& /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/lldb
-b -s
/home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserAnonTypedef.test
--
/home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserAnonTypedef.test.tmp
|
/home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/FileCheck
/home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserAnonTypedef.test
--
Exit Code: 1
Command Output (stderr):
--
error: Can't run the expression locally: Interpreter doesn't handle one of the
expression's opcodes
/home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserAnonTypedef.test:11:10:
error: expected string not found in input
# CHECK: $0 = 1
^
:1:1: note: scanning from here
(lldb) target create
"/home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserAnonTypedef.test.tmp"
^
:10:18: note: possible intended match here
Breakpoint 1: where = TestCallUserAnonTypedef.test.tmp`main + 55 at
anonymous-struct.cpp:25, address = 0x080486b7
^
--
FAIL: lldb :: Expr/TestCallUserDefinedFunction.test (32117 of 32394)
TEST 'lldb :: Expr/TestCallUserDefinedFunction.test'
FAILED
Script:
--
/home/dim/llvm-4.0.0/rc2/Phase2/Release/llvmCore-4.0.0-rc2.install/usr/local/bin/clang++
/home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/Inputs/call-function.cpp
-g -o
/home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserDefinedFunction.test.tmp
&& /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/lldb
-b -s
/home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserDefinedFunction.test
--
/home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserDefinedFunction.test.tmp
|
/home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/FileCheck
/home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserDefinedFunction.test
--
Exit Code: 1
Command Output (stderr):
--
error: Can't run the e
Re: [lldb-dev] [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged
On Thu, Feb 9, 2017 at 2:23 PM, Dimitry Andric wrote:
> On 9 Feb 2017, at 01:33, Hans Wennborg via Release-testers
> wrote:
>>
>> 4.0.0-rc2 was just tagged from the branch at r294535.
>
> Building on FreeBSD 10 at least didn't crash this time, and lld built just
> fine. :) I uploaded the following:
>
> SHA256 (clang+llvm-4.0.0-rc2-i386-unknown-freebsd10.tar.xz) =
> 0725eed8060a1a9983432a547a51c78e155584575120e449c41bebd80eb64652
> SHA256 (clang+llvm-4.0.0-rc2-amd64-unknown-freebsd10.tar.xz) =
> 0b71197a3288b4c7c54f12497b4907257eda71d9be0cb26f9497b25539b5a3c3
>
> On i386-freebsd10 there were some interesting test results:
>
>
> Unexpected Passing Tests (1):
> lldb :: Expr/TestCallStdStringFunction.test
>
>
> Failing Tests (4):
> LLVM :: tools/llvm-xray/X86/convert-with-debug-syms.txt
> lldb :: Expr/TestCallStopAndContinue.test
> lldb :: Expr/TestCallUserAnonTypedef.test
> lldb :: Expr/TestCallUserDefinedFunction.test
>
> On amd64-freebsd10 the lldb failures didn't occur, but the 'unexpected
> passing' one did, as did the one xray failure.
>
> The xray failure looks like this:
>
> FAIL: LLVM :: tools/llvm-xray/X86/convert-with-debug-syms.txt (31351 of 33866)
> TEST 'LLVM ::
> tools/llvm-xray/X86/convert-with-debug-syms.txt' FAILED
> Script:
> --
> /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/llvm-xray
> convert -m
> /home/dim/llvm-4.0.0/rc2/llvm.src/test/tools/llvm-xray/X86/Inputs/elf64-sample-o2.bin
> -y
> /home/dim/llvm-4.0.0/rc2/llvm.src/test/tools/llvm-xray/X86/Inputs/naive-log-simple.xray
> -f=yaml -o - 2>&1 | /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0
> .0-rc2.obj/./bin/FileCheck
> /home/dim/llvm-4.0.0/rc2/llvm.src/test/tools/llvm-xray/X86/convert-with-debug-syms.txt
> --
> Exit Code: 1
>
> Command Output (stderr):
> --
> /home/dim/llvm-4.0.0/rc2/llvm.src/test/tools/llvm-xray/X86/convert-with-debug-syms.txt:13:15:
> error: expected string not found in input
> ; CHECK-NEXT: - { type: 0, func-id: 2, function: {{.*foo.*}}, cpu: 37,
> thread: 84697, kind: function-enter,
> ^
> :11:2: note: scanning from here
> - { type: 0, func-id: 2, function: 'foo(void)', cpu: 37, thread: 84697,
> ^
> :19:2: note: possible intended match here
> - { type: 0, func-id: 3, function: main, cpu: 37, thread: 84697, kind:
> function-exit,
> ^
>
> --
>
>
>
> The lldb test failures look like this:
>
> FAIL: lldb :: Expr/TestCallUserAnonTypedef.test (32116 of 32394)
> TEST 'lldb :: Expr/TestCallUserAnonTypedef.test' FAILED
>
> Script:
> --
> /home/dim/llvm-4.0.0/rc2/Phase2/Release/llvmCore-4.0.0-rc2.install/usr/local/bin/clang++
>
> /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/Inputs/anonymous-struct.cpp
> -g -o
> /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserAnonTypedef.test.tmp
> && /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/lldb
> -b -s
> /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserAnonTypedef.test
> --
> /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserAnonTypedef.test.tmp
> |
> /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/FileCheck
>
> /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserAnonTypedef.test
> --
> Exit Code: 1
>
> Command Output (stderr):
> --
> error: Can't run the expression locally: Interpreter doesn't handle one of
> the expression's opcodes
> /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserAnonTypedef.test:11:10:
> error: expected string not found in input
> # CHECK: $0 = 1
> ^
> :1:1: note: scanning from here
> (lldb) target create
> "/home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserAnonTypedef.test.tmp"
> ^
> :10:18: note: possible intended match here
> Breakpoint 1: where = TestCallUserAnonTypedef.test.tmp`main + 55 at
> anonymous-struct.cpp:25, address = 0x080486b7
> ^
>
> --
>
>
>
> FAIL: lldb :: Expr/TestCallUserDefinedFunction.test (32117 of 32394)
> TEST 'lldb :: Expr/TestCallUserDefinedFunction.test'
> FAILED
> Script:
> --
> /home/dim/llvm-4.0.0/rc2/Phase2/Release/llvmCore-4.0.0-rc2.install/usr/local/bin/clang++
>
> /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/Inputs/call-function.cpp
> -g -o
> /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserDefinedFunction.test.tmp
> && /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/lldb
> -b -s
> /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserDefinedFunction.test
> --
> /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/li
Re: [lldb-dev] [llvm-dev] [4.0.0] Release notes nag email
> On Feb 9, 2017, at 1:46 PM, Hans Wennborg via llvm-dev > wrote: > > Dear everyone, > > It's time for the six-monthly release notes nag email in preparation > for the upcoming release. > > As usual, the release notes are almost empty. Please help fill them > with the work you've done in the past six months. The notes do get > read by a lot of people, so I think they're worth some effort. > > If you made any interesting changes in the last six months, or know > someone who did, please write something about it. You can commit > directly the release notes on the branch, or send me a patch and I'll > happily commit it for you. > > If you're responsible for the care of a specific target, please help > give those notes some extra love. > > > Here are some examples we might want to mention (thanks LLVM Weekly!). > If you're cc'd on this email, you're mentioned below. > > - Adam, do you want to add a mention of opt-viewer? > > - Alex, do you want to put something about RISC-V in the notes? > > - Anastasia, do you want to write something about OpenCL? > > - Brendon, do you want to mention MachinePipeliner? IIUC, this is only > used by Hexagon at the moment? > > - Dan, do you want to put in an update about WebAssembly? > > - David, do you want to write something about ADCE? > > - Davide, do you want to write something about NewGVN? > > - Dean, XRay started to land in this cycle. Do you want to mention it > in the notes? > > - Dylan, do you want to include an AVR status update? > > - Eric, want to add a note about clang-change-namespace to the > clang-tools-extra notes? > > - Gor, do you want to add the status of co-routines support? > > - Jacques, do you want to add a note about Lanai? > > - James, do you want to mention the switch range reduction through > rotation (r277325) optimization? > > - Kate, do you want to mention the gread LLDB clang-formating or LLDB > evolution in general? > > - Matthias, should we write something about MIR? It's used quite a bit > now, is that new for this release? It is not new, but was never mentioned in the release notes before. So I added a short section in r294656 of the 4.0 branch. - Matthias ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [4.0.0] Release notes nag email
> On Feb 9, 2017, at 1:46 PM, Hans Wennborg wrote: > > Dear everyone, > > It's time for the six-monthly release notes nag email in preparation > for the upcoming release. > > As usual, the release notes are almost empty. Please help fill them > with the work you've done in the past six months. The notes do get > read by a lot of people, so I think they're worth some effort. > > If you made any interesting changes in the last six months, or know > someone who did, please write something about it. You can commit > directly the release notes on the branch, or send me a patch and I'll > happily commit it for you. > > If you're responsible for the care of a specific target, please help > give those notes some extra love. > > > Here are some examples we might want to mention (thanks LLVM Weekly!). > If you're cc'd on this email, you're mentioned below. > > - Adam, do you want to add a mention of opt-viewer? > > - Alex, do you want to put something about RISC-V in the notes? > > - Anastasia, do you want to write something about OpenCL? > > - Brendon, do you want to mention MachinePipeliner? IIUC, this is only > used by Hexagon at the moment? > > - Dan, do you want to put in an update about WebAssembly? > > - David, do you want to write something about ADCE? > > - Davide, do you want to write something about NewGVN? > > - Dean, XRay started to land in this cycle. Do you want to mention it > in the notes? > > - Dylan, do you want to include an AVR status update? > > - Eric, want to add a note about clang-change-namespace to the > clang-tools-extra notes? > > - Gor, do you want to add the status of co-routines support? > > - Jacques, do you want to add a note about Lanai? > > - James, do you want to mention the switch range reduction through > rotation (r277325) optimization? > > - Kate, do you want to mention the gread LLDB clang-formating or LLDB > evolution in general? > > - Matthias, should we write something about MIR? It's used quite a bit > now, is that new for this release? > > - Oren, do you want to add a note about the new x86 regcall and > vectorcall conventions? > > - Quentin, there's been a lot of work on the global instructions > selector. Should we put a status update in the notes? No, I don’t think we want to expose it to the users yet. > > - Reid, do you want to include something about CodeView support? > > - Richard, want to add something about Modules TS? And C++ in general of > course? > > - Sebastian, can you write something about GVNHoist? > > - Zach, do you want to add something about the clang-tidy VS plugin? > > > Many thanks, > Hans ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
