06d40de8bb
2007-01-02 Douglas Gregor <doug.gregor@gmail.com> * c-common.c(c_common_nodes_and_builtins): Since variants of void_type_node get built before it is given a name, we need to give those variants the name, too. (complete_array_type): We need to work with the canonical main type of the array, from which we will build the qualified version. * params.def (PARAM_VERIFY_CANONICAL_TYPES): New. * print-tree.c (print_node): Display canonical type information for each type. * stor-layout.c (layout_type): When we don't know the alignment of a type for which we're building an array, we end up guessing wrong, so make the type require structural equality. * tree.c (make_node_stat): When we build a new type, it is its own canonical type. (build_type_attribute_qual_variant): When building an attribute variant, its canonical type is the non-attribute variant. However, if the attributes are target-dependent and they differ, we need to use structural equality checks for this type. (build_qualified_type): A qualified type is not equivalent to its unqualified variant; set the canonical type appropriately. (build_distinct_type_copy): When building a distinct type from another type, the new type is its own canonical type. (build_variant_type_copy): When building a new type variant, we assume that it is equivalent to the original type. (build_pointer_type_for_mode): When building a pointer type, also build a canonical type pointer. (build_reference_type_for_mode): When building a reference type, also build a canonical type reference. (build_index_type): When we can't hash an index type (e.g., because its maximum value is negative), the index type requires structural equality tests. (build_array_type): Build the canonical form of an array type. (build_function_type): Function types require structural equality, because they contain default arguments, attributes, etc. (build_method_type_directly): Ditto for method types. (build_offset_type): Build the canonical offset type. (build_complex_type): Build the canonical vector type. (make_vector_type): Build the canonical vector type. * tree.h (TYPE_CANONICAL): New. (TYPE_STRUCTURAL_EQUALITY_P): New. (SET_TYPE_STRUCTURAL_EQUALITY): New. (struct tree_type): Added "canonical" field. * params.h (VERIFY_CANONICAL_TYPES): New. * doc/c-tree.texi (TYPE_CANONICAL): Document. (TYPE_STRUCTURAL_EQUALITY_P): Document. (SET_TYPE_STRUCTURAL_EQUALITY): Document. * doc/invoke.texi (verify-canonical-types): Document --param parameter for verifying canonical types. 2007-01-02 Douglas Gregor <doug.gregor@gmail.com> * typeck.c (structural_comptypes): Renamed from "comptypes". (comptypes): Use canonical type information to perform fast type comparison. When VERIFY_CANONICAL_TYPES, verify that the canonical type comparison returns the same results as we would see from the current, structural check. Support COMPARE_STRUCTURAL when we need structural checks. * decl.c (typename_compare): Fix comment. (build_typename_type): TYPENAME_TYPE nodes require structural equality checks, because they resolve different based on the current class type. (make_unbound_class_template): UNBOUND_CLASS_TEMPLATE nodes require structural equality checks (for now). (build_ptrmemfunc_type): Build the canonical pointer to member function type. (compute_array_index_type): Whenever we build a new index type to represent the size of an array in a template, we need to mark this index type as requiring structural equality. This goes for arrays with value-dependent sizes with the current ABI, or all arrays with ABI-1. * tree.c (cplus_array_hash): New. (struct cplus_array_info): New. (cplus_array_compare): New. (cplus_array_htab): New. (build_cplus_array_type_1): Use a hash table to cache the array types we build. Build the canonical array type for each array type. (cp_build_qualified_type_real): When building a cv-qualified array type, use the hash table of array types and build canonical array types as necessary. (bind_template_template_parm): BOUND_TEMPLATE_TEMPLATE_PARM nodes use structural equality (for now). * cp-tree.h (COMPARE_STRUCTURAL): New. * pt.c (canonical_template_parms): New. (canonical_type_parameter): New. (process_template_parm): Find the canonical type parameter. (lookup_template_class): When we have named the primary template type, set the canonical type for our template class to the primary template type. If any of the template arguments need structural equality checks, the template class needs structural equality checks. (tsubst): When reducing the level of a template template parameter, we require structural equality tests for the resulting parameter because its template parameters have not had their types canonicalized. When reducing a template type parameter, find the canonical reduced type parameter. (any_template_arguments_need_structural_equality_p): New. 2007-01-02 Douglas Gregor <doug.gregor@gmail.com> * objc-act.c (objc_build_volatilized_type): Keep track of canonical types. (objc_get_protocol_qualified_type): Ditto. From-SVN: r120341 |
||
|---|---|---|
| .. | ||
| ChangeLog | ||
| Make-lang.in | ||
| README | ||
| config-lang.in | ||
| lang-specs.h | ||
| objc-act.c | ||
| objc-act.h | ||
| objc-lang.c | ||
| objc-tree.def | ||
README
GNU Objective C notes ********************* This document is to explain what has been done, and a little about how specific features differ from other implementations. The runtime has been completely rewritten in gcc 2.4. The earlier runtime had several severe bugs and was rather incomplete. The compiler has had several new features added as well. This is not documentation for Objective C, it is usable to someone who knows Objective C from somewhere else. Runtime API functions ===================== The runtime is modeled after the NeXT Objective C runtime. That is, most functions have semantics as it is known from the NeXT. The names, however, have changed. All runtime API functions have names of lowercase letters and underscores as opposed to the `traditional' mixed case names. The runtime api functions are not documented as of now. Someone offered to write it, and did it, but we were not allowed to use it by his university (Very sad story). We have started writing the documentation over again. This will be announced in appropriate places when it becomes available. Protocols ========= Protocols are now fully supported. The semantics is exactly as on the NeXT. There is a flag to specify how protocols should be typechecked when adopted to classes. The normal typechecker requires that all methods in a given protocol must be implemented in the class that adopts it -- it is not enough to inherit them. The flag `-Wno-protocol' causes it to allow inherited methods, while `-Wprotocols' is the default which requires them defined. +initialize =========== This method, if defined, is called before any other instance or class methods of that particular class. This method is not inherited, and is thus not called as initializer for a subclass that doesn't define it itself. Thus, each +initialize method is called exactly once (or never if no methods of that particular class is never called). Besides this, it is allowed to have several +initialize methods, one for each category. The order in which these (multiple methods) are called is not well defined. I am not completely certain what the semantics of this method is for other implementations, but this is how it works for GNU Objective C. Passivation/Activation/Typedstreams =================================== This is supported in the style of NeXT TypedStream's. Consult the headerfile Typedstreams.h for api functions. I (Kresten) have rewritten it in Objective C, but this implementation is not part of 2.4, it is available from the GNU Objective C prerelease archive. There is one difference worth noting concerning objects stored with objc_write_object_reference (aka NXWriteObjectReference). When these are read back in, their object is not guaranteed to be available until the `-awake' method is called in the object that requests that object. To objc_read_object you must pass a pointer to an id, which is valid after exit from the function calling it (like e.g. an instance variable). In general, you should not use objects read in until the -awake method is called. Acknowledgements ================ The GNU Objective C team: Geoffrey Knauth <gsk@marble.com> (manager), Tom Wood <wood@next.com> (compiler) and Kresten Krab Thorup <krab@iesd.auc.dk> (runtime) would like to thank a some people for participating in the development of the present GNU Objective C. Paul Burchard <burchard@geom.umn.edu> and Andrew McCallum <mccallum@cs.rochester.edu> has been very helpful debugging the runtime. Eric Herring <herring@iesd.auc.dk> has been very helpful cleaning up after the documentation-copyright disaster and is now helping with the new documentation. Steve Naroff <snaroff@next.com> and Richard Stallman <rms@gnu.ai.mit.edu> has been very helpful with implementation details in the compiler. Bug Reports =========== Please read the section `Submitting Bugreports' of the gcc manual before you submit any bugs.