search for: deplibs

...open UNDEFS, >>> - "$nmPath -u $Directory/$lib | sed -e 's/^[ 0]* U //' | sort >>> | uniq |"; >>> + "$nmPath -u $Directory/$lib | sed -e 's/^[ 0]* U //' -e 's/^ >>> *//' | sort | uniq |"; >>> my %DepLibs; >>> while (<UNDEFS>) { >>> chomp; >>> >> >> starting at line 123 there seems to be a by-hand version of the >> sed command. I guess this needs to be adjusted too. Probably >> sed can be used nowadays. >> > I'd adjust it...

...; } >> open UNDEFS, >> - "$nmPath -u $Directory/$lib | sed -e 's/^[ 0]* U //' | sort | >> uniq |"; >> + "$nmPath -u $Directory/$lib | sed -e 's/^[ 0]* U //' -e 's/^ *//' >> | sort | uniq |"; >> my %DepLibs; >> while (<UNDEFS>) { >> chomp; >> > > starting at line 123 there seems to be a by-hand version of the > sed command. I guess this needs to be adjusted too. Probably > sed can be used nowadays. > I'd adjust it to be able to run in the...

Hi all, Did you know that there is a 'deplibs' keyword? Neither did I. It looks like it's not really used for much. We don't document it in the Language Reference. The only support I see if for reading/writing bitcode and manipulating modules. There's a bunch of code that could be removed if we could get rid of this. Does anyo...

Please nuke it. It is really old and was never used. If it comes back it should be done with module metadata. -Chris On Nov 26, 2012, at 4:35 PM, Bill Wendling <wendling at apple.com> wrote: > Hi all, > > Did you know that there is a 'deplibs' keyword? Neither did I. It looks like it's not really used for much. We don't document it in the Language Reference. The only support I see if for reading/writing bitcode and manipulating modules. There's a bunch of code that could be removed if we could get rid of this. > >...

...p our runtime upstream. Hence, we need readers recognize previous version bitcodes as well, at least in LLVM 3.x. However, the incompatibility happened once in LLVM 3.1, and we deeply hope it won't happen again in the future 3.x version. I think it is perfectly reasonable to accept and ignore deplibs in old .bc files. Bill, can you take care of that? -Chris

...derstand the Assembler/Byte code format. Starting with a C hello world program there are statements at the beginning of the disassembled bc file that I couldn't find any documentation: target endian = little target pointersize = 32 target triple = "i686-pc-linux-gnu" deplibs = [ "c", "crtend" ] implementation These are "self-explantory" but what are the possible values and what other items should I be prepared to output. Thanks, Wink Saville

...lease nuke it. It is really old and was never used. If it comes back it > should be done with module metadata. > > -Chris > > On Nov 26, 2012, at 4:35 PM, Bill Wendling <wendling at apple.com> wrote: > > > Hi all, > > > > Did you know that there is a 'deplibs' keyword? Neither did I. It looks > like it's not really used for much. We don't document it in the Language > Reference. The only support I see if for reading/writing bitcode and > manipulating modules. There's a bunch of code that could be removed if we > could get rid...

...;<ul>\n"; > } > open UNDEFS, > - "$nmPath -u $Directory/$lib | sed -e 's/^[ 0]* U //' | sort | > uniq |"; > + "$nmPath -u $Directory/$lib | sed -e 's/^[ 0]* U //' -e 's/^ *//' > | sort | uniq |"; > my %DepLibs; > while (<UNDEFS>) { > chomp; starting at line 123 there seems to be a by-hand version of the sed command. I guess this needs to be adjusted too. Probably sed can be used nowadays. Ciao, Duncan.

...ollowing code should return the value 17 (I tested with GCC, to be sure): int main() { int i; for (i=0; i<10; i++) if (i>5) i+=10; return i; } But the demo wants to return 7 instead: Output from LLVM disassembler target endian = little target pointersize = 32 deplibs = [ "c", "crtend" ] implementation ; Functions: int %main() { loopexit: call void %__main( ) ret int 7 } declare void %__main() -- Joachim.

...;exestr" comment type being deprecated. > I see that the /defaultlib flag itself to the linker is deprecated, but it isn't clear to me that that means the dependent library feature is also deprecated. To clarify, at one point LLVM IR had a way to list dependent libraries in the form of deplibs = [ "blah.lib", "foo.lib" ] This feature was later removed in llvm commit r168694, which is what I referred to as being deprecated. i.e., I was not saying that the MSVC defaultlib flag is being deprecated. - Gao.

The -c option tells llvm-gcc to build a bytecode file without linking in the LLVM runtime library. This is similar to the -c option for regular gcc, which you use to build multiple separate .o files that you're going to link into a single executable. If you want to build from a single source file, it's easiest just to compile without the -c option. If you're building from

Hello llvm\lld, The autlolink feature in swift appends a section to the obj files (.swift1_autolink_entries) that is later need to determine what t link against in the final linked binary. I am trying to get rid of these section in the final linked binary at link time. I understand this could be done with (llvm-objcopy --remove-section=.swift1_autolink_entries) but would like have the linker

...rogram --------------- #include <stdio.h> int main() { printf("hello world\n"); return 0; } ------------- end C program ------------- This is compiled using llvm online demo into the following llvm code (target removed): ----------------- LLVM code -------------- deplibs = [ "stdc++", "c", "crtend" ] %.str_1 = internal constant [13 x sbyte] c"hello world\0A\00"; <[13 x sbyte]*> [#uses=1] implementation ; Functions: declare int %printf(sbyte*, ...) int %main() { entry: call void %__main( ) %tmp.0 = call int (sbyte*,...

...> int main() { > printf("hello world\n"); > return 0; > } > ------------- end C program ------------- > > This is compiled using llvm online demo into the following llvm code > (target removed): > ----------------- LLVM code -------------- > deplibs = [ "stdc++", "c", "crtend" ] > %.str_1 = internal constant [13 x sbyte] c"hello world\0A\00"; <[13 x > sbyte]*> [#uses=1] > > implementation ; Functions: > > declare int %printf(sbyte*, ...) > > int %main() { > entry: &g...

...hat already a while ago and it solves almost all problems, as you say. But the problem is a code like: float f; float float_addition(float a, float b) { return a+b; } which is translated by LLVM into: target endian = little target pointersize = 32 target triple = "i686-pc-linux-gnu" deplibs = [ "c", "crtend" ] %f = weak global float 0.000000e+00 ; <float*> [#uses=0] implementation ; Functions: float %float_addition(float %a, float %b) { entry: %tmp.2 = add float %a, %b ; <float> [#uses=1] ret float %tmp.2 } The global variable f is still consid...

Hello, When I compile a "hello.c" program with a printf in "main" and use llvm-gcc with a "-c" option: llvm-gcc -c t1.c -o t1.bc and then try to compile t1.bc to native using llc & gcc I get a call to "__main" which is undefined. If I don't use the "-c" option: llvm-gcc t1.c -o t1 I don't get a reference to

...> int main() { > printf("hello world\n"); > return 0; > } > ------------- end C program ------------- > > This is compiled using llvm online demo into the following llvm code > (target removed): > ----------------- LLVM code -------------- > deplibs = [ "stdc++", "c", "crtend" ] > %.str_1 = internal constant [13 x sbyte] c"hello world\0A\00"; <[13 x > sbyte]*> [#uses=1] > > implementation ; Functions: > > declare int %printf(sbyte*, ...) > > int %main() { > entry: &g...

..."); return 0; } ----------------------- without "-c" (llvm-gcc t1.c -o t1) the dissassembled bytecode does not call __main: ----------------------- ; ModuleID = '<stdin>' target endian = little target pointersize = 32 target triple = "i686-pc-linux-gnu" deplibs = [ "c", "crtend" ] %struct..TorRec = type { int, void ()* } %struct.TorRec = type { int, void ()* } %.str_1 = internal constant [4 x sbyte] c"yo\0A\00" ; <[4 x sbyte]*> [#uses=1] implementation ; Functions: declare int %printf(sbyte*, ...) i...

..."hello world\n"); > > return 0; > > } > > ------------- end C program ------------- > > > > This is compiled using llvm online demo into the following llvm code > > (target removed): > > ----------------- LLVM code -------------- > > deplibs = [ "stdc++", "c", "crtend" ] > > %.str_1 = internal constant [13 x sbyte] c"hello world\0A\00"; <[13 x > > sbyte]*> [#uses=1] > > > > implementation ; Functions: > > > > declare int %printf(sbyte*, ...) > > &...

...b>$lib</b</dt><dd><ul>\n"; } open UNDEFS, - "$nmPath -u $Directory/$lib | sed -e 's/^[ 0]* U //' | sort | uniq |"; + "$nmPath -u $Directory/$lib | sed -e 's/^[ 0]* U //' -e 's/^ *//' | sort | uniq |"; my %DepLibs; while (<UNDEFS>) { chomp; Cheers, Nathan