Summary document

[Christophe de Dinechin]

Hi Jim,


I have a few questions regarding the proposed issues list.

Classification:
Could you please detail what the gABI and psABI are?


A5: Empty parameters
What does that mean? That's not a term used in the standard. I guess  
it is either empty parameter list (K&R style), default arguments  
(but I don't see what the problem would be here) or passing empty  
classes (again, I don't see exactly what the problem could be).


I also would like to add a few issues to your list:

A7: Primary base class optimization / Selection of primary base class
A8: Alignment constraints on bases / virtual bases
A9: Sorting of class fields as allowed by [class.mem]/12
A10: Structure field promotion / passing structs as registers

B3: Optimizing for unchanged vptr using a predicate bit
B4: What do vtable entries point to (function entry vs. function  
descriptor)
B5: Where are vtables emitted ("key function")

C2: Order of construction/destruction wrt link command
C3: Order of construction/destruction wrt shared libraries

D5: Interoperability with other languages (Java in particular)
D5-bis: Allowing resumption?
D6: Interaction with signals or asynchronous events

E3: Templates repository
E4: Template separation model (maybe that's what you mean with E2)


And, since our goal is to make customers happy, why not also try to  
agree on a set of common command line options (for historical  
reasons, we could say that you need a different driver for those, or  
a special switch to turn on a "compatible" mode)


Best Regards
Christophe de Dinechin