similar to: [LLVMdev] Some Questions about LLVM

Displaying 20 results from an estimated 5000 matches similar to: "[LLVMdev] Some Questions about LLVM"

2004 Oct 27
2
[LLVMdev] Some Questions about LLVM
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=GB2312" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Yes, I checked that envvar, and it is set.<br> The error msg when compiling a .c
2004 Oct 25
0
[LLVMdev] Some Questions about LLVM
On Mon, 25 Oct 2004, zhou feng wrote: > I have some questions about LLVM > 1. I recently compiled LLVM on my X86 machine correctly. But when I use > the built LLVm compiling programs(in the getting started guide), I got > an warning saying can not find library "lc" (something like that). Yet > LLVM did yeild a execution native code and it runs correctly except with > a
2004 Dec 12
5
[LLVMdev] LLVM_LIB_SEARCH_PATH
Hello, I need to solicit your opinion about something. I'm toying with the idea of getting rid of LLVM_LIB_SEARCH_PATH. Right now the linkers will use this environment variable if it specifies a single directory. It will look in that directory to find libraries when things like -lc or -lcrtend are specified on the command line. Right now, the only known place this is useful to set to is the
2004 Dec 12
0
[LLVMdev] LLVM_LIB_SEARCH_PATH
On Sun, 12 Dec 2004, Reid Spencer wrote: > Hello, > > I need to solicit your opinion about something. > > I'm toying with the idea of getting rid of LLVM_LIB_SEARCH_PATH. Right > now the linkers will use this environment variable if it specifies a > single directory. It will look in that directory to find libraries when > things like -lc or -lcrtend are specified on
2004 Sep 05
2
[LLVMdev] POST MORTEM: llvm-test changes
That's weird. What is your default shell that Perl invokes with the "system" command. This works fine with bash-2.05b. Reid. On Sun, 2004-09-05 at 10:01, Vladimir Merzliakov wrote: > > x86 FreeBSD: > > * hasn't run with changes yet > > I manually start script. I use this options (+ -verbose now for testing) > >
2004 Sep 05
0
[LLVMdev] POST MORTEM: llvm-test changes
> That's weird. What is your default shell that Perl invokes with the > "system" command. This works fine with bash-2.05b. In reality :) i use this script in crontab (and run it manually with added verbose flag): ---8X-------------- #!/bin/sh - # if !([ -d /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD ]) then mkdir
2004 Dec 12
2
[LLVMdev] LLVM_LIB_SEARCH_PATH
Chris Lattner wrote: > On Sun, 12 Dec 2004, Reid Spencer wrote: > >> Hello, >> >> I need to solicit your opinion about something. >> >> I'm toying with the idea of getting rid of LLVM_LIB_SEARCH_PATH. Right >> now the linkers will use this environment variable if it specifies a >> single directory. It will look in that directory to find
2003 Dec 06
2
[LLVMdev] Important change to LLVM makefiles
Please read this if you're working out of LLVM CVS: I just checked in a change to the makefiles to stop using -fshort-enum when building LLVM. This flag enables a trivial optimization, but causes the code generated by the G++ compiler to not match the standard C++ ABI. Because of this, the presence of the flag makes it more difficult to link LLVM libraries to external source bases, and it
2005 Jan 13
2
[LLVMdev] the pred_begin and pred_end of BasicBlock
Sorry, still a bit confused. Say we have two basic blocks: A and B. B has a label. There is no branch/control flow instructions explicit uses B. like this: A: code sequence does not contain br/other control flow instruction B: lable_of_b: code sequence Is A still a predecessor of B? Thanks. Chris Lattner wrote: > On Thu, 13 Jan 2005, Zhou Feng wrote: > >> hi, >> I'm
2004 Dec 13
0
[LLVMdev] LLVM_LIB_SEARCH_PATH
On Sun, 12 Dec 2004, Jeff Cohen wrote: >> I definitely prefer #1. The only concern I have with it is that this makes >> it impossible to move the llvmgcc install directory once it is built (tools >> would not look in the correct directories). >> > This is a very big concern. Users of LLVM generally do not build llvmgcc -- > are actively discouraged from building
2003 Dec 07
0
[LLVMdev] Important change to LLVM makefiles
I have recently built the LLVM suite .. The problem is when I run llvmgcc( after setting alias to $LLVM ) gcc: installation problem, cannot exec `gccld': No such file or directory the LLVM_LIB_SEARCH_PATH=.. is set to LLVMGCCDIR/bytecode-libs Any idea
2005 Jan 13
2
[LLVMdev] the pred_begin and pred_end of BasicBlock
hi, I'm a bit confused by the pred_begin/end of BasicBlock in CFG.h. I cann't understand what is a **use** of a BasicBlock. Also, I have no idea of when CFG would be constructed in LLVM. Thanks. Zhou Feng
2003 Dec 07
2
[LLVMdev] Can you hint on solution to following problem
gccld: Cannot find linker input file 'crtend.o I have set the LLVM_LIB_SEARCH_PATH ls -l $LLVM_LIB_SEARCH_PATH total 104 -rw-r--r-- 1 muj20 muj20 12788 Dec 7 17:05 crtend.o -rw-r--r-- 1 muj20 muj20 1984 Dec 7 17:05 libc.bc -rw-r--r-- 1 muj20 muj20 120 Dec 7 17:05 libcurses.bc
2014 May 14
3
[CFT] ASLR, PIE, and segvguard on 11-current and 10-stable
Hey All, [NOTE: crossposting between freebsd-current@, freebsd-security@, and freebsd-stable at . Please forgive me if crossposting is frowned upon.] Address Space Layout Randomization, or ASLR for short, is an exploit mitigation technology. It helps secure applications against low-level exploits. A popular secure implementation is known as PaX ASLR, which is a third-party patch for Linux. Our
2014 May 14
3
[CFT] ASLR, PIE, and segvguard on 11-current and 10-stable
Hey All, [NOTE: crossposting between freebsd-current@, freebsd-security@, and freebsd-stable at . Please forgive me if crossposting is frowned upon.] Address Space Layout Randomization, or ASLR for short, is an exploit mitigation technology. It helps secure applications against low-level exploits. A popular secure implementation is known as PaX ASLR, which is a third-party patch for Linux. Our
2005 Feb 16
4
[LLVMdev] Install fails due to missing 'pax' tool
Hello, I've just tries make && make install on a fresh CVS tree, and get: llvm[0]: Installing include files /bin/sh: line 1: pax: command not found Two questions. 1. Why install process requires some nonstandard tool? Is it possible to get away without it. 2. autoconf/configure.ac has this: AC_PATH_PROG(PAX, [pax], [pax]) but Makefile.rules uses plain 'pax',
2008 Oct 31
14
questions on zfs backups
On Thu, Oct 30, 2008 at 11:05 PM, Richard Elling <Richard.Elling at sun.com> wrote: > Philip Brown wrote: >> I''ve recently started down the road of production use for zfs, and am hitting my head on some paradigm shifts. I''d like to clarify whether my understanding is correct, and/or whether there are better ways of doing things. >> I have one question for
2015 Aug 12
2
Re: [PATCH] dib: handle unsetting functions in environment
On Wednesday 12 August 2015 10:33:00 John Eckersberg wrote: > If a function name, with its trailing parentheses, is in the > environment , trying to unset it will error out with a message of "not > a valid identifier". In this case, try to unset it again with the -f > option which can handle the parentheses in the supplied identifier. > --- > dib/dib.ml | 2 +- > 1
2014 May 05
2
[PATCH] test-charset-fidelity: allow to skip testing specific FSes
Allow to skip testing the filesystem "foo" if the environment variable SKIP_TEST_CHARSET_FIDELITY_foo=1 is set. This way it possible to not test one or more filesystems without disabling the test altogether. --- tests/charsets/test-charset-fidelity.c | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/tests/charsets/test-charset-fidelity.c
2005 Feb 16
0
[LLVMdev] Install fails due to missing 'pax' tool
Vladimir, I believe I've corrected this situation with version 1.299 of Makefile.rules. It now only uses find and install to do the installation of the header files. pax isn't used any more. Hopefully this helps you. Reid. On Wed, 2005-02-16 at 04:18, Vladimir Prus wrote: > Hello, > I've just tries make && make install on a fresh CVS tree, and get: > >