search for: builtin_plugins

...documentation doesn't talk about creating standalone drivers. Sorry for that, I was planning to update it for ages... For now, please look at examples/Skeleton, which is a standalone driver skeleton, on which the mcc16 driver is based. > I think the correct command line is > $ make LLVMC_BUILTIN_PLUGINS=MyPlugin LLVMC_BASED_DRIVER_NAME=mydriver > > rather than > $ make BUILTIN_PLUGINS=MyPlugin DRIVER_NAME=mydriver > (I found the later one in LLVMC-Reference) This section is about building the "main" llvmc driver and its plugins. Creation of standalone drivers is not describe...

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

...t;Simple" plugin to the configured directory $ cd objs/tools/llvmc/plugins $ cp -rf $LLVM_SRC/tools/llvmc/example/Simple MyPlugin Changed the plugin name in the Makefile from "Simple" to "MyPlugin", and moved "Simple.td" to "MyPlugin.td" $ make LLVMC_BUILTIN_PLUGINS=MyPlugin LLVMC_BASED_DRIVER_NAME=mydriver That created "mydriver" executable for me. - Sanjiv > 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 t...

> Would it help if it was allowed to pass arguments to hooks? So that > you could write, for example: > > (cmd_line "$CALL(MyHook, $INFILE, $OUTFILE)") Well, what I found myself wanting was a dynamic (strconcat) dag that could join together strings and (call MyHook, INFILE, OUTFILE) dags. > As Anton said, that was intentional. We wanted to minimize the number > of