Displaying 20 results from an estimated 3000 matches similar to: "Executing code changed with LLVM"
2020 Aug 23
2
MultiDatabase shard count limitations
Olly Betts <olly at survex.com> wrote:
> On Fri, Aug 21, 2020 at 09:06:59AM +0000, Eric Wong wrote:
> > Going back to the "prioritizing aggregated DBs" thread from
> > February 2020, I've got 390 Xapian shards for 130 public inboxes
> > I want to search against(*). There's more on the horizon (we're
> > expecting tens of thousands of public
2015 Sep 03
2
Fuzzing complex programs
I'm fairly sure your compiler (or rather linker) errors are coming from the
fact that you are not linking to the C++ runtime library. Use `clang++
-std=c++11 *.o`, and I'm reasonably sure it will do what you want.
--
Mats
On 3 September 2015 at 12:26, Greg Stark via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On Sun, Aug 30, 2015 at 3:30 PM, Greg Stark <stark at
2001 Sep 29
0
configure.in fixes for 2.9.9p2
configure.in patches for 2.9.9p2:
1. Allow --with-pcre to take a path specifying the root of the
PCRE install (ROOT/include, ROOT/lib)
2. Ditto for --with-zlib
3. $no_libnsl and $no_libsocket can be determined programmatically
4. Check for innetgr, getspnam, and util in the default $LIBS before
checking in -lrpc, -lgen, and -lutil, respectively
5. dirname() is in -lgen on some
2019 Jan 26
2
How to debug .ll file with segmentation fault?
Hi,
I edited a working .ll file and llvm-as it to a .bc file. But it
causes segmentation fault. I don't know how to debug such errors.
Could anybody show me the best way to debug such errors? Thanks.
$ TRACE_OUTFILE=/tmp/trace.txt lli /tmp/y/bash_trcr.bc --norc
__trace_init
LLVMSymbolizer: error reading file: No such file or directory
#0 0x00007f162b1ee0ea
2006 Apr 03
2
[LLVMdev] lli: problem finding external symbol
Hi, I have a large-ish application I'm trying to build with LLVM, so I
replaced g++ in the Makefiles with llvm-g++. This appears to work fine
when I pass -Wl,-native to generate an ELF executable, but I want to
control the inlining threshold it uses, so I am now passing
-Wl,-disable-inlining and -Wa,-disable-inlining, and having it
generate LLVM bytecode, then running opt -inlining to generate
2020 Feb 01
0
Interpreter crash due to an "Unknown constant pointer type!"
Hi Alberto,
Can you please file a bug for it, with the test case attached (if you
haven't already).
Thanks,
Ehud.
On Sat, 1 Feb 2020 at 11:32 Alberto Barbaro via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hi all,
> just a gentle reminder :) Is there any update on this please?
>
> Happy to help in any way I can
>
> Alberto
>
> Il giorno ven 3 gen 2020 alle
2019 Jan 26
3
How to debug .ll file with segmentation fault?
Could you give specific pointers to the resources that are relevant to
segmentation fault debugging? This kind of bug is the hardest to bebug
because the error message has nothing to do with the actual bug.
Generic advices without consideration of specific properties of the problem
will surely end up inefficient debugging.
What I added to the .ll file in this case are just function calls to
2001 May 21
1
2.9p1 patches
1. Add support for files >2GB via Paul Eggert's AC_SYS_LARGEFILE
macro. This macro is now part of autoconf 2.50. Because of this,
"config.h" needs to be included before system headers to get
the appropriate defines for LFS support.
openbsd-compat/sigact.c
configure.in
acinclude.m4
2. AIX defines TILDE in <sys/ioctl.h>. Rename to TILDE_CHAR. Feel
2001 Nov 22
1
[PATCH]: Fix configure.ac to allow linking against PCRE on Cygwin
Hi,
the current configure.ac file contains an unfortunately static
setting of $LIBS when the host system is Cygwin. It always
adds -lregex to $LIBS before the --with-pcre setting is evaluated.
The later adding of -lpcreposix -lpcre doesn't work correctly
since it follows later in the link order.
The following patch changes that. The static $LIBS setting in the
Cygwin case doesn't
2006 Apr 03
0
[LLVMdev] lli: problem finding external symbol
On Mon, 3 Apr 2006, Michael McCracken wrote:
> the bytecode with lli - I get the following error:
>
> $ lli -load=/home/mmccrack/linux/lib/libTau.sh leo-inline-300-tau.bc
> ERROR: Program used external function
> '__llvm_cxxeh_allocate_exception' which could not be resolved!
This is most likely because you are trying to link with llvmgcc, not with
llvm-g++. Make sure that
2015 Dec 15
2
Trouble supressing ASAN reported leaks
Hi,
I'm currently trying to find and fix memory leaks (compiling with
``-fsanitize=address``) in the KLEE tool [1] an having found some
leaks and I'm having trouble suppressing them.
I'm trying to suppress them using the
``-fsanitize-blacklist=blacklist.txt`` option as documented at
[2]. I'm using Clang 3.7 ( Arch Linux package 3.7.0-6).
The sort of reported leaks I see are
```
2011 May 11
1
[LLVMdev] compiling with libstdc++.a that "could not read symbol"
Hi there,
I have a question on my linux box where I cant link properly. I've tried
configure option --enable-shared or --disable-shared.
The following are the message I got. Is there anything I can do to fix this
linking/lib problem?
thanks in advance,
Tim
ps.
make[3]: Entering directory
`/remote/dept5428a/clientstore/timoshiu/timoshiu_esp_main_llvm/obj/lib/Transforms/Hello'
llvm[3]:
2018 Jul 12
2
custom LLVM Pass with options fails to load
Hi Philip,
thanks for the quick answer.
That makes sense, but when leaving the set LLVM_LINK_COMPONENTS out
I get an undefined symbol when loading the plugin:
_ZTVN4llvm2cl3optINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEELb0ENS0_6parserIS7_EEEE
which boils down to
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char>>,
2005 Sep 12
2
Compiling xapian-bindings-0.9.2 on OpenBSD 3.7
Hello,
Compiling xapian-core-0.9.2 worked fine, and make check reported that the tests ran without problems (although it skipped some near the end). Now I'm trying to compile xapian-bindings-0.9.2 on OpenBSD 3.7 but have run into a problem. After hours of searching the net I haven't found a solution.
For reference gcc -v gives the following output:
Configured with:
Thread model: single
2004 Sep 10
4
non-PIC code in shared libs again
On Wednesday, February 5, 2003, at 10:47 PM, Josh Coalson wrote:
> --- Matt Zimmerman <mdz@debian.org> wrote:
>
> good, very good. it may take me a little bit to get to it
> since I'm starting a new job next week.
>
> Ben, can you inspect the patch and confirm that it covers
> what you also suggested?
The patch fixed the problem with your libs. However, when
2020 Feb 10
2
Interpreter crash due to an "Unknown constant pointer type!"
>
> Hey Lang - does any of this look familiar to you?
I'm afraid not: I know nothing about the interpreter. As far as I'm aware
it's essentially abandonware.
Alberto: The usual recommendation in these circumstances is to use a JIT
class instead of the interpreter. You're using -force-interpreter though,
so I assume you really want to use the interpreter for your use case?
2004 Sep 10
2
Re: non-PIC code in shared libs again
On Tue, Feb 11, 2003 at 05:14:45PM +0000, Christian Weisgerber wrote:
> Ben Hines <bhines@alumni.ucsd.edu> wrote:
>
> > The patch fixed the problem with your libs. However, when linking the
> > xmms plugin i still get:
> >
> > *** Warning: This library needs some functionality provided by -lstdc++.
>
> This is because of id3lib, which is written in
2001 Oct 07
3
Using -lssh as shared library
Hello! This is my first post to this list... ;)
I'm not shure if someone will be interested in this topic.
For me, it has interest, as long as I maintain 100+ unix
(linux) servers with dialup access and every package update
cost some significant time to download, so package size is
somewhat important here.
I looked to openssh and realized that package consists of
several programs, all uses
2020 Jan 03
3
Interpreter crash due to an "Unknown constant pointer type!"
David,
sorry for this email but I noticed I made a mistake in the previous one. So
I managed to compile llvm Debug with asserts release. I have used the
following commands:
cmake -DLLVM_TARGETS_TO_BUILD=X86 -DLLVM_ENABLE_RTTI=ON
-DLLVM_ENABLE_FFI=ON -DCMAKE_BUILD_TYPE=Debug -DLLVM_ENABLE_ASSERTIONS=ON ..
cmake --build . -- -j8 && sudo cmake --build . --target install
Once lli was
2009 Feb 12
1
problem when using xapian's static libs in windows
I have download source ?1.10? from the internet
and build it into lib
Then I create a project as the helpdoc said
I using vc2005(vc8)
The source in my test project is as follow??copy from the helpdoc?
#include <xapian.h>
#include <iostream>
using namespace std;
int main(int argc, char **argv)
{
// Simplest possible options parsing: we just require three or more