On 2020-10-08, Greg Clayton via lldb-dev wrote:
Hello LLDB devs,
This is a deep dive into an issue I found in the LLDB handling of DWARF call
frame information, so no need to read further if this doesn't interest you!
I am in the process of adding some support to LLVM for parsing the opcode st
On 2020-09-18, Eric Christopher via lldb-dev wrote:
Hi Walter,
I've only done a brief scan of the document but, in general, I'm favorable
of the goals, aim, and approach. Something I think would be good would be
to compare/contrast against rr as an "exploring alternatives" section of
the documen
On 2020-04-20, Richard Smith via cfe-dev wrote:
On Mon, 20 Apr 2020 at 13:57, Anton Korobeynikov via cfe-dev <
cfe-...@lists.llvm.org> wrote:
> If we are reasonably certain that no one would be opening new issues on
GitHub while the migration is running...
And pull requests (the numbering is co
On 2020-01-30, Anton Korobeynikov via cfe-dev wrote:
Will you be able to start numbering in github at a number larger than the
largest bug in bugzilla? It would be annoying to have overlapping bug numbers.
Bug numbers exist in code comments, list archives, etc., etc. If someone
reads 'clang
On 2020-01-31, Tom Stellard via llvm-dev wrote:
On 01/31/2020 01:21 AM, James Henderson wrote:
My only concern is the ability to get auto-subscribed onto issues for specific
tools (i.e. the setup I currently have). If that can be resolved in a
satisfactory manner, then I'm all for this (althou
