{"push_id":1392506600,"size":1,"distinct_size":0,"ref":"refs/heads/swift-3.1-branch","head":"ab8e654235726bf1debd8a028cdbce56635a39b2","before":"07eb96d269c563a999fd502ebb2558a99166229b","commits":[{"sha":"ab8e654235726bf1debd8a028cdbce56635a39b2","author":{"name":"Adrian Prantl","email":"3b76fbf1c74594027f839a53c333f1ac0d409492@apple.com"},"message":"Emit the DW_AT_type for a C++ static member definition\nif it is more specific than the one in its DW_AT_specification.\n\nIf a static member is an array, the translation unit containing the\nmember definition may have a more specific type (including its length)\nthan TUs only seeing the class declaration. This patch adds a\nDW_AT_type to the member's DW_TAG_variable in addition to the\nDW_AT_specification in these cases. The member type in the\nDW_AT_specification still shows the more generic type (without the\nlength) to avoid defeating type uniquing.\n\nThe DWARF standard discourages “duplicating” a DW_AT_type in a member\nvariable definition but doesn’t explicitly forbid it.  Having the more\nspecific type (with the array length) available is what allows the\ndebugger to print the contents of a static array member variable.\n\nhttps://reviews.llvm.org/D26368\nrdar://problem/28706946\n\ngit-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@286302 91177308-0d34-0410-b5e6-96231b3b80d8\n(cherry picked from commit bb82f0a4b070c40c2e7d840ca5f6dad6422a34f4)","distinct":false,"url":"https://api.github.com/repos/gottesmm/swift-llvm/commits/ab8e654235726bf1debd8a028cdbce56635a39b2"}]}
{"actor":{"display_login":"gottesmm"}}