[Lldb-commits] [PATCH] Fix type detection for 'char' when it is unsigned

[Zachary Turner]

unit test?

On Thu, Mar 26, 2015 at 11:50 AM, Tamas Berghammer <tberghammer at google.com>
wrote:

>
> Based on it I still believe if the dwarf file contains a basic type with
> name "char" and it is a DW_ATE_unsigned_char then CharTy will be
> initialized to Char_U and everything will work fine and the user will see
> the type name defined in the dwarf file ("char"). If you want I can add a
> check (possibly an assert) to verify that we hit this case only when
> ASTContext.LangOpts.CharIsSigned is false (if it is not true then the dwarf
> file or lldb is broken).
>
>
Or a unit test.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20150326/061105b9/attachment.html>