search for: ofmt

...I've started to put together a simple driver for Elsa and LLVM that I'm calling "ellsif" (cute name, I think it works). The file being compiled is a "printf" function. Here are timing results for optimized and unoptimized runs: [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i -time-actions Adding test/ofmt.i as a preprocessed C file Phase: Preprocessing test/ofmt.i is ignored during this phase Phase: Translation compile test/ofmt.i to become an unoptimized LLVM bitcode file typechecking results: errors: 0 warnings: 0 Phase: Optimization optimize ofmt....

...that I'm calling "ellsif" (cute name, I think > it works). Er. Hm. Can you explain the name? The problem with names like "ellsif" is that it sounds like "else if". I like the fact that it reminds one of Elsa. > > [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i -time-actions -std-compile-opts Ok, this indicates that you are developing your compiler in the elsa directory. As I have said before, this is not going to work as Scott wants elsa to be "done". Oink was invented as a bucket to put elsa tools into and that is the best place for it....

>> Adding test/ofmt.i as a preprocessed C file >> Phase: Preprocessing >> test/ofmt.i is ignored during this phase >> > > What preprocessor are you using? Taras has already found one that is > working for him and that is licensed under BSD and that has some > features in it that...

I'm linking a program (my ellsif driver) that basically brings in most of the LLVM stuff: bitcode reading, optimizations, linking, and target code generation. All of a sudden, I'm getting the following when I run: [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i test/sieve.i -time-actions -O5 <premain>: CommandLine Error: Argument 'machine-licm' defined more than once! ellsif: CommandLine Error: Argument 'machine-licm' defined more than once! It seems like the constructor for this argument is being run twice. ellsif works as expe...

(Bcc''ed to networking discuss). Hi All, Have enclosed man page draft for dlstat(1M) herewith. This is part of the effort to gain better visibility into network traffic in light of crossbow features like virtual NICs, interrupt vs. polling modes etc. This in turn would greatly assist network performance analysis. It is also aimed at segregating link/flow configuration from

I would really like to avoid shipping multiple preprocessors as part of the standard elsa/oink project. On 12/21/07, Taras Glek <tglek at mozilla.com> wrote: > > >> Adding test/ofmt.i as a preprocessed C file > >> Phase: Preprocessing > >> test/ofmt.i is ignored during this phase > >> > > > > What preprocessor are you using? Taras has already found one that is > > working for him and that is licensed under BSD and that has some...

> I'm linking a program (my ellsif driver) that basically brings in most > of the LLVM stuff: bitcode reading, optimizations, linking, and target > code generation. > > All of a sudden, I'm getting the following when I run: > [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i test/sieve.i -time-actions > -O5 > <premain>: CommandLine Error: Argument 'machine-licm' defined more than once! > ellsif: CommandLine Error: Argument 'machine-licm' defined more than once! I recently had a similar problem when I wrote a new pass and built it into...

...;m linking a program (my ellsif driver) that basically brings in most >> of the LLVM stuff: bitcode reading, optimizations, linking, and target >> code generation. >> >> All of a sudden, I'm getting the following when I run: >> [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i test/sieve.i -time-actions >> -O5 >> <premain>: CommandLine Error: Argument 'machine-licm' defined more than > once! >> ellsif: CommandLine Error: Argument 'machine-licm' defined more than once! > > I recently had a similar problem when I wrote a...