[llvm-bugs] [Bug 36055] Reproducible Clang crash + strongly suspected invalid code generation

2018-02-09 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=36055

Hans Wennborg  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #9 from Hans Wennborg  ---
(In reply to Richard Smith from comment #8)
> The particular symptom is a regression, but every prior version of Clang has
> produced a broken AST for that code. Regardless, yes, let's take this fix
> for clang 6; it's low risk and fixes a subtle but nasty bug.

Merged in r324719.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 36055] Reproducible Clang crash + strongly suspected invalid code generation

2018-02-08 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=36055

Hans Wennborg  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #6 from Hans Wennborg  ---
(In reply to Richard Smith from comment #5)
> Fixed in r324537.

Do you think we should merge it to 6.0?

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 36055] Reproducible Clang crash + strongly suspected invalid code generation

2018-02-07 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=36055

Richard Smith  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from Richard Smith  ---
Fixed in r324537.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs