similar to: [LLVMdev] llvm-ld's output file names.

Hi Sanjiv, Sanjiv Gupta <sanjiv.gupta <at> microchip.com> writes: > > Hi Mikhail, > > I have one more problem related to driver/llvm-ld at my hand for which i > could not think of any solution. May be you can help. > [...] > > Is this possible in driver? or should I hack llvm-ld? On second thought, I think I'll add a workaround for this even if

Hi, On Sat, Sep 5, 2009 at 9:12 PM, Sanjiv Gupta<sanjiv.gupta at microchip.com> wrote: > Is the patch below ok? > > Index: LLVMCConfigurationEmitter.cpp > =================================================================== > --- LLVMCConfigurationEmitter.cpp    (revision 80668) > +++ LLVMCConfigurationEmitter.cpp    (working copy) > @@ -1141,6 +1141,7 @@ >          

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

Mikhail Glushenkov wrote: > Hi Sanjiv, > > On Sun, Sep 6, 2009 at 8:13 PM, Mikhail > Glushenkov<the.dead.shall.rise at gmail.com> wrote: > >> Hi Sanjiv, >> >> On Sun, Sep 6, 2009 at 8:07 PM, Mikhail >> Glushenkov<the.dead.shall.rise at gmail.com> wrote: >> >>> [...] >>> >> [Sorry, the formatting was a

Hi Sanjiv, 2009/6/18 Sanjiv Gupta <sanjiv.gupta at microchip.com>: > 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? > Do I need to write some C++ code to customize such behaviors? Yes, this is what hooks are for.

Mikhail Glushenkov wrote: > Hi Sanjiv, > > 2009/6/18 Sanjiv Gupta <sanjiv.gupta at microchip.com>: > >> 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? >> Do I need to write some C++ code

Mikhail Glushenkov wrote: > > > 2. Is there anyway to call a C++ hook from inside actions? > > for example > > (actions (case > > (not_empty "Wl,"), (append_cmd "$CALL(Myhook)" ))) > > Not yet, this is something I'm working on right now. > Hi Mikhail, Did you get a chance to do something about this? > > > BTW, I've

Hi Mikhail, I was trying to figure out how to do the following in compiler driver. 1. mcc16 driver has a -p <device_name> option. Now from this device_name I want to be able to construct a file name like "device_name.o" and pass that to the linker. Unpack_values "p" gives me the device_name, but I do not know how to add ".o" suffix to it. something like:

Hi Sanjiv, 2009/6/29 Sanjiv Gupta <sanjiv.gupta at microchip.com>: > I want to retrieve the value of argv[0] (which was passed to main function > of the driver) in PrependCustomizedPath. I've added a way to access argv[0] in hooks: http://thread.gmane.org/gmane.comp.compilers.llvm.cvs/50789 -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against

> BTW, Chris's Makefile changes broke llvmc yesterday (r75379). I'm > working on a fix. Hi Mikhail, Did you get a chance to fix this. I still get errors while building examples. i00202 at ubuntu:~/projects/llvm/tools/llvmc/example/mcc16$ make make[1]: Entering directory `/home/i00202/projects/llvm/tools/llvmc/example/mcc16/plugins' make[2]: Entering directory

Mikhail Glushenkov wrote: > Hi Sanjiv, > > 2009/6/15 Sanjiv Gupta <sanjiv.gupta at microchip.com>: > >> Hi Mikhail, >> How do you build mcc16 executable? >> > > This should work: > > $ cd $LLVM_DIR/tools/llvmc/examples/mcc16 > $ make > > I configure llvm into a separate directory from source. When I do the steps you mentioned in

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, On Thu, Nov 19, 2009 at 5:07 AM, Sanjiv Gupta <sanjiv.gupta at microchip.com> wrote: > Hi Mikhail, > > I was trying to figure out how to do the following in compiler driver. > > 1.  mcc16 driver has a -p <device_name> option. Now from this device_name I > want to be able to construct a file name like "device_name.o" and pass that > to the

Hi Sanjiv, On Tue, Dec 8, 2009 at 4:41 AM, Sanjiv Gupta <sanjiv.gupta at microchip.com> wrote: > Mikhail Glushenkov wrote: >> >> > 2. Is there anyway to call a C++ hook from inside actions? >> > for example >> > (actions (case >> >         (not_empty "Wl,"), (append_cmd "$CALL(Myhook)" ))) >> >> Not yet, this is

Mikhail Glushenkov wrote: > Hi, > > On Thu, Sep 10, 2009 at 8:01 PM, Sanjiv Gupta > <sanjiv.gupta at microchip.com> wrote: > >> Why do we need both 'conflict' and 'warning' ? >> > > 'warning' just prints a warning, 'conflict' is a fatal error. > > A better example would be something like: > > (warning (and

Hi Mikhail, What is mentioned in the reference manual is this: // Evaluates to "cmdline1" if the option "-A" is provided on the // command line; to "cmdline2" if "-B" is provided; // otherwise to "cmdline3". (case (switch_on "A"), "cmdline1", (switch_on "B"), "cmdline2",

Hi Sanjiv, On Wed, Jul 1, 2009 at 7:02 PM, Sanjiv Gupta<sanjiv.gupta at microchip.com> wrote: > I found out the problem. Looks like I can not rely on argv[0] to contain the > full path of the executable always. Yeah, that's what I was thinking. > Can I rely on: > static Path GetMainExecutable(const char *argv0, void *MainAddr); Clang relies on it. According to

Hi Sanjiv, 2009/6/15 Sanjiv Gupta <sanjiv.gupta at microchip.com>: > I configure llvm into a separate directory from source. > When I do the steps you mentioned in the source directory, this is what I > get. In that case, copy $LLVM_DIR/tools/llvmc/example/mcc16/Makefile to $LLVM_OBJ_DIR/tools/llvmc/example/mcc16/Makefile and build from that directory.

Hi Sanjiv, 2009/6/15 Sanjiv Gupta <sanjiv.gupta at microchip.com>: > Hi Mikhail, > How do you build mcc16 executable? This should work: $ cd $LLVM_DIR/tools/llvmc/examples/mcc16 $ make If you're building from some other dir, you'll need to update mcc16/Makefile, so it knows where Makefile.common is located. > There are so many confusing things there: driver, plugins,

> 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