similar to: [LLVMdev] Weird behavior of llvm-ld

Hi Bram, Comments inline .. On Wed, 2006-08-16 at 18:01 +0200, Bram Adams wrote: > Hi, > > I'm using LLVM 1.8 with the GCC4-frontend on a Slackware 10.2 box (GCC > 3.3.6). When issuing the following command (line 14 in a script called > manual.sh): > > llvm-ld -O1 *.trans -L${SOME_LIB_DIR} -L${SOME_OTHER_LIB_DIR} -L > ${LLVM_FRONT}/lib -lSOME_LIB -lSOME_OTHER_LIB

In a previous post (included at the end of the message), Reid stated that in August 2006, llvm-ld did not support native libraries. I have a few questions about that. Is it still true that llvm does not support native libraries? Furthermore, what exactly is meant by that? In particular, I have bytecode that I want to turn into a native executable and it needs to be linked against a dynamic

Hi Ryan, On Sat, 2007-03-31 at 18:33 -0500, Ryan M. Lefever wrote: > In a previous post (included at the end of the message), Reid stated > that in August 2006, llvm-ld did not support native libraries. I have a > few questions about that. Is it still true that llvm does not support > native libraries? Furthermore, what exactly is meant by that? llvm-ld has been worked on (by

Hi, Op 16-aug-06, om 18:59 heeft Reid Spencer het volgende geschreven: >> llvm-ld: warning: Supposed library 'SOME_OTHER_LIB' isn't a library. > > The -l option is used to link libraries into the resulting executable. > I'm hoping "SOME_OTHER_LIB" is not the actual name and you're just > paraphrasing the actual command line. Note that native

Hi, Reid Spencer wrote: >> That's interesting! So, one only needs to add a 2-arg function called >> RunOptimizations to the module (can't check it right now)? >> > > That is correct. That function and only that function will be called. > What happens in that function is up to you :) > So, I tried this the last two days, but to no avail. I first

Dear all, I have a function that predicts DV based on one predictor pred: pred<-c(0,3000000,7800000,15600000,23400000,131200000) DV<-c(0,500,1000,1400,1700,1900) ## I define Function 1 that computes the predicted value based on pred values and parameters a and b: calc_DV_pred <- function(a,b) { DV_pred <- rep(0,(length(pred))) for(i in 1:length(DV_pred)){ DV_pred[i] <- a *

Hi Bram, On Wed, 2006-08-16 at 22:41 +0200, Bram Adams wrote: > Op 16-aug-06, om 18:59 heeft Reid Spencer het volgende geschreven: > Are there any workarounds (using other LLVM-tools) to link a native > library with LLVM-bytecode? Yes. The general approach is to use llvm-as, llvm-dis, opt and llvm-link to work with the bytecode. You can also use gccld and gccas to run some canned

Hi Sanjiv, Sanjiv Gupta <sanjiv.gupta <at> microchip.com> writes: > > PIC16 now has clang and llc based system to generate native assembly. We > then use our native assembler (gpasm) and the native linker (mplink) to > generate the final executable. How can I integrate these things with > the driver llvmc to have gcc like user experience? Note that we also >

PIC16 now has clang and llc based system to generate native assembly. We then use our native assembler (gpasm) and the native linker (mplink) to generate the final executable. How can I integrate these things with the driver llvmc to have gcc like user experience? Note that we also want to run llvm-ld in order to perform the LTOs in case of multiple files. - Sanjiv

Hi Zide, I think I found the right way to reach my goal. I used the following command: clang -O3 -Xclang -disable-llvm-optzns main.c -S -emit-llvm -o main.ll to generate an IR file enriched by all the metadata that otherwise wouldn't be generated with -O0. Moreover, -disable-llvm-optzns flag ensures that none of the optimization passes has been applied yet to the IR. In this way, I can

Dear all, I am doing few experiments to do understand optimization phase interactions. Here is a brief description of my experiements. 1. I picked the list of machine independent optimizations acting on llvm IR (those that are enabled at O3). 2. for each optimzation in the optimization-list a) Compiled the program using 'clang -c O0 -flto program.c' b) opt

Hello, At the boot prompt ALLOWOPTIONS 0 is only applied to implicit kernels and not to labels. For configuration which want to allow selection, but prevent customization of the kernel command line, this behaviour is bad. Also the IMPLICIT 0 is applied to both the boot prompt and configuration setting (like DEFAULT); but one could argue that only the command supplied at the prompt make sense to

> I'll be happy to answer any further questions you may have, feel free to e-mail > me directly (though right now our mail server is down) > The salient features that we want to have in the driver are: 1. llvm-ld will be used as "The Optimizer". 2. If the user has specified to generate the final executable, then llvm-ld should run on all the .bc files generated by clang

Full_Name: Karsten Krug Version: 2.4.0 OS: Open Suse 10.0, Windows XP Submission from: (NULL) (88.134.13.50) I found a problem in the 'optimise' function for one dimensional optimisation. Example 1: Try to find a maximum of the function below with the use of 'optimise' in the interval [0,0.5]. The function follows a parabola and has two local maxima located at the margins of

Hi, trying to install a package containing C code and requiring non-default configure argument settings the incantation (this has worked for R <= 2.8.1 on the same architectures) R CMD INSTALL --configure-args="--with-opt1 --with-opt2" packname does always result in a warning Warning: unknown option '--with-opt2' and consequently the option is ignored. Reverting the order

Mikhail Glushenkov wrote: > > Hi Sanjiv, > > Sanjiv Gupta <sanjiv.gupta <at> microchip.com> writes: > > > The salient features that we want to have in the driver are: > > [...] > > As promised, I've implemented a basic compiler driver for the > PIC16 toolchain. It's under tools/llvmc/examples/mcc16. > Hi Mikhail, How do you build mcc16

Hi Sanjiv, Sanjiv Gupta <sanjiv.gupta <at> microchip.com> writes: > The salient features that we want to have in the driver are: > [...] As promised, I've implemented a basic compiler driver for the PIC16 toolchain. It's under tools/llvmc/examples/mcc16. Some examples illustrating the features you requested: > 2. If the user has specified to generate the final

On 19 June 2011 14:44, Suresh Purini <suresh.purini at gmail.com> wrote: >  I am doing few experiments to do understand optimization phase > interactions. Here is a brief description of my experiements. > > 1. I picked the list of machine independent optimizations acting on > llvm IR (those that are enabled at O3). > 2.  for each optimzation in the optimization-list >  

Hi, Thanks a lot for your exceptional work.... I guess many people dealing with bootable CD's just could'nt do anything without isolinux... However I've got a small problem. In fact the problem is maybe due to my BIOS (Phoenix on an HP Vectra VL800), and maybe due to isolinux / memdisk, I don't know. Generally speaking, take any floppy, format it under Win2K, copy from your hard

Bram, I looked over your patch and it looks good. I applied a patch based on yours. The llvm-ld tool now uses the PluginLoader just like the opt tool. It will also run some cleanup passes after the loaded plugins run to ensure cruft is removed. See this patch for details: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060814/036882.html Thanks for the patch! And, yes, you are on