https://bugs.llvm.org/show_bug.cgi?id=44748
Bug ID: 44748
Summary: ObjectFile/ELF tests fail due to mismatched ID
Product: lldb
Version: 10.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
P
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
On Thu, 2020-01-30 at 14:38 -0500, Hans Wennborg via Release-testers
wrote:
>
Please file bug reports for any issues you find as blockers of
> https://llvm.org/pr44555
>
> Release testers: please start your engines, run the script, share your
> results, and upload binaries.
>
Gentoo/amd64 issue
On 30 Jan 2020, at 20:38, Hans Wennborg via Release-testers
wrote:
>
> It took a bit longer than planned due to master being a somewhat
> unstable at the branch point, but Release Candidate 1 has now been
> tagged as llvmorg-10.0.0-rc1.
For this rc, I used three patches, which are attached.
Ma
https://bugs.llvm.org/show_bug.cgi?id=44736
Jonas Devlieghere changed:
What|Removed |Added
Assignee|lldb-dev@lists.llvm.org |jdevliegh...@apple.com
--
You are receivin
https://bugs.llvm.org/show_bug.cgi?id=44736
Bug ID: 44736
Summary: Incorrect use of llvm::toStringRef in TypeSystem.cpp
Product: lldb
Version: 10.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
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 (although less than two weeks
> seems like a rather
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 (although less than two
weeks seems like a rather ambitious time to switch over...). If it can't,
then I'd
