r297702 - [CodeGen][ObjC] Fix a bug where the type of an ivar wasn't encoded

Akira Hatanaka via cfe-commits cfe-commits at lists.llvm.org
Mon Jun 26 21:36:45 PDT 2017


This should be fixed in r306364.

> On Jun 22, 2017, at 1:26 PM, Akira Hatanaka <ahatanaka at apple.com> wrote:
> 
> According to the documentation, the starting position of the field has to be encoded too:
> 
> https://gcc.gnu.org/onlinedocs/gcc/Type-encoding.html <https://gcc.gnu.org/onlinedocs/gcc/Type-encoding.html>
> 
> I’m not sure whether we need the same information for bitfield ivars though.
> 
>> On Jun 22, 2017, at 12:03 PM, Joerg Sonnenberger <joerg at bec.de <mailto:joerg at bec.de>> wrote:
>> 
>> On Thu, Jun 22, 2017 at 11:09:48AM -0700, Akira Hatanaka wrote:
>>> Do you want the same encoding for the bitfield “int : 1” you saw before r297792, which is just “i"?
>>> 
>>> The encoding for bitfield is normally bN where N is the number of bits,
>>> but the comment in function EncodeBitField says GNU runtime encodes it differently.
>> 
>> Sorry, can't answer that. I primarily care about a new clang crash that
>> didn't exist before, cut I can't answer what the correct behavior should
>> be.
>> 
>> Joerg
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20170626/6249c591/attachment.html>


More information about the cfe-commits mailing list