similar to: [LLVMdev] Linux-x86 and Solaris Makefile configuration

Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Linux-x86 and Solaris Makefile configuration"

2002 Sep 13
2
[LLVMdev] Linux-x86 Compatability
ISSUE: In Interpreter::getCurrentExecutablePath(), dladdr() is a Solarisism. Luckily, getCurrentExecutablePath isn't being currently used anywhere in lli. ACTION: Wrap the method contents with #ifdef __sun__ ... #else return ""; #endif. If this functionality is actually desired, it would be more portable to hack up main() to join getcwd() with basename(argv[0]) to find the
2002 Sep 13
2
[LLVMdev] Linux-x86 Compatability
ISSUE: INT64_MAX undefined in InstrSelectionSupport.cpp and InstructionCombining.cpp. I'm not completely sure where INT64_MAX comes from on Solaris, but C99 says that INT64_MAX is defined in stdint.h, but, for C++, only if __STDC_LIMIT_MACROS is #defined. Solaris (at least in CSIL) unfortunately does not have stdint.h, but it does have the old inttypes.h - and so does Linux. ACTION: In
2002 Oct 25
1
[LLVMdev] Makefile.common:388: Depend/xxx.d: No such file or directory
For your listening pleasure, I got tired of seeing these unnecessary warnings from make, so I changed the line from include xxx to -include xxx to make make be quiet. -- Casey Carter Casey at Carter.net ccarter at uiuc.edu AIM: cartec69 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: p URL:
2002 Oct 27
0
[LLVMdev] utils/Burg Makefile fails
The machinery around the bison call in the Makefile does not work for me. From the source file gram.yc, my bison (version 1.28) generates files gram.yc.tab.h and gram.yc.tab.c instead of gram.tab.cc and gram.tab.hc. My fix is to use the -o option to tell bison what to name the outputs. -- Casey Carter Casey at Carter.net ccarter at uiuc.edu AIM: cartec69 -------------- next part
2002 Sep 13
1
[LLVMdev] Linux-x86 Compatability
ISSUE: In CommandLine.h, gcc 2.96 thinks that the apply() template function, when called as: apply("Some text string", x) should be expanded to applicator<const char[n]>("Some text string", x) instead of applicator<char[n]>("Some text string", x). ACTION: Duplicate the template specialization for applicator<char[n]> as applicator<const
2002 Sep 13
1
[LLVMdev] Linux-x86 Compatability
ISSUE: In Interpreter::executeInstruction(), _sys_siglistp is a Solarisism. ACTION: Replace _sys_siglistp[signo] with strsignal(signo) which is more portable, maybe POSIX? PATCH: Apply from llvm top-level directory with "patch -p0." -- Casey Carter Casey at Carter.net ccarter at uiuc.edu AIM: cartec69 -------------- next part -------------- An embedded and charset-unspecified text
2002 Sep 13
0
[LLVMdev] Linux-x86 Compatibility
ISSUE: getTimeRecord in lib/VMCore/Pass.cpp uses timeval and gettimeofday() without including sys/time.h. ACTION: Include sys/time.h. PATCH: Apply from llvm top-level directory with "patch -p0." -- Casey Carter Casey at Carter.net ccarter at uiuc.edu AIM: cartec69 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: patch URL:
2002 Sep 13
1
[LLVMdev] Linux-x86 Compatability
ISSUE: ExternalFunctions.cpp::lookupFunction() calls dlsym(RTLD_DEFAULT, ...). In glibc, dlfcn.h does not make RTLD_DEFAULT visible unless _GNU_SOURCE is #defined. Unlike the evil money-grubbing non-free software pigs at sun, the FSF is trying not to pollute the C namespace. ;) ACTION: Hack the Makefile to #define _GNU_SOURCE while compiling in tools/lli. Yes, I know that this is ugly.
2002 Sep 13
1
[LLVMdev] Linux-x86 Compatability
ISSUE: Linux doesn't have any steenking SIGEMT signal, as referred to in lib/Support/Signals.cpp. ACTION: Wrap the use with a #ifdef SIGEMT / #endif. PATCH: Apply from llvm top-level directory with "patch -p0". -- Casey Carter Casey at Carter.net ccarter at uiuc.edu AIM: cartec69 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed...
2002 Sep 13
1
[LLVMdev] Linux-x86 Compatibility
ISSUE: DSOs in Linux are created by "g++ -shared" instead of "g++ -G". ACTION: Compile with "g++ -shared" instead of "g++ -G", i.e., use the alternate definition of "MakeSO" in Makefile.common. PATCH: Apply from llvm top-level directory with "patch -p0". -- Casey Carter Casey at Carter.net ccarter at uiuc.edu AIM: cartec69
2002 Sep 13
0
[LLVMdev] Dynamic loading on x86-Linux
ISSUE: By default, symbols are not exported from an executable unless they are linked against a DSO. What this means is that dlopen()ed DSOs cannot link to symbols in the main executable unless that executable was linked with --export-dynamic. ACTION: Ensure that opt is linked with "-Wl,--export-dynamic" on the G++ command line by defining "ExportSymbols" in
2002 Oct 27
2
[LLVMdev] Compile error in include/Support/GraphWriter.h
Issue: GraphWriter includes <ostream>, which my gcc2 apparently thinks is <ostream.h>. Fix: Make a new <Support/ostream> that handles this discrepancy, ala <Support/hash_set>. -- Casey Carter Casey at Carter.net ccarter at uiuc.edu AIM: cartec69 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: patch URL:
2002 Sep 17
1
[LLVMdev] Bug in InstructionCombining.cpp
ISSUE: This code: %bob = type { int } int %alias() { %pbob1 = alloca %bob %pbob2 = getelementptr %bob* %pbob1 ;pbob2 aliases pbob1 %pbobel = getelementptr %bob* %pbob2, long 0, ubyte 0 %rval = load int* %pbobel ret int %rval } Crashes when run through opt -instcombine. InstCombiner visits instructions in reverse declaration order, but
2002 Sep 11
2
[LLVMdev] Porting to x86 Linux
So, I had to make a few changes to the llvm sources to allow compilation on x86 redhat 7.3 (gcc-2.96, glibc 2.2.4). Is there any general interest in maintaining a port? I will happily submit patches. -- Casey Carter Casey at Carter.net ccarter at uiuc.edu AIM: cartec69
2002 Sep 13
2
[LLVMdev] Linux-x86 Compatability
Chris Lattner wrote: >>>Interesting. INT64_MAX is supposed to be provided by >>>include/Support/DataTypes.h. Do you know of a reliable preprocessor >>>symbol that can be used to determine whether we're on a linux box, or >>> >>> > > > >>Well, there is always __linux__, but that doesn't necessarily imply that >>we
2002 Sep 13
3
[LLVMdev] Linux-x86 Compatability
Chris Lattner wrote: >>ISSUE: INT64_MAX undefined in InstrSelectionSupport.cpp and >>InstructionCombining.cpp. I'm not completely sure where INT64_MAX comes >>from on Solaris, but C99 says that INT64_MAX is defined in stdint.h, >>but, for C++, only if __STDC_LIMIT_MACROS is #defined. Solaris (at >>least in CSIL) unfortunately does not have stdint.h, but it does
2002 Sep 17
0
[LLVMdev] Typo in Pass.h
Like the subject says. -- Casey Carter Casey at Carter.net ccarter at uiuc.edu AIM: cartec69 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: patch URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20020917/496d0a9c/attachment.ksh>
2002 Sep 17
0
[LLVMdev] Linux-x86 Dynamic loading
ISSUE: Every tool that uses dynamic module loading must be linked with $(ExportSymbols). ACTION: Alter Makefiles for analyze, llc, and opt. lli is ready. -- Casey Carter Casey at Carter.net ccarter at uiuc.edu AIM: cartec69 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: patch URL:
2002 Sep 17
0
[LLVMdev] Typo in www/docs/WritingAnLLVMPass.html
Pretty straightforward. -- Casey Carter Casey at Carter.net ccarter at uiuc.edu AIM: cartec69 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: patch URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20020917/24b4e16a/attachment.ksh>
2002 Sep 17
1
[LLVMdev] Linux-x86 compile errors
ISSUE: Some Reoptimizer header files think that int64_t is in <sys/types.h> instead of "Support/DataTypes.h". ACTION: Ensure that all users of types int64_t or uint64_t include "Support/DataTypes.h" -- Casey Carter Casey at Carter.net ccarter at uiuc.edu AIM: cartec69 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed...