I presume you already look for CPU::FlushICache. Immediate values stored in literal pools do not require cache sync when patched, maybe start with Assembler::set_target_address and similar.
Rodolph. On 4 June 2014 20:07, Hendrik Greving <[email protected]> wrote: > I am looking for a way to determine from the V8 engine when we edit > (patch) existing crankshafted code, as well as possibly just moving > optimized code (e.g. from garbage collection). I also like to understand > what we're doing, e.g. distinguishing patching pointer literals and > changing code for deoptimization by changing instructions altogether (by > inserting branches). Any help, papers, summarizes, hints to the source code > (e.g. CodePatcher?) greatly appreciated! > > Thanks, > Hendrik Greving > > -- > -- > v8-dev mailing list > [email protected] > http://groups.google.com/group/v8-dev > --- > You received this message because you are subscribed to the Google Groups > "v8-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
