[lldb] NFC remove DISALLOW_COPY_AND_ASSIGNSummary:This is how I applied my clang-tidy check (seehttps://reviews.llvm.org/D80531) in order to remove`DISALLOW_COPY_AND_ASSIGN` and have deleted cop
[lldb] NFC remove DISALLOW_COPY_AND_ASSIGNSummary:This is how I applied my clang-tidy check (seehttps://reviews.llvm.org/D80531) in order to remove`DISALLOW_COPY_AND_ASSIGN` and have deleted copy ctors and deletedassignment operators instead.```lang=bashgrep DISALLOW_COPY_AND_ASSIGN /opt/notnfs/kkleine/llvm/lldb -r -l | sort | uniq > filesfor i in $(cat files);do clang-tidy \ --checks="-*,modernize-replace-disallow-copy-and-assign-macro" \ --format-style=LLVM \ --header-filter=.* \ --fix \ -fix-errors \ $i;done```Reviewers: espindola, labath, aprantl, teemperorReviewed By: labath, aprantl, teemperorSubscribers: teemperor, aprantl, labath, emaste, sbc100, aheejin, MaskRay, arphaman, usaxena95, lldb-commitsTags: #lldbDifferential Revision: https://reviews.llvm.org/D80543
show more ...
[lldb] NFC: Fix trivial typo in comments, documents, and messagesDifferential Revision: https://reviews.llvm.org/D77460
[NFC] Remove ASCII lines from commentsA lot of comments in LLDB are surrounded by an ASCII line to delimit thebegging and end of the comment.Its use is not really consistent across the code base
[NFC] Remove ASCII lines from commentsA lot of comments in LLDB are surrounded by an ASCII line to delimit thebegging and end of the comment.Its use is not really consistent across the code base, sometimes thelines are longer, sometimes they are shorter and sometimes they areomitted. Furthermore, it looks kind of weird with the 80 column limit,where the comment actually extends past the line, but not by much.Furthermore, when /// is used for Doxygen comments, it looksparticularly odd. And when // is used, it incorrectly gives theimpression that it's actually a Doxygen comment.I assume these lines were added to improve distinguishing betweencomments and code. However, given that todays editors and IDEs do agreat job at highlighting comments, I think it's worth to drop this forthe sake of consistency. The alternative is fixing all theinconsistencies, which would create a lot more churn.Differential revision: https://reviews.llvm.org/D60508llvm-svn: 358135
Bring Doxygen comment syntax in sync with LLVM coding style.This changes '@' prefix to '\'.llvm-svn: 355841
Update the file headers across all of the LLVM projects in the monorepoto reflect the new license.We understand that people may be surprised that we're moving the headerentirely to discuss the ne
Update the file headers across all of the LLVM projects in the monorepoto reflect the new license.We understand that people may be surprised that we're moving the headerentirely to discuss the new license. We checked this carefully with theFoundation's lawyer and we believe this is the correct approach.Essentially, all code in the project is now made available by the LLVMproject under our new license, so you will see that the license headersinclude that license only. Some of our contributors have contributedcode under our old license, and accordingly, we have retained a copy ofour old license notice in the top-level files in each project andrepository.llvm-svn: 351636
Remove comments after header includes.This patch removes the comments following the header includes. They wereadded after running IWYU over the LLDB codebase. However they add littlevalue, are of
Remove comments after header includes.This patch removes the comments following the header includes. They wereadded after running IWYU over the LLDB codebase. However they add littlevalue, are often outdates and burdensome to maintain.Differential revision: https://reviews.llvm.org/D54385llvm-svn: 346625
*** This commit represents a complete reformatting of the LLDB source code*** to conform to clang-format’s LLVM style. This kind of mass change has*** two obvious implications:Firstly, merging t
*** This commit represents a complete reformatting of the LLDB source code*** to conform to clang-format’s LLVM style. This kind of mass change has*** two obvious implications:Firstly, merging this particular commit into a downstream fork may be a hugeeffort. Alternatively, it may be worth merging all changes up to this commit,performing the same reformatting operation locally, and then discarding themerge for this particular commit. The commands used to accomplish thisreformatting were as follows (with current working directory as the root ofthe repository): find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} + find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ;The version of clang-format used was 3.9.0, and autopep8 was 1.2.4.Secondly, “blame” style tools will generally point to this commit instead ofa meaningful prior commit. There are alternatives available that will attemptto look through this change and find the appropriate prior commit. YMMV.llvm-svn: 280751
Revert accidental commit.llvm-svn: 151074
Remove a ton of implicit narrowing conversions for C++11 compatibility.llvm-svn: 151071
More improvements to not follow child processes and improved logging that always shows the process info.llvm-svn: 148257
Added some fixes for the fd interposing dylib:- don't strip too many frames from the backtrace when logging close backtraces- cleanup some logging messagesllvm-svn: 148195
Fix make errors (define the DYLIB_ONLY make variable).llvm-svn: 147823
Added a file descriptor interposing library for darwin. This can catch allfunctions that can create file descriptors and close them. It will warn whenthere close file descriptor call that returns w
Added a file descriptor interposing library for darwin. This can catch allfunctions that can create file descriptors and close them. It will warn whenthere close file descriptor call that returns with EBADF and show the corresponding stack backtraces that caused the issue. It will also log allfile descriptor create and delete calls. See the comments at the top ofFDInterposing.cpp for all of the details.llvm-svn: 147816