On 01/21/2016 04:19 PM, Jason Merrill wrote:
Can we reconsider the representation of flexible arrays? Following the example of the C front-end is causing a lot of trouble, and using a null TYPE_DOMAIN seems more intuitive.
I remember running into at least one ICE in the middle end with the alternate representation (null TYPE_DOMAIN). At this late stage I would worry about the fallout from that. It seems that outside of 69251 and 69277 the problems are mostly triggered by ill-formed code that wasn't being tested and I'm hoping that the problems in the well-formed cases have been reported (and with the patches I've sent fixed). At the same time, based on some debugging I had to do for 69251 (ICE in unify_array_domain on a flexible array member) it seems that it might make handling them in template easier. Martin
