search for: global_variable

Eric, think I came across an issue with the parser in unicorn, with a request (due to 2 layers of nginx proxying) coming across with both a X_FORWARDED_PROTO and a X-Forwarded-Proto header. From the socket (in HttpRequest) - we get: X_FORWARDED_PROTO: http X-Forwarded-Proto: https which is parsed to HTTP_X_FORWARDED_PROTO"=>"http,https There was a passenger ticket that

On 12/20/2017 1:37 PM, Sanjoy Das wrote:> > Fwiw, I was under the impression that regular loads could *not* be > reordered with volatile loads since we could have e.g.: > > int *normal = &global_variable; > volatile int* ptr = 0; > int k = *ptr; // segfaults, and the signal handler writes to *normal > int value = *normal; > > and that we'd have to treat volatile loads and stores essentially as > calls to unknown functions. For this to work, "normal" should...

Guys, It seems as though the llvm system doesn't deterministically iterate over Module::iterator, or global_iterator. To make myself clearer, the iterators iterate over all the global_variables but on different llvm passes (different calls to opt -load), the iterators iterate over them in different orders. I was thinking that it has something non deterministic to do with byte code reading or the llvm system initializing the variable. Thanks, Augustine Mathew -------------- next part --...

hi, According to the llvm docs, llvm will generate global variable information such as llvm.dbg.global_variable.type which contains the line number and original name of global variables. But I tried on llvm-1.8 with -g, no such debug intrinsic functions are dumped, I only see some stoppoint, func.start. Are there any secrete options I should pass to llvm-gcc? Thanks. -Jerry -------------- next par...

Got it. I had a global_variable also with the name "main". Perhaps getOrInsertFuntion needs an assert to check this (it was returning a variable I guess rather than a function, and thus static_cast was broken). On 10/04/13 20:15, edA-qa mort-ora-y wrote: > I'm getting a strange behaviour when I attempt to create...

Daniel, Thanks a lot for the pointer, that's very helpful! I'll use that as a guide to update how we handle volatile accesses. Mind if I ask for feedback when I update the patch? Krzysztof, Thanks for the answer, that was very informative! I appreciate it! Best, Alina On Wed, Dec 20, 2017 at 5:33 AM, Krzysztof Parzyszek < kparzysz at codeaurora.org> wrote: > Hi Alina, > The

I'm getting a strange behaviour when I attempt to create my main function: auto func = static_cast<llvm::Function*>(module->getOrInsertFunction( "main", types->type_void(), (llvm::Type*)0 ) ); ASSERT( func ); auto block = llvm::BasicBlock::Create( *context, "entry", func ); The "BasicBlock::Create" function is causing a segfault. This only happens

...n functions. Both have name foo . So there is no way to know which descriptor represents which function. I am trying to get this information in assembly printer. Proposed solution : llvm.dbg.subprogram.type should have a reference to function is represents. This is in the same way as llvm.dbg.global_variable.type has a reference to global variable it represents. Thanks Vasudev -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 5980 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20...

...zyszek via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On 12/20/2017 1:37 PM, Sanjoy Das wrote:> > >> Fwiw, I was under the impression that regular loads could *not* be >> reordered with volatile loads since we could have e.g.: >> >> int *normal = &global_variable; >> volatile int* ptr = 0; >> int k = *ptr; // segfaults, and the signal handler writes to *normal >> int value = *normal; >> >> and that we'd have to treat volatile loads and stores essentially as >> calls to unknown functions. >> > > Fo...

...ilto:kparzysz at codeaurora.org>> wrote: > > On 12/20/2017 1:37 PM, Sanjoy Das wrote:> > > Fwiw, I was under the impression that regular loads could *not* be > reordered with volatile loads since we could have e.g.: > > int *normal = &global_variable; > volatile int* ptr = 0; > int k = *ptr; // segfaults, and the signal handler writes > to *normal > int value = *normal; > > and that we'd have to treat volatile loads and stores > essentially as > calls t...

Hi, On 10/04/13 20:23, edA-qa mort-ora-y wrote: > Got it. I had a global_variable also with the name "main". Perhaps > getOrInsertFuntion needs an assert to check this (it was returning a > variable I guess rather than a function, and thus static_cast was broken). if you use LLVM's cast rather than static_cast then you will get an assertion failure if the ca...

...led mongrel as serverweb and as soon as i connect locally to "localhost:3000" i can see all the content properly. When i try to connect through another machine the CSS is not used at all. I''ve searched over the web and i''ve read that it''s necessary to modify the global_variables.rb file like that: SITE = RAILS_ENV == ''production'' ? ''mydomain.com'' : ''localhost:3000'' Right now i still don''t have a domain but a static ip so i modified the file with the IP address of the machine: SITE = RAILS_ENV == ''p...

...Metadata.cpp, DebugInfo.cpp) I found that I can get it from DebugInfo or Metadata. But my little research was not successful. my code excerpt: DebugInfoFinder DIFinder; DIFinder.processModule(*M); llvm::outs() << "Count of global Variables in Module : " << DIFinder.global_variable_count() << "\n"; for(DIGlobalVariableExpression *DIGVExpr : DIFinder.global_variables()) { if(DIGlobalVariable *DIGV = DIGVExpr->getVariable()) { llvm::outs() << "DIGV DisplayName : " << DIGV->getDisplayName() <&lt...