search for: bintzeng

...e calls to free at the predecessors of dominance frontier is inadequate. It is possible that there are exit blocks that are dominated by BB12 (calls to malloc). I guess we can also insert calls to free at these exit blocks too. > H. > > > On Tue, Nov 12, 2013 at 11:30 PM, Bin Tzeng <bintzeng at gmail.com> wrote: > >> Hi all, >> >> I have been writing a pass to heapify some alloca's (it is >> pessimistization, not optimization). For example, in the following control >> flow graph, there is a call to malloc inserted in block BB12. In order to >&...

...calculates the > "availability frontier" which is probably what you're looking for. > I suggest, however, that you try coming up with another solution instead. > You might consider using -mergereturn. > > H. > > > On Wed, Nov 13, 2013 at 2:13 AM, Bin Tzeng <bintzeng at gmail.com> wrote: > >> Hi Henrique, >> Thanks for the quick reply! >> >> On Tue, Nov 12, 2013 at 9:13 PM, Henrique Santos < >> henrique.nazare.santos at gmail.com> wrote: >> >>> PRE normally uses a latest placement algorithm to do somethin...

...d, PRE.cpp existed last at r25315. It calculates the "availability frontier" which is probably what you're looking for. I suggest, however, that you try coming up with another solution instead. You might consider using -mergereturn. H. On Wed, Nov 13, 2013 at 2:13 AM, Bin Tzeng <bintzeng at gmail.com> wrote: > Hi Henrique, > Thanks for the quick reply! > > On Tue, Nov 12, 2013 at 9:13 PM, Henrique Santos < > henrique.nazare.santos at gmail.com> wrote: > >> PRE normally uses a latest placement algorithm to do something of the >> sort. >>...

...calculates the > "availability frontier" which is probably what you're looking for. > I suggest, however, that you try coming up with another solution instead. > You might consider using -mergereturn. > > H. > > > On Wed, Nov 13, 2013 at 2:13 AM, Bin Tzeng <bintzeng at gmail.com> wrote: > >> Hi Henrique, >> Thanks for the quick reply! >> >> On Tue, Nov 12, 2013 at 9:13 PM, Henrique Santos < >> henrique.nazare.santos at gmail.com> wrote: >> >>> PRE normally uses a latest placement algorithm to do somethin...

...er block where a call to free() was inserted without going back to BB10 again. I hope this reasoning make sense. : ) Also, you might also have to treat the special case in which the block where the malloc() is placed dominates the return block. H. On Fri, Nov 15, 2013 at 2:29 AM, Bin Tzeng <bintzeng at gmail.com> wrote: > Hi Henrique, > > I have tried using -mergereturn and inserting a free into the predecessors > of dominance frontier of malloc block and it caused double free. It is > possible for multiple free's to be inserted on the path from malloc to an > exit. F...

...ich is probably what you're looking > for. > > I suggest, however, that you try coming up with another solution > instead. You might consider using -mergereturn. > > > > > > H. > > > > > > On Wed, Nov 13, 2013 at 2:13 AM, Bin Tzeng < bintzeng at gmail.com > > wrote: > > > > > Hi Henrique, > Thanks for the quick reply! > > > > > On Tue, Nov 12, 2013 at 9:13 PM, Henrique Santos < > henrique.nazare.santos at gmail.com > wrote: > > > > > > > PRE normally uses...

On Jun 20, 2013, at 4:39 PM, Bin Tzeng <bintzeng at gmail.com> wrote: > Hi all, > > There might be a simple error in the LLVM reference manual. The example for sext instruction: > > %X = sext i8 -1 to i16 ; yields i16 :65535 > > %X should yield i16: -1, as opposed to 65535. > Here is the simple patch (also at...

15.06.2013, 00:53, "Bin Tzeng" <bintzeng at gmail.com>: > It is interesting. I can see some use cases with such a tool. To me, source-level implementation > is not as accurate as binary translation. For instance, it is hard to check the taint for return addresses > since there is no concept of return instructions on source lev...

Hi all, There might be a simple error in the LLVM reference manual. The example for sext instruction: %X = sext i8 -1 to i16 ; yields i16 :65535 %X should yield i16: -1, as opposed to 65535. Here is the simple patch (also attached): Index: docs/LangRef.rst =================================================================== --- docs/LangRef.rst (revision 184496) +++ docs/LangRef.rst

...the sort. I don't know about GVN/PRE, but older version of PRE might have it. Just placing the calls to free at the predecessors (dominated by BB12) of the dominance frontier of BB12 seems to work, however. Is there anything wrong with this? H. On Tue, Nov 12, 2013 at 11:30 PM, Bin Tzeng <bintzeng at gmail.com> wrote: > Hi all, > > I have been writing a pass to heapify some alloca's (it is > pessimistization, not optimization). For example, in the following control > flow graph, there is a call to malloc inserted in block BB12. In order to > avoid memory leak, free&...

Hi all, I have been writing a pass to heapify some alloca's (it is pessimistization, not optimization). For example, in the following control flow graph, there is a call to malloc inserted in block BB12. In order to avoid memory leak, free's are needed. The free cannot be inserted in BB23 because BB23 is not dominated by BB12. There are two ways to go I can think of here. One way is to

Thanks for the reply. Just for a little more clarity, is i16, i32... signed, unsigned, or just a bit pattern? On Thu, Jun 20, 2013 at 9:17 PM, Chris Lattner <clattner at apple.com> wrote: > > On Jun 20, 2013, at 4:39 PM, Bin Tzeng <bintzeng at gmail.com> wrote: > > > Hi all, > > > > There might be a simple error in the LLVM reference manual. The example > for sext instruction: > > > > %X = sext i8 -1 to i16 ; yields i16 :65535 > > > > %X should yield i16: -1, as opposed to 6553...

Hi all, LLVM is smart that it can synthesize llvm.memset, llvm.memcpy etc. from loops, which can be lowered into calls to memset, memcpy and so on. Is there an option that can disable this optimization? For some cases, I do not want the code to depend on libc. Thanks in advance! Bin -------------- next part -------------- An HTML attachment was scrubbed... URL:

It is interesting. I can see some use cases with such a tool. To me, source-level implementation is not as accurate as binary translation. For instance, it is hard to check the taint for return addresses since there is no concept of return instructions on source level. The stack does not appear until later. For a security mechanism, return addresses need to be protected. On Fri, Jun 14, 2013 at

On Thu, Jun 13, 2013 at 03:13:37PM -0700, Sean Silva wrote: > Could you maybe give some example use cases? A use case I am interested in is to take a large application and use this instrumentation as a tool to help monitor how data flows from its inputs (sources) to its outputs (sinks). This has applications from a privacy/security perspective in that one can audit how a sensitive data item