similar to: [LLVMdev] [patch] website/trunk/docs/GettingStarted.html

On Nov 29, 2009, at 8:16 AM, Josef Eisl wrote: > Hello, > > seems like GettingStarted.html is outdated regarding the version numbers > of the autoconf tools. I've changed it so they meet the versions in > AutoRegen.sh. Hi Josef, llvm/docs/GettingStarted.html (in the main llvm svn repo) seems up to date. The "website" module in svn is an old broken thing that

Hey, I have written a few lines about Release and Debug Builds (SVN checkout vs. LLVM distribution). I've also added the RELEASE_25 tag to the tags list and corrected a typo. Can someone please review? As I'm not a native speaker/writer it may contain strange wording/spelling mistakes ;). Any feedback welcome. BR Josef -- zapster -------------- next part -------------- A non-text

Thanks for your response! On 30/01/2019 20:18, Rui Ueyama wrote: > Hi Josef, > > Let me clarify my understanding. Do you want to keep original bitcode > files in the output executable when doing LTO, so that the resulting > executable contains both compiled bitcode (which is in native machine > instructions) and original bitcode files? Exactly! Kind of analogous to what

On Thu, Jan 31, 2019 at 11:05 AM Rui Ueyama via llvm-dev < llvm-dev at lists.llvm.org> wrote: > That feature is probably too specific to your project. Most projects that > use LTO are using LTO just because it generates better code. Your project > is special as your program itself can also interpret LLVM bitcode, but > that's not the case for most other programs. > I

--- OK, what about this attempt? docs/GettingStarted.html | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index 2e2200d..51aba29 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -252,7 +252,8 @@ software you will need.</p> </tr> <tr> <td>Cygwin/Win32</td>

Hi everybody! I'm Josef and I'm working at Oracle Labs on Sulong [1,2], the LLVM IR execution engine in GraalVM [3]. In addition to executing bare bitcode files, Sulong also accepts ELF files with embedded bitcode sections. Therefore, it would be great if LLD in (Full)LTO mode would support embedding bitcode sections to the resulting object file. Is that something that would be

--- My bad -- the patch was against 2.6. Hope this iteration will be the last :-) docs/GettingStarted.html | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index 851bfb6..fd8f308 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -252,7 +252,8 @@ software you will need.</p> </tr>

David Greene wrote: > On Saturday 01 May 2010 08:34:50 Josef Eisl wrote: >> Hello, >> >> I want learn more about register allocation and do some analysis for a >> current research project. After reading some papers (eg. Chaitin, >> Briggs) I think its time to get my hands dirty :). > > Welcome! > >> First I plan to (re)implement some of the classic

Reid, Thank you for all your help. I think that I have AutoRegen.sh working now. (I still get the warning about GOB2_HOOK, but I'm assuming that's not a problem.) I'll explain the scenario that led to the problem. I copied the sample project to ~/work/myproject/src/sample. Then I renamed it to ~/work/myproject/src/llvm, indicating that this was the llvm part of my project.

Hi Ryan, The output from autoconf doesn't look familiar (but then, does it ever?). Note that it thinks that AC_CONFIG_MAKEFILE isn't defined which is likely if you didn't get the LLVM_SRC_ROOT correct. Here's the only things I can think of: 1. You also need to cvs update llvm/autoconf/m4 to get the new definition of LLVM_CONFIG_PROJECT. 2. You typed in the LLVM source root

Reid, Thanks for the help. I am trying out the fixes you checked into CVS. I seem to be getting some errors running AutoRegen.sh. I am a bit inexperienced with autoconf and m4. The errors I'm getting are below. Do you know what the problem is? I am using machines running FC3. The autoconf version is 2.59, the aclocal version is 1.9.2, and the m4 version is 1.4.1.

Thank you for the response. I guess the only thing that is confusing is that the LLVM documentation, at http://llvm.org/docs/Projects.html under the "Create a Project from the Sample Project" heading, indicates that (1) you can place your project *anywhere* you want, and (2) that you are supposed to use the AutoRegen.sh script as is. However, that seems not to be the case. The

Ryan, Rather than fix the documentation to match reality, I decided to fix reality to match the documentation. I have just committed (CVS head) changes to the sample project's AutoRegen.sh script that will prompt the user for the path to the LLVM source root and the LLVM object root, if it can't automatically determine the location (because your project is not located in the llvm/projects

It's complaining about the LLVM autoconf/m4 directory which contains the m4 macros that are used in your project's configure.ac. By convention, your project should be in the llvm/projects directory so that you have: 1. llvm/autoconf 2. llvm/projects/yourProj/autoconf The AutoRegen.sh in #2 is looking for #1. By convention that should be located at ../../../autoconf/m4. AC_CONFIG_AUX_DIR

Try using the --with-llvmsrc and --with-llvmobj options to explicitly set the locations of your LLVM source tree and object tree, respectively. I faintly recall seeing this error and seem to recall using these options to work around it. -- John T. ________________________________________ From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] On Behalf Of Lane Schwartz [dowobeha at

On Fri, Apr 11, 2008 at 3:24 PM, John Criswell <criswell at cs.uiuc.edu> wrote: > Lane Schwartz wrote: > > > [snip] > > > > OK then. I didn't realize that having a newer version would be a problem. > > > > I compiled and installed autoconf 2.59. I still get the same problem: > > > > $ autoconf --version > > autoconf (GNU Autoconf)

Hi, I am attempting to set up a new frontend project based on the sample project (I'm following the instructions at http://llvm.org/docs/Projects.html). In doing so, I hit a problem with AutoRegen.sh which I worked around, and hit a problem with configure that I don't know how to work around. Below is what happens when I attempt to autoconf and configure the sample project that ships

I am trying to create a project in my home directory based off the instructions in http://llvm.org/docs/Projects.html. I have completed step 4 requiring me to set the values in autoconf/configure.ac In step 5, when I run AutoRegen.sh, I get the following error: Can't find the LLVM autoconf/m4 directory. The project should be checked out to projects directory So, I assumed that I set

On Sat, Apr 12, 2008 at 1:26 PM, Lane Schwartz <dowobeha at gmail.com> wrote: > John, > > Thanks for the advice. The script you sent gives me the same problem. > I am now able to work around the issue by making the following change > to the AutoRegen.sh script that comes with the sample project: > > 16,17c16,17 > < llvm_src_root=../../.. > <

Hello, I want learn more about register allocation and do some analysis for a current research project. After reading some papers (eg. Chaitin, Briggs) I think its time to get my hands dirty :). First I plan to (re)implement some of the classic approaches to get familiar with the framework. At the beginning the following questions came up: - Is there some documentation about register allocation