[ccan] dgraph, tlist, tcon: MSVC error due to array of flexible structs

David Gibson david at gibson.dropbear.id.au
Tue Sep 27 14:45:56 AEST 2016


On Thu, Sep 22, 2016 at 10:31:16PM -0600, Kevin Locke wrote:
> Hi all,
> 
> Building dgraph using Microsoft Visual C++ produces the following
> error:
> 
> dgraph.h(25): error C2233: 'edge': arrays of objects containing
> zero-size arrays are illegal
> 
> The issue is that MSVC supports flexible array members, but does not
> support arrays of structs with flexible array members.

Right, which actually makes sense - how can you have an array when you
have no way of knowing how much space to allocate for the flexible
members.

In fact what TCON really wants here is a true 0-element array, rather
than a flexible array member, which is not something supported by the
C standard, or many compilers, although gcc has it (predating standard
flexible members).

> My
> understanding is that such support is not required by C99 or C11, but
> I don't know whether such support is common beyond Clang/GCC.
> 
> Is there any interest in supporting such compilers?  If so, I can see
> a few potential fixes:
> 
> 1. Change TCON to use flexible array members only when the compiler
> supports arrays of structs with flexible array members.  This is an
> easy fix, but wastes space for every TCON/TLIST usage on such
> compilers.
> 
> 2. Have TCON (and TLIST) provide an alternative macro which uses
> flexible array members only when supported in arrays, and use that in
> dgraph.  It would increase the API and duplicate a bit of code, but
> would only waste space when TCON/TLIST are placed in arrays.
> 
> 2. Replace the 2-element edge array in struct dgraph_node with
> separate fields edge_from and edge_to.  This complicates the logic a
> bit, since it is no longer symmetric with dgraph_edge.  It would also
> be an incompatible API change.

C11 only allows flexible array members as the last element of a
structure for obvious reasons.  For the same reason, a structure
containing a flexible array member is only allowed as the last element
of any containing structure.

I doubt the result would work even on gcc (it was exactly this case
that caused me to write TCON_WRAP()).  It's almost certain not to work
on a compiler that doesn't support flexible array members in arrays.

> 3. Change TLIST to use TCON_WRAP?  I don't understand TLIST/TCON well
> enough to know if this is really an option.  Hopefully an expert can
> weigh in here.

So.. in a way this has already been done.  The tlist2 module is
basically exactly like the tlist module, but using TCON_WRAP instead
of TCON.

IIRC, Rusty didn't want to simply replace the tlist module in case
there could be subtle brekages in usage.

So converting dgraph to use tlist2 instead of tlist should do the
trick.

...

I had a quick look at this.  It is a little fiddly.  In addition to
using TCON_WRAP(), tlist2 also uses the tcon_container_of() stuff so
that less arguments are needed when using the lists.

This means that the from and to edge lists would need slightly
different types, so we'd have to implement them as separate fields in
addition to the other changes.  That in turn means there are some
places in draph where we'd have to have an actual if / switch instead
of just looking up the right edge list by the DGRAPH_{FROM,TO} enum.

I don't think there's any showstopper there, just some fiddliness.


So that leaves the question of which is the easier approach:

  * Change dgraph to use tlist2, including separate from and to lists

or

  * Change tlist in place to use TCON_WRAP more minimally (avoid the
    flexible array member, but don't use the TCON_CONTAINER() stuff)

> Thoughts?



-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/ccan/attachments/20160927/e87a04aa/attachment-0001.sig>


More information about the ccan mailing list