[lldb][NFC] Fix all formatting errors in .cpp file headers
Summary:
A *.cpp file header in LLDB (and in LLDB) should like this:
```
//===-- TestUtilities.cpp -------------------------------------------------===//
```
However in LLDB most of our source files have arbitrary changes to this format and
these changes are spreading through LLDB as folks usually just use the existing
source files as templates for their new files (most notably the unnecessary
editor language indicator `-*- C++ -*-` is spreading and in every review
someone is pointing out that this is wrong, resulting in people pointing out that this
is done in the same way in other files).
This patch removes most of these inconsistencies including the editor language indicators,
all the different missing/additional '-' characters, files that center the file name, missing
trailing `===//` (mostly caused by clang-format breaking the line).
Reviewers: aprantl, espindola, jfb, shafik, JDevlieghere
Reviewed By: JDevlieghere
Subscribers: dexonsmith, wuzish, emaste, sdardis, nemanjai, kbarton, MaskRay, atanasyan, arphaman, jfb, abidh, jsji, JDevlieghere, usaxena95, lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D73258
2020-01-24 15:23:27 +08:00
|
|
|
//===-- StreamString.cpp --------------------------------------------------===//
|
2010-06-09 00:52:24 +08:00
|
|
|
//
|
2019-01-19 16:50:56 +08:00
|
|
|
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
|
|
// See https://llvm.org/LICENSE.txt for license information.
|
|
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
2010-06-09 00:52:24 +08:00
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
2017-02-03 05:39:50 +08:00
|
|
|
#include "lldb/Utility/StreamString.h"
|
2010-06-09 00:52:24 +08:00
|
|
|
|
|
|
|
using namespace lldb;
|
|
|
|
using namespace lldb_private;
|
|
|
|
|
|
|
|
StreamString::StreamString() : Stream(0, 4, eByteOrderBig) {}
|
|
|
|
|
|
|
|
StreamString::StreamString(uint32_t flags, uint32_t addr_size,
|
|
|
|
ByteOrder byte_order)
|
|
|
|
: Stream(flags, addr_size, byte_order), m_packet() {}
|
|
|
|
|
2021-07-03 02:27:37 +08:00
|
|
|
StreamString::~StreamString() = default;
|
2010-06-09 00:52:24 +08:00
|
|
|
|
|
|
|
void StreamString::Flush() {
|
|
|
|
// Nothing to do when flushing a buffer based stream...
|
|
|
|
}
|
|
|
|
|
Add byte counting mechanism to LLDB's Stream class.
Summary:
This patch allows LLDB's Stream class to count the bytes it has written to so far.
There are two major motivations for this patch:
The first one is that this will allow us to get rid of all the handwritten byte counting code
we have in LLDB so far. Examples for this are pretty much all functions in LLDB that
take a Stream to write to and return a size_t, which usually represents the bytes written.
By moving to this centralized byte counting mechanism, we hopefully can avoid some
tricky errors that happen when some code forgets to count the written bytes while
writing something to a stream.
The second motivation is that this is needed for the migration away from LLDB's `Stream`
and towards LLVM's `raw_ostream`. My current plan is to start offering a fake raw_ostream
class that just forwards to a LLDB Stream.
However, for this raw_ostream wrapper we need to fulfill the raw_ostream interface with
LLDB's Stream, which currently lacks the ability to count the bytes written so far (which
raw_ostream exposes by it's `tell()` method). By adding this functionality it is trivial to start
rolling out our raw_ostream wrapper (and then eventually completely move to raw_ostream).
Also, once this fake raw_ostream is available, we can start replacing our own code writing
to LLDB's Stream by LLVM code writing to raw_ostream. The best example for this is the
LEB128 encoding we currently ship, which can be replaced with by LLVM's version which
accepts an raw_ostream.
From the point of view of the pure source changes this test does, we essentially just renamed
the Write implementation in Stream to `WriteImpl` while the `Write` method everyone is using
to write its raw bytes is now just forwarding and counting the written bytes.
Reviewers: labath, davide
Reviewed By: labath
Subscribers: JDevlieghere, lldb-commits
Differential Revision: https://reviews.llvm.org/D50159
llvm-svn: 338733
2018-08-03 00:38:34 +08:00
|
|
|
size_t StreamString::WriteImpl(const void *s, size_t length) {
|
2020-01-07 19:13:03 +08:00
|
|
|
m_packet.append(static_cast<const char *>(s), length);
|
2010-06-09 00:52:24 +08:00
|
|
|
return length;
|
|
|
|
}
|
|
|
|
|
Add byte counting mechanism to LLDB's Stream class.
Summary:
This patch allows LLDB's Stream class to count the bytes it has written to so far.
There are two major motivations for this patch:
The first one is that this will allow us to get rid of all the handwritten byte counting code
we have in LLDB so far. Examples for this are pretty much all functions in LLDB that
take a Stream to write to and return a size_t, which usually represents the bytes written.
By moving to this centralized byte counting mechanism, we hopefully can avoid some
tricky errors that happen when some code forgets to count the written bytes while
writing something to a stream.
The second motivation is that this is needed for the migration away from LLDB's `Stream`
and towards LLVM's `raw_ostream`. My current plan is to start offering a fake raw_ostream
class that just forwards to a LLDB Stream.
However, for this raw_ostream wrapper we need to fulfill the raw_ostream interface with
LLDB's Stream, which currently lacks the ability to count the bytes written so far (which
raw_ostream exposes by it's `tell()` method). By adding this functionality it is trivial to start
rolling out our raw_ostream wrapper (and then eventually completely move to raw_ostream).
Also, once this fake raw_ostream is available, we can start replacing our own code writing
to LLDB's Stream by LLVM code writing to raw_ostream. The best example for this is the
LEB128 encoding we currently ship, which can be replaced with by LLVM's version which
accepts an raw_ostream.
From the point of view of the pure source changes this test does, we essentially just renamed
the Write implementation in Stream to `WriteImpl` while the `Write` method everyone is using
to write its raw bytes is now just forwarding and counting the written bytes.
Reviewers: labath, davide
Reviewed By: labath
Subscribers: JDevlieghere, lldb-commits
Differential Revision: https://reviews.llvm.org/D50159
llvm-svn: 338733
2018-08-03 00:38:34 +08:00
|
|
|
void StreamString::Clear() {
|
|
|
|
m_packet.clear();
|
|
|
|
m_bytes_written = 0;
|
|
|
|
}
|
2010-06-09 00:52:24 +08:00
|
|
|
|
2012-05-30 04:04:10 +08:00
|
|
|
bool StreamString::Empty() const { return GetSize() == 0; }
|
|
|
|
|
2010-06-09 00:52:24 +08:00
|
|
|
size_t StreamString::GetSize() const { return m_packet.size(); }
|
|
|
|
|
2014-10-11 07:07:36 +08:00
|
|
|
size_t StreamString::GetSizeOfLastLine() const {
|
|
|
|
const size_t length = m_packet.size();
|
|
|
|
size_t last_line_begin_pos = m_packet.find_last_of("\r\n");
|
|
|
|
if (last_line_begin_pos == std::string::npos) {
|
|
|
|
return length;
|
|
|
|
} else {
|
|
|
|
++last_line_begin_pos;
|
|
|
|
return length - last_line_begin_pos;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2016-11-17 05:15:24 +08:00
|
|
|
llvm::StringRef StreamString::GetString() const { return m_packet; }
|
2010-06-09 00:52:24 +08:00
|
|
|
|
2012-05-10 10:52:23 +08:00
|
|
|
void StreamString::FillLastLineToColumn(uint32_t column, char fill_char) {
|
|
|
|
const size_t length = m_packet.size();
|
|
|
|
size_t last_line_begin_pos = m_packet.find_last_of("\r\n");
|
|
|
|
if (last_line_begin_pos == std::string::npos) {
|
|
|
|
last_line_begin_pos = 0;
|
|
|
|
} else {
|
|
|
|
++last_line_begin_pos;
|
|
|
|
}
|
|
|
|
|
|
|
|
const size_t line_columns = length - last_line_begin_pos;
|
|
|
|
if (column > line_columns) {
|
|
|
|
m_packet.append(column - line_columns, fill_char);
|
2016-09-07 04:57:50 +08:00
|
|
|
}
|
|
|
|
}
|