search for: toolname

Displaying 20 results from an estimated 48 matches for "toolname".

2019 Jan 09
2
Removing LLVM_ALWAYS_INLINE from ADT classes
On Wed, Jan 9, 2019 at 9:38 AM Mehdi AMINI <joker.eph at gmail.com> wrote: > > > > On Fri, Jan 4, 2019 at 3:15 PM Davide Italiano via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Hi, >> I would like to propose, based on a previous discussion on llvm-dev, >> the following change. >> https://reviews.llvm.org/D56337 >> >> The
2019 Jan 10
2
Removing LLVM_ALWAYS_INLINE from ADT classes
...9;ll update the patch. > > * thread #1, queue = 'com.apple.main-thread', stop reason = step over > frame #0: 0x000000010000a110 lldb`main(argc=1, > argv=0x00007ffeefbff9c8) at Driver.cpp:872 > 869 > 870 // Print stack trace on crash. > 871 llvm::StringRef ToolName = llvm::sys::path::filename(argv[0]); > -> 872 llvm::sys::PrintStackTraceOnErrorSignal(ToolName); > 873 llvm::PrettyStackTraceProgram X(argc, argv); > 874 > 875 // Parse arguments. > > (lldb) p ToolName.size() > (size_t) $2 = 4 > (lldb) p ToolName.consume_fron...
2005 May 22
0
[LLVMdev] Python-LLVM bindings updated
...er. Please also make sure you read http://llvm.cs.uiuc.edu/docs/Projects.html which will help you set up a project. You might also find the Projects section of http://llvm.cs.uiuc.edu/docs/MakefileGuide.html useful. 3. Fix your Makefile to build a shared library properly. You have set TOOLNAME which is for building an executable tool not a shared library. You need to set LIBRARYNAME=..., not TOOLNAME=... 4. Fix the name of your project. It currently builds "llvm.so" which is not correct by our naming standards. It should result to something like "libLLVMpy.so&quot...
2005 May 23
1
[LLVMdev] Python-LLVM bindings updated
Hi, some discussion below. Reid wrote: > 3. Fix your Makefile to build a shared library properly. You have set > TOOLNAME which is for building an executable tool not a shared > library. You need to set LIBRARYNAME=..., not TOOLNAME=... I remember having failed to build a functioning Python extension module with LIBRARYNAME and SHARED_LIBRARY flags. Anyway, I cannot remember the details now so will try again....
2005 May 22
4
[LLVMdev] Python-LLVM bindings updated
Hi, I've updated the Python LLVM bindings for LLVM 1.5 (attached). I also thought of setting up a CVS repository for this, but before I do that I thought I'd ask if you want to take the Python bindings to the main LLVM CVS? I noticed that the C language bindings would be maintained there. Changes in Python-LLVM: - Updated to match LLVM 1.5 API - Added Windows build support (created
2005 May 19
2
[LLVMdev] [Cygwin] llvm 'make install' build errors
Actually, I just found out why. Remove the space from the end of the TOOLNAME line in llvm-ar and llvm-ranlib Makefiles. This is what's causing it, there's a space between "llvm-ar" and ".exe" I'll patch the makefiles when UIUC's CVS server isn't so sluggish. Reid On Thu, 2005-05-19 at 13:45 -0700, Reid Spencer wrote: > The rules...
2002 Sep 15
0
[LLVMdev] Simple make script
I added a simple script called "makellvm" in the base llvm directory to build a library and an executable with one command. The script runs gnumake in the current directory, and if that completes successfully, it chdir's to your llvm/tools/<toolname> and runs gnumake there. <toolname> can be specified on the command name and if not, it defaults to opt. Examples: makellvm ## run gnumake in $cwd, then in tools/opt makellvm llc ## run gnumake in $cwd, then in tools/llc makellvm -h ## print usage message --Vikram -----------...
2012 Nov 08
2
[LLVMdev] llvm-config --libs failed
...docs/tutorial/LangImpl3.html It compiles successfully with: clang++ -g -O3 toy.cpp `llvm-config --cppflags --ldflags --libs core` -o toy according to the project documentation, my Makefile inside the source of the project contains (it is in llvm/src/projects/test/tools/test/Makefile): LEVEL=../.. TOOLNAME=luna LINK_COMPONENTS = all include $(LEVEL)/Makefile.common And while executing make in build directory I get error: /home/[...]/dev/llvm/src/projects/test/build/../Makefile.llvm.rules:963: *** llvm-config --libs failed. Stop. [...] - I deleted this part What is interesting, if I run llvm-conf...
2005 May 19
0
[LLVMdev] [Cygwin] llvm 'make install' build errors
>Actually, I just found out why. Remove the space from the end of the >TOOLNAME line in llvm-ar and llvm-ranlib Makefiles. This is what's >causing it, there's a space between "llvm-ar" and ".exe" Ahh, great, thanks alot. I do not really feel upto looking into makefiles yet as I don't really know automake, configure scripts, etc, etc >I...
2009 Sep 21
3
[LLVMdev] Error when building tutorial example
...tering is that, I was trying out the first tutorial (http://llvm.org/docs/tutorial/JITTutorial1.html). I attempted to do this in another folder that was copied from llvm/projects/sample. I created a new folder called "tut1" in sample/tools/ folder, and the following Makefile. LEVEL=../.. TOOLNAME=tut1 LINK_COMPONENTS += --cxxflags LINK_COMPONENTS += --ldflags LINK_COMPONENTS += --libs LINK_COMPONENTS += core LINK_COMPONENTS += engine include $(LEVEL)/Makefile.common However, I'm getting the following error on gmake. gmake[2]: *** No rule to make target `-I/usr/src/llvm/include', ne...
2009 Jun 18
0
[LLVMdev] llvmc for PIC16
...s from where the driver itself > resides, rather than from the PATH? > Do I need to write some C++ code to customize such behaviors? Yes, this is what hooks are for. You're supposed to change the cmd_line property to something like this: (cmd_line "$CALL(PrependCustomizedPath, 'toolname') --tool --options") The PrependCustomizedPath function above is implemented in C++ (just drop a .cpp file into the plugin directory). > And how to make sure that we have same behavior on Windows as far as paths > (/ Vs \) and picking up tools from the driver directory is concerne...
2006 Mar 23
0
[LLVMdev] Virtual "components" for llvm-config
The only thing that comes to me off the top of my head is to look at the various LLVM tools and applications and see if there are common sets of libraries used by the tools. Ideally we'd want to "llvm-config --libs {toolname}" for each tool where {toolname} is replaced by the virtual component corresponding to the tool. That might be overkill, but if there are multiple tools that share the same set of libraries, it makes sense to me that those comment library sets be implemented as virtual components. In looking...
2009 Jun 18
3
[LLVMdev] llvmc for PIC16
Hi Mikhail, Thanks for your wonderful help so far. I have few more questions to ask: How do I modify the driver to pick tools from where the driver itself resides, rather than from the PATH? And how to make sure that we have same behavior on Windows as far as paths (/ Vs \) and picking up tools from the driver directory is concerned? Do I need to write some C++ code to customize such
2006 Mar 22
2
[LLVMdev] Virtual "components" for llvm-config
To ease portability headaches, I'd like to support several virtual "components" in llvm-config. Possibilities include: all: Include all LLVM libraries. backend: Include either a working native backend or cbackend. engine: Include a working subclass of ExecutionEngine, either the JIT or interpreter. You could, for example, get a typical set of JIT-related libs using:
2005 Jan 14
6
[LLVMdev] Proposed Makefile Changes
...think these should all be named BUILD_<thing_to_build> so we'd have BUILD_ARCHIVE_LIBRARY and BUILD_SHARED_LIBRARY and BUILD_RELINKD_LIBRARY and BUILD_TOOL 6. The directive names are concatenated in some cases. I'd like to see TOOL_NAME instead of TOOLNAME and LIBRARY_NAME instead of LIBRARYNAME. Its easier for *me* to read, but I'd like some feedback on this one as its as "gratuitous" change. 7. The documentation in MakefileGuide.html is lacking a tutorial on how to use the LLVM Makefile system for projects...
2011 Oct 13
0
[LLVMdev] llvm-objdump related patch
...addr + Index); - DumpBytes(StringRef(Bytes.data() + Index, Size)); + DumpBytes(StringRef(Bytes.data() + Index - SectionVMA, Size)); IP->printInst(&Inst, outs(), ""); outs() << "\n"; } else { errs() << ToolName << ": warning: invalid instruction encoding\n"; if (Size == 0) - Size = 1; // skip illegible bytes + Size = 4; // skip illegible bytes This isn't right for most instruction sets. This value needs to be computed based on the current instruction s...
2005 May 19
3
[LLVMdev] [Cygwin] llvm 'make install' build errors
Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron
2012 Nov 08
0
[LLVMdev] llvm-config --libs failed
...ompiles successfully with: clang++ -g -O3 toy.cpp `llvm-config > --cppflags --ldflags --libs core` -o toy > > according to the project documentation, my Makefile inside the source of > the project contains (it is in llvm/src/projects/test/tools/test/Makefile): > > LEVEL=../.. > TOOLNAME=luna > LINK_COMPONENTS = all > include $(LEVEL)/Makefile.common > > > And while executing make in build directory I get error: > /home/[...]/dev/llvm/src/projects/test/build/../Makefile.llvm.rules:963: > *** llvm-config --libs failed. Stop. > > [...] - I deleted this par...
2011 Oct 12
2
[LLVMdev] llvm-objdump related patch
Michael, I have rework the patch according to your suggestion. And I have read binutil/objdump source code and found that it has a logic that if there's no symtab, it will use dynsym, which is missing in llvm-objdump. Songmao -------------- next part -------------- A non-text attachment was scrubbed... Name: 0002-Fix-the-address-calculation-for-llvm-objdump.patch Type: text/x-patch
2005 May 19
4
[LLVMdev] [Cygwin] llvm 'make install' build errors
On Thu, 2005-05-19 at 22:34 +0100, Aaron Gray wrote: > I do not really feel upto looking into makefiles yet as I don't really know > automake, configure scripts, etc, etc > Aaron, its trivial. Open up tools/llvm-ar/Makefile in an editor. Go to the TOOLNAME line, delete the space at the end of the line, save the file, rebuild. > >I'll patch the makefiles when UIUC's CVS server isn't so sluggish. The patches are committing right now, albeit slowly. > > Okay, I'm working from the 1.5 release at the moment. I will move to...