search for: createglobalvariableexpression

...h such logical variable inside the memory block are known constants. - I'd like to make it possible to access these logical variables inside the debugger as if they are normal global variables. My idea was to create the debug information for each of these logical variables by using DIBuilder::createGlobalVariableExpression called GVE and provide a DIExpression called DIE that should basically take the value of the global variable GVE is added to, i.e. the value of BaseAddress, and add a constant offset corresponding to the logical variable. This should be the address of the logical variable. So, the DIExpression DI...

...the memory block are known constants. > > - I'd like to make it possible to access these logical variables > inside the debugger as if they are normal global variables. > > My idea was to create the debug information for each of these logical > variables by using DIBuilder::createGlobalVariableExpression called > GVE and provide a DIExpression called DIE that should basically take > the value of the global variable GVE is added to, i.e. the value of > BaseAddress, and add a constant offset corresponding to the logical > variable. This should be the address of the logical variable. >...

...known constants. >> >> - I'd like to make it possible to access these logical variables >> inside the debugger as if they are normal global variables. >> >> My idea was to create the debug information for each of these logical >> variables by using DIBuilder::createGlobalVariableExpression called >> GVE and provide a DIExpression called DIE that should basically take >> the value of the global variable GVE is added to, i.e. the value of >> BaseAddress, and add a constant offset corresponding to the logical >> variable. This should be the address of the logical...

...gt; >>> - I'd like to make it possible to access these logical variables >>> inside the debugger as if they are normal global variables. >>> >>> My idea was to create the debug information for each of these logical >>> variables by using DIBuilder::createGlobalVariableExpression called >>> GVE and provide a DIExpression called DIE that should basically take >>> the value of the global variable GVE is added to, i.e. the value of >>> BaseAddress, and add a constant offset corresponding to the logical >>> variable. This should be the addres...

...t; - I'd like to make it possible to access these logical variables >>>> inside the debugger as if they are normal global variables. >>>> >>>> My idea was to create the debug information for each of these logical >>>> variables by using DIBuilder::createGlobalVariableExpression called >>>> GVE and provide a DIExpression called DIE that should basically take >>>> the value of the global variable GVE is added to, i.e. the value of >>>> BaseAddress, and add a constant offset corresponding to the logical >>>> variable. This shou...

...e to make it possible to access these logical variables >>>>> inside the debugger as if they are normal global variables. >>>>> >>>>> My idea was to create the debug information for each of these logical >>>>> variables by using DIBuilder::createGlobalVariableExpression called >>>>> GVE and provide a DIExpression called DIE that should basically take >>>>> the value of the global variable GVE is added to, i.e. the value of >>>>> BaseAddress, and add a constant offset corresponding to the logical >>>>> var...

Hi there, At the end of last week we saw a number of commits go in that were camelCasing batches of MCStreamer::Emit* and AsmPrinter::Emit* functions. For example: - https://reviews.llvm.org/rG549b436beb4129854e729a3e1398f03429149691 - https://reviews.llvm.org/rGa55daa146166353236aa528546397226bee9363b - https://reviews.llvm.org/rG0bc77a0f0d1606520c7ad0ea72c434661786a956 Unfortunately all these