similar to: optim and optimize are not finding the right parameter

Hello! I have 2 variables - predictor "pred" and response variable "DV": pred<-c(439635.053, 222925.718, 668434.755, 194242.330, 5786.321, 115537.344, 100835.368, 7133.206, 159058.286, 4079991.629, 3380078.060, 2661279.136, 2698324.478, 1245213.965, 1901815.503, 1517019.451, 1396857.736, 1034030.988, 432249.574, 342329.325, 1831335.792, 2209578.859, 1641709.754,

> 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

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 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

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

Here is the first Perl script I've tried to write to run rsync. It seems to work, but I don't see the progress like I should. I apologize if it's sloppy, I should add that it's not only the first perl script I've written for rsync, it's the first perl script I've written at all. ___________________________ #!/usr/bin/perl -w print " This command will DELETE

On Sat, 2004-08-14 at 21:00, Chris Lattner wrote: > On Sat, 14 Aug 2004, Reid Spencer wrote: > > > I'm at the point in developing llvmc (Compiler Driver) where I need to > > get the details on the specific optimization arguments that the -O > > family of options should (by default) issue to "opt". I'm soliciting > > your feedback on this so I can

On Sat, 14 Aug 2004, Reid Spencer wrote: > I'm at the point in developing llvmc (Compiler Driver) where I need to > get the details on the specific optimization arguments that the -O > family of options should (by default) issue to "opt". I'm soliciting > your feedback on this so I can start testing optimization. Hopefully you > can provide it by early this coming

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

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

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, 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 -load=${MY_LIB_DIR}/opt1.so -load=${MY_LIB_DIR}/opt2.so -debug-pass=Details -debug -o test ... I get the following

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

Folks, I'm at the point in developing llvmc (Compiler Driver) where I need to get the details on the specific optimization arguments that the -O family of options should (by default) issue to "opt". I'm soliciting your feedback on this so I can start testing optimization. Hopefully you can provide it by early this coming week. For clarity, the -O options are currently defined

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 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