similar to: [Bug 1559] New: Autoconf overrides AR environment variable

Hi, Since I want to write tests with llvm-lit, I pulled the latest revision of LLVM from SVN HEAD and tried to run the following command (copied from http://llvm.org/docs/TestingGuide.html): $ ~/llvm/Debug+Asserts/bin/llvm-lit ~/llvm/test/Integer/BitCast.ll llvm-lit: lit.cfg:103: fatal: No site specific configuration available! Any ideas on why this happens? Thanks, Brice

I just read the LLVM Programmer's Manual, which mentions (but specifically does not include any details of) the InstVisitor template. Could someone please provide an example of how to use this template to find (as an example) all CallSites for the function strcpy? Thanks, Brice Lin

Sorry, I should have been clearer. My question deals with -emit-llvm and -c, not -g and debug information. If you remove the -g flag from the command I posted previously, the problem remains. Either way, I updated my tree recently. Oddly enough, -emit-llvm affects the compile for me without -c or -S. When I run the aforementioned command, llvm-gcc outputs the following: ld warning: in

On Apr 14, 2009, at 1:49 PM, Luke Dalessandro wrote: > > On Apr 14, 2009, at 12:48 PM, Brice Lin wrote: > >> I just read the LLVM Programmer's Manual, which mentions (but >> specifically does not include any details of) the InstVisitor >> template. Could someone please provide an example of how to use this >> template to find (as an example) all CallSites for

Hi, there can be an issue with recent gcc where the system-installed "ar" and "ranlib" commands cannot handle LTO binaries. On compilation, this manifests itself with error messages claiming that they need extra plugins. This can be fixed by using the command line $ AR=gcc-ar RANLIB=gcc-ranlib ./configure --enable-lto so it is not a big issue, but it would still be nicer

2010/11/8 Brice Lin <brice.lin at gmail.com>: > $ ~/llvm/Debug+Asserts/bin/llvm-lit ~/llvm/test/Integer/BitCast.ll > llvm-lit: lit.cfg:103: fatal: No site specific configuration available! Have you ever run "make check" and passed? ...Takumi

Hi Tomas, > On 4/23/19 2:59 PM, Thomas K?nig wrote: >> Hi, >> >> there can be an issue with recent gcc where the system-installed "ar" >> and "ranlib" commands cannot handle LTO binaries.? On compilation, this >> manifests itself with error messages claiming that they need extra >> plugins. > Thanks for the report. What was the

On Apr 14, 2009, at 12:48 PM, Brice Lin wrote: > I just read the LLVM Programmer's Manual, which mentions (but > specifically does not include any details of) the InstVisitor > template. Could someone please provide an example of how to use this > template to find (as an example) all CallSites for the function > strcpy? If this is really what you want to do, then the easiest

Ignore this at your own peril. I have committed changes to CVS that introduce a fully functional llvm-ar tool, and a new lib/Linker library that uses the archive's symbol table to hasten linking. However, this implies that archives read by the LLVM tools *must* have an LLVM symbol table in them. This happens automatically for the crtend.a library, but not for the runtime libraries produced by

On Feb 26, 2009, at 12:40 PM, Brice Lin wrote: > Sorry, I should have been clearer. My question deals with -emit-llvm > and -c, not -g and debug information. If you remove the -g flag from > the command I posted previously, the problem remains. Either way, I > updated my tree recently. > > Oddly enough, -emit-llvm affects the compile for me without -c or -S. > When I run the

I forgot to mention .. This is a temporary requirement. I am working on changes so that an archive file that doesn't have a symbol table can be linked successfully, albeit a LOT slower. Reid. On Sun, 2004-11-14 at 15:41, Reid Spencer wrote: > Ignore this at your own peril. > > I have committed changes to CVS that introduce a fully functional > llvm-ar tool, and a new

For systems that don't have perl at /usr/bin/perl, fixpaths doesn't run. I've added a check in configure.in to find where perl is and use it to run fixpaths. Here's the patch: --- configure.in.orig Mon Dec 27 23:09:36 1999 +++ configure.in Tue Dec 28 10:16:05 1999 @@ -9,6 +9,7 @@ AC_PROG_RANLIB AC_PROG_INSTALL AC_CHECK_PROG(AR, ar, ar) +AC_CHECK_PROG(PERL, perl, perl)

Is it possible to add any flags to this command so that the resulting compile runs perfectly fine (-c builds, but does not work)? llvm-gcc -o conftest -g -O2 -Wall -Wpointer-arith -Wuninitialized -Wsign-compare -Wno-pointer-sign -Wformat-security -fno-builtin-memset -emit-llvm <filename.c> where <filename.c> contains #include <stdio.h> int main() { exit(0); } Thanks

On Thu, Aug 9, 2012 at 12:49 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: >> I think this is a leftover from the days we used to have a *byte*code >> and use bzip2 on it :-) >> >> I will try to clean it up. > > The attached patch removes all references to compression from llvm-ar, > llvm-ranlib and related libraries. > > Is it OK? >

SVA/safecode looks interesting. Is it available to play with? I grepped for strings such as "sva" "secure" "safecode" in the LLVM source tree and didn't find anything, nor did I see obvious links to implementations from the project web pages. In the short term, questions I'd be interested in answering are: What happens when embedded codes that I care

> llvm-ar cannot do compression. I think this is a leftover from the days we used to have a *byte*code and use bzip2 on it :-) I will try to clean it up. > - Michael Spencer > Cheers, Rafael

I need to generate a minimal Samba working in a SH4 cpu in a STLinux 2.3 environment. The goal is to have very very simple Samba server running in a STLinux environment. STLinux Kernel has included the CIFS support. Really I'm a newbie in Samba cross-compilation. And obviously I've problems :-( Any help will be appreciated. Thanks :-) 1) First of all I've set some env vars: export

Hi, I have a question about compiling Ogg/Vorbis. As I plan to have the code run on the LEON/SPARC CPU so I have to use sparc-rtems-gcc, sparc-rtems-ld, sparc-rtems-ranlib. Now, in order to compile the libs, e.g., libogg, I have to create my own Makefile like this: PROG=bitwise framing CC=sparc-rtems-gcc AR=sparc-rtems-ar RANLIB=sparc-rtems-ranlib CFLAGS=-rtems -msoft-float -Wall -W -g

On Thu, Aug 9, 2012 at 1:15 PM, Michael Spencer <bigcheesegs at gmail.com> wrote: > On Thu, Aug 9, 2012 at 12:49 PM, Rafael Espíndola > <rafael.espindola at gmail.com> wrote: >>> I think this is a leftover from the days we used to have a *byte*code >>> and use bzip2 on it :-) >>> >>> I will try to clean it up. >> >> The attached

On Feb 26, 2009, at 10:16 AMPST, Brice Lin wrote: > Is it possible to add any flags to this command so that the resulting > compile runs perfectly fine (-c builds, but does not work)? > > llvm-gcc -o conftest -g -O2 -Wall -Wpointer-arith -Wuninitialized > -Wsign-compare -Wno-pointer-sign -Wformat-security -fno-builtin-memset > -emit-llvm <filename.c> > > where