[llvm-commits] [llvm] r137468 - in /llvm/trunk: docs/LangRef.html include/llvm/DerivedTypes.h lib/VMCore/Type.cpp

Eli Friedman eli.friedman at gmail.com
Fri Aug 12 10:40:15 PDT 2011


On Fri, Aug 12, 2011 at 10:31 AM, Chris Lattner <sabre at nondot.org> wrote:
> Author: lattner
> Date: Fri Aug 12 12:31:02 2011
> New Revision: 137468
>
> URL: http://llvm.org/viewvc/llvm-project?rev=137468&view=rev
> Log:
> add new accessors to reflect new terminology in struct types.
>
> Modified:
>    llvm/trunk/docs/LangRef.html
>    llvm/trunk/include/llvm/DerivedTypes.h
>    llvm/trunk/lib/VMCore/Type.cpp
>
> Modified: llvm/trunk/docs/LangRef.html
> URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/LangRef.html?rev=137468&r1=137467&r2=137468&view=diff
> ==============================================================================
> --- llvm/trunk/docs/LangRef.html (original)
> +++ llvm/trunk/docs/LangRef.html Fri Aug 12 12:31:02 2011
> @@ -2031,20 +2031,22 @@
>
>  <p>Structures may optionally be "packed" structures, which indicate that the
>   alignment of the struct is one byte, and that there is no padding between
> -  the elements.  In non-packed structs, padding between field types is defined
> -  by the target data string to match the underlying processor.</p>
> -
> -<p>Structures can either be "anonymous" or "named".  An anonymous structure is
> -  defined inline with other types (e.g. <tt>{i32, i32}*</tt>) and a named types
> -  are always defined at the top level with a name.  Anonmyous types are uniqued
> -  by their contents and can never be recursive since there is no way to write
> -  one.  Named types can be recursive.
> +  the elements.  In non-packed structs, padding between field types is inserted
> +  as defined by the TargetData string in the module, which is required to match
> +  what the underlying processor expects.</p>
> +
> +<p>Structures can either be "literal" or "identified".  A literal structure is
> +  defined inline with other types (e.g. <tt>{i32, i32}*</tt>) whereas identified
> +  types are always defined at the top level with a name.  Literal types are
> +  uniqued by their contents and can never be recursive or opaque since there is
> +  no way to write one.  Named types can be recursive, can be opaqued, and are

"Named types".

-Eli




More information about the llvm-commits mailing list