[llvm] r321911 - Re-land "Fix faulty assertion in debug info"

Shoaib Meenai via llvm-commits llvm-commits at lists.llvm.org
Fri Feb 9 02:17:46 PST 2018


Thank you! For what it's worth, my use case was broken with 6.0 (before this merge) but not 5.0, so it was a regression in a loose sense :)

From: <hwennborg at google.com> on behalf of Hans Wennborg <hans at chromium.org>
Date: Friday, February 9, 2018 at 2:07 AM
To: Shoaib Meenai <smeenai at fb.com>
Cc: Adrian McCarthy <amccarth at google.com>, "llvm-commits at lists.llvm.org" <llvm-commits at lists.llvm.org>
Subject: Re: [llvm] r321911 - Re-land "Fix faulty assertion in debug info"

It's a little outside the scope for the release branch in that it's
not fixing a regression, but on the other hand it seems low risk so
why not. Merged in r324723.

Thanks,
Hans

On Fri, Feb 9, 2018 at 10:37 AM, Shoaib Meenai <smeenai at fb.com<mailto:smeenai at fb.com>> wrote:
Could this be merged to 6.0? I'm attempting to use CodeView + DWARF for some
internal builds (DWARF because of legacy tooling and CodeView because VS and
WinDbg are amazing), and I run into tons of assertion failures without this.



From: llvm-commits <llvm-commits-bounces at lists.llvm.org<mailto:llvm-commits-bounces at lists.llvm.org>> on behalf of Adrian
McCarthy via llvm-commits <llvm-commits at lists.llvm.org<mailto:llvm-commits at lists.llvm.org>>
Reply-To: Adrian McCarthy <amccarth at google.com<mailto:amccarth at google.com>>
Date: Friday, January 5, 2018 at 3:02 PM
To: "llvm-commits at lists.llvm.org<mailto:llvm-commits at lists.llvm.org>" <llvm-commits at lists.llvm.org<mailto:llvm-commits at lists.llvm.org>>
Subject: [llvm] r321911 - Re-land "Fix faulty assertion in debug info"



Author: amccarth

Date: Fri Jan  5 15:01:04 2018

New Revision: 321911

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20180209/88738dca/attachment.html>


More information about the llvm-commits mailing list