search for: annoat

...robust even in the case of version mismatches between consumers and producers. That is, the syntax generally does not carry semantics beyond "this text has an annotation," so consumers can simply ignore annotations they do not understand or do not care about. ** Instruction Annotations Annoated assembly display will supply contextual markup to help clients more efficiently implement things like pretty printers. Most markup will be target independent, so clients can effectively provide good display without any target specific knowledge. Annotated assembly goes through the normal instruc...

...e case of version mismatches between consumers and producers. That is, the syntax generally does not carry semantics beyond "this text has an annotation," so consumers can simply ignore annotations they do not understand or do not care about. > > ** Instruction Annotations > > Annoated assembly display will supply contextual markup to help clients more efficiently implement things like pretty printers. Most markup will be target independent, so clients can effectively provide good display without any target specific knowledge. > > Annotated assembly goes through the norma...

...gards to redefining the current MD_prof. I'd encourage you to post a patch for the entry count mechanism, but not tie its semantics to exact execution count. (Something like "the value provided must correctly describe the relative hotness of this routine against others in the program annoatated with the same metadata. It is the relative scaling that is important, not the absolute value. In particular, the value need not be an exact execution count.") > > > Many of the other issues you raise seem like they could also be > addressed without major changes to...

...- AnnotationType - Name NULL values are wildcards. So you could say: Give me all annotations for a Value* /// Function local annotations Value* v = ... vector< const Annotation *> &ans = curFunction->lookupAnnotation( v, NULL, NULL); Or based on a specific type: /// Module wide annoations AnnotationType *type = ... Value< const Annotation *> &ans = module->lookupAnnotation( v, type, NULL ); This just random thought though. > >>>As a historical curiosity, Function still needs to be annotatable due to >>>the LLVM code generator relying on it....

...mismatches between consumers and producers. That is, the syntax generally does not carry semantics beyond "this text has an annotation," so consumers can simply ignore annotations they do not understand or do not care about. >> >> ** Instruction Annotations >> >> Annoated assembly display will supply contextual markup to help clients more efficiently implement things like pretty printers. Most markup will be target independent, so clients can effectively provide good display without any target specific knowledge. >> >> Annotated assembly goes through...

...producers. That is, the syntax generally does not carry semantics beyond "this text has an annotation," so consumers can simply ignore annotations they do not understand or do not care about. >>>> >>>> ** Instruction Annotations >>>> >>>> Annoated assembly display will supply contextual markup to help clients more efficiently implement things like pretty printers. Most markup will be target independent, so clients can effectively provide good display without any target specific knowledge. >>>> >>>> Annotated assemb...

...ween consumers and producers. That is, the syntax generally does not carry semantics beyond "this text has an annotation," so consumers can simply ignore annotations they do not understand or do not care about. >>> >>> ** Instruction Annotations >>> >>> Annoated assembly display will supply contextual markup to help clients more efficiently implement things like pretty printers. Most markup will be target independent, so clients can effectively provide good display without any target specific knowledge. >>> >>> Annotated assembly goes t...

...t; So you could say: > > Give me all annotations for a Value* > > /// Function local annotations > Value* v = ... > vector< const Annotation *> &ans = curFunction->lookupAnnotation( v, > NULL, NULL); > > Or based on a specific type: > > /// Module wide annoations > AnnotationType *type = ... > Value< const Annotation *> &ans = module->lookupAnnotation( v, type, NULL ); > > This just random thought though. > > > > >>>As a historical curiosity, Function still needs to be annotatable due to > >>>the...

Hi, Using 2.2.9 (ubuntu 14.04 LTS) and sending the following command, the server crashes when I try to delete an annotation: ? login ? C: 2 setannotation Trash "/vendor/cmu/cyrus-imapd/expire" ("value.shared" NIL) Apr 27 09:29:16 backend1 dovecot: imap-login: Login: user=<heiko>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=6651, secured Apr 27 09:29:16 backend1

...at is, the syntax generally does not carry semantics beyond "this text has an annotation," so consumers can simply ignore annotations they do not understand or do not care about. >>>>> >>>>> ** Instruction Annotations >>>>> >>>>> Annoated assembly display will supply contextual markup to help clients more efficiently implement things like pretty printers. Most markup will be target independent, so clients can effectively provide good display without any target specific knowledge. >>>>> >>>>> Annotated...

...>> >> I'd encourage you to post a patch for the entry count mechanism, but not tie >> its semantics to exact execution count. (Something like "the value provided >> must correctly describe the relative hotness of this routine against others >> in the program annoatated with the same metadata. It is the relative >> scaling that is important, not the absolute value. In particular, the value >> need not be an exact execution count.") >> >> >>> >>> Many of the other issues you raise seem like they could also be...

Hi Jakob, I have some thoughts on this too .. On Fri, 2006-02-24 at 19:56 +0100, Jakob Praher wrote: > I get you 100 % here. But as you say later in the mail, many information > is done by some runtime std::map<Value*,foo> stuff. Which is really > handy at runtime, but I *had* serialization in mind when I was thinking > about Annotations. I see annotations as a way to serialize

...x generally does not carry semantics beyond "this text has an annotation," so consumers can simply ignore annotations they do not understand or do not care about. >>>>>> >>>>>> ** Instruction Annotations >>>>>> >>>>>> Annoated assembly display will supply contextual markup to help clients more efficiently implement things like pretty printers. Most markup will be target independent, so clients can effectively provide good display without any target specific knowledge. >>>>>> >>>>>> A...

...;Give me all annotations for a Value* >> >>/// Function local annotations >>Value* v = ... >>vector< const Annotation *> &ans = curFunction->lookupAnnotation( v, >>NULL, NULL); >> >>Or based on a specific type: >> >>/// Module wide annoations >>AnnotationType *type = ... >>Value< const Annotation *> &ans = module->lookupAnnotation( v, type, NULL ); >> >>This just random thought though. >> >> >>>>>As a historical curiosity, Function still needs to be annotatable due to &...

hi Chris! thanks for your reply. First of all I did not know about the history with the Annotation stuff. Annotable for me was a way how one could realize this things. So as I see it right now - it is more that Annotable will completly vanish soon. This is interesting to me. Chris Lattner schrieb: > On Fri, 24 Feb 2006, Jakob Praher wrote: > >> When translating a complex c

> On Mar 2, 2015, at 4:19 PM, Diego Novillo <dnovillo at google.com> wrote: > > On Thu, Feb 26, 2015 at 6:54 PM, Diego Novillo <dnovillo at google.com <mailto:dnovillo at google.com>> wrote: > > I've created a few bugzilla issues with details of some of the things I'll be looking into. I'm not yet done wordsmithing the overall design document.