search for: localvar

...: 00760D4A sub_760D4A proc near ; CODE XREF: sub_75FCB0+159^Xp 00760D4A push ebp 00760D4B mov eax, ds:dword_75D66C 00760D50 mov ebp, esp 00760D52 sub esp, 14h 00760D55 push ebx ; ; localvar <- *(long *)75D66C = 0x56000 ; 00760D56 mov [ebp-4], eax 00760D59 push esi 00760D5A push edi 00760D5B push eax 00760D5C push 75D5F0h 00760D61 call sub_75FC7B 00760D66...

Hi all, I'm using clang + LLVM 2.9. Let's consider following code sample: extern void bar(int x) ; void foo(int y) { bar(y) ; } When compiled with clang at -O2 -g I've got following LLVM file: ; ModuleID = 'localvar.c' target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64" target triple = "x86_64-unknown-linux-gnu" define void @foo(i32 %y) nounwind { tail call void @llvm.dbg.va...

...eval NSUBSHELL [klibc] [INPUT] Use exit status 127 when the script to run does not exist Harald van Dijk (2): [klibc] [EVAL] Let funcnode refer to a function definition, not its first command [klibc] [SHELL] Improve LINENO support Herbert Xu (22): [klibc] [VAR] Add localvars nesting [klibc] [VAR] Fix poplocalvar leak [klibc] [VAR] Move unsetvar functionality into setvareq [klibc] [VAR] Replace cmdenviron with localvars [klibc] [VAR] Fix poplocalvar on abnormal exit from function [klibc] [VAR] Do not poplocalvars prematurely on regular uti...

...n = fmul %my_type %a, 5.0 ret %my_type %return }" ... doesn't work -> "use of undefined type" This used to work fine in 2.9 and is easily 'fixed' in LLParser by checking for the named type against the Module and adding it to the NamedType map when the parser hits LocalVar. But this seems like a hack. Anyway I guess I'm just checking that this is a bug and not something that I'm not understanding correctly. Cheers, Andrew.

...libc.git;a=commit;h=a4d612ae4f36810afb28b497e867714a01cbec82 Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Thu, 31 May 2018 01:15:34 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:55 +0000 [klibc] dash: eval: Always set localvar_stop [ dash commit 42298df5898a62f0df893be3af029d7e981623bd ] The variable localvar_stop is set iff vlocal is true. gcc doesn't get this so we get a spurious warning. This patch fixes this by always calling pushlocalvars with vlocal and making it only actually do the push if vlocal is non-z...

...ar **nargv; + int vflags; + int vlocal; errlinno = lineno = cmd->ncmd.linno; if (funcline) @@ -745,7 +747,6 @@ evalcommand(union node *cmd, int flags) /* First expand the arguments. */ TRACE(("evalcommand(0x%lx, %d) called\n", (long)cmd, flags)); setstackmark(&smark); - localvar_stop = pushlocalvars(); file_stop = parsefile; back_exitstatus = 0; @@ -759,6 +760,8 @@ evalcommand(union node *cmd, int flags) cmd_flag = 0; execcmd = 0; spclbltin = -1; + vflags = 0; + vlocal = 0; path = NULL; argc = 0; @@ -770,6 +773,8 @@ evalcommand(union node *cmd, int flags)...

...int CurChar = getNextChar(); - - if (CurChar == EOF) { + + if (CurChar == EOF) { GenerateError("End of file in local variable name"); return YYERROR; } @@ -320,30 +321,31 @@ int LLLexer::LexPercent() { } } } - + // Handle LocalVarName: %[-a-zA-Z$._][-a-zA-Z$._0-9]* - if (isalpha(CurPtr[0]) || CurPtr[0] == '-' || CurPtr[0] == '$' || + if (isalpha(CurPtr[0]) || CurPtr[0] == '-' || CurPtr[0] == '$' || CurPtr[0] == '.' || CurPtr[0] == '_') { ++CurPtr; - while (isa...

...urce code, > but rather by examining the behaviour of compiling .ll files with clang. > Surely there is somewhere in the llvm libraries where we either reject or accept (through inaction) extension/truncation to types of the same size. Maybe the verifier? > > >>> * Item 13 - LocalVar and LocalID for named types >>> >>> This is more of a question. Why are types referred to using local names >>> "%x" instead of global names "@x"? It seems inconsistent as local names >>> are >>> scoped to the function; a local variab...

Hello Sean, Thank you for your reply. I'll give your suggestion to item 6 and 7 a try tonight. I'll start a compilation and let it run throughout the night. My laptop (x61s) is 8 years old by know, so compiling LLVM takes a little time :) Regarding item 8. I don't know if anyone is using "": in the wild so fixing the implementation might make sense. If not the

On Wed, Jan 28, 2015 at 6:28 PM, Robin Eklind <carl.eklind at myport.ac.uk> wrote: > Hello Sean, > > Thank you for your reply. I'll give your suggestion to item 6 and 7 a try > tonight. I'll start a compilation and let it run throughout the night. My > laptop (x61s) is 8 years old by know, so compiling LLVM takes a little time > :) > This is why I did so much