Merge pull request #365 from riscv-non-isa/fix-358

Add note for array with empty struct or union

Author: kito-cheng

riscv-cc.adoc

@@ -270,14 +270,27 @@ hierarchy flattened, including any array fields.  That is, `struct { struct
 { float f[1]; } a[2]; }` and `struct { float f0; float f1; }` are
 treated the same.  Fields containing empty structs or unions are ignored while
 flattening, even in {Cpp}, unless they have nontrivial copy constructors or
-destructors.  Fields containing zero-length bit-fields are ignored while
-flattening.  Attributes such as `aligned` or `packed` do not interfere with a
-struct's eligibility for being passed in registers according to the rules
-below, i.e. `struct { int i; double d; }` and `+struct
+destructors.  Fields containing zero-length bit-fields or zero-length arrays are
+ignored while flattening.  Attributes such as `aligned` or `packed` do not
+interfere with a struct's eligibility for being passed in registers according
+to the rules below, i.e. `struct { int i; double d; }` and `+struct
 __attribute__((__packed__)) { int i; double d }+` are treated the same, as are
 `struct { float f; float g; }` and `+struct { float f; float g __attribute__
 ((aligned (8))); }+`.
 
+NOTE: One exceptional case for the flattening rule is an array of empty
+structs or unions; C treats it as an empty field, but {Cpp}
+treats it as a non-empty field since {Cpp} defines the size of an empty struct
+or union as 1. i.e. for `struct { struct {} e[1]; float f; }` as the first
+argument, C will treat it like `struct { float f; }` and pass `f` in `fa0` as
+described below, whereas {Cpp} will pass the pass the entire aggregate in `a0` 
+(XLEN = 64) or `a0` and `a1` (XLEN = 32), as described in the integer calling
+convention.
+Zero-length arrays of empty structs or union will be
+ignored for both C and {Cpp}. i.e. For `struct { struct {} e[0]; float f; };`,
+as the first argument, C and {Cpp} will treat it like `struct { float f; }`
+and pass `f` in `fa0` as described below.
+
 A real floating-point argument is passed in a floating-point argument
 register if it is no more than ABI_FLEN bits wide and at least one floating-point
 argument register is available.  Otherwise, it is passed according to the