search for: optionalconfig

Currently, llvm bytecode files must begin with llvm\d where \d = {0,1,2}. Have you considered allowing a "hash bang path" to precede the llvm magic number? This would allow llvm modules to be executable on UNIX systems (and under cygwin). Would the community find this useful? I like the idea of platform-independent binaries being able to masquerade as native executibles. I'm

...ease forgive my reversing the order of your two points in my reply below: > > This would allow llvm modules to be executable on UNIX systems (and > > under cygwin). > > This is possible now, although in a more involved manner: > http://llvm.cs.uiuc.edu/docs/GettingStarted.html#optionalconfig My main impetus for this is that llvm binaries seem to me a much more elegant and promising technology than Mach-O fat binaries (so-called Apple Universal Binaries). Of course, at the moment, fat binaries are a much more proven technology. Unfortunately, associating arbitrary magic numbers wit...

Dear All, I thought I would chime in with some ideas and opinions: o Configuration Files If it isn't too much trouble, I think we should go with XML for the following reasons: 1) We wouldn't need to implement a parsing library. There are several XML parsing libraries available, and I'm guessing that they're available in several different programming languages (Reid, am I

LLVMers, Since there's been little feedback on the design document I sent out, some decisions are being made in order to progress the work. If you have strong feelings about any of these, voice them now! 1. Name = llvmcc 2. The config file format will resemble Microsoft .ini files (name=value in sections) 3. -O set of options will control what gets done and what kind of output is