[llvm-commits] [Review] Attributes Documentation

[James Molloy]

Hi Bill,

I'm not worried about the technical feasibility of any solution; rather
that without careful thought this might prove a step *backwards* in
terms of user-readability and debuggability.

Cheers,

James

On Thu, 2012-12-06 at 20:39 +0000, Bill Wendling wrote:
> On Dec 6, 2012, at 12:55 AM, James Molloy <James.Molloy at arm.com> wrote:
>
> > Hi Bill,
> >
> > On Thu, 2012-12-06 at 02:01 +0000, Bill Wendling wrote:
> >> In practice, there won't be a large number of differences between
> >> functions. The attributes come about in only a few ways:
> >>
> >>        - through command line options
> >>        - via '__attribute__' declarations
> >
> > You forget compiler-added annotations such as
> > readonly/readnone/noreturn, which can serve as analysis markers. These
> > can get added during optimization passes, so your IR attribute groups
> > are going to change during optimization passes (eww).
> >
> I forgot about those. But yes, they're changeable. And that's fine. They'll just be given a new attributes object or added onto a list (or set) of attribute objects. The internal representation is still in flux right now. :)
>
> -bw
>
>
>
>


-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.