search for: hasoptions

...**argv) { ... } ...to... extern "C" int llcmain(int argc, char **argv) { ... } Now I am calling this function directly from my server code. This works fine for the first build, however any other builds fail in CommandLine.cpp:1101 CommandLineParser::ParseCommandLineOptions assert(hasOptions() && "No options specified!"); <--fails here I'm trying to work out why this is breaking, I am assuming there is some global state left after processing that llc.cpp doesn't normally need to worry about? Is there a way to reset this global state cleanly? I'm assu...

Hi, I have downloaded files and also local versions of pwlib oh323 (both Janus patched). Both libraries compile fine, but I get following errors on asterisk-oh323-0.6.5. Readme is a bit confusing since it doesn't mention which local libraries should be downloaded from inaccess to get everything working OK. I've also tried with/without patching oh323 with supplied patch. Any hint, advice

...cmain(int argc, char **argv) { > ... > } > > > Now I am calling this function directly from my server code. This works fine for the first build, however any other builds fail in > > CommandLine.cpp:1101 > > CommandLineParser::ParseCommandLineOptions > > assert(hasOptions() && "No options specified!"); <--fails here > > > I'm trying to work out why this is breaking, I am assuming there is some global state left after processing that llc.cpp doesn't normally need to worry about? > > Is there a way to reset this global st...

I'm trying to make the chan_h323 in /usr/src/asterisk/channels/h323 But I'm getting all kinds of errors about PWLIB... I built using the newest PWLIB and OpenH323 from CVS Error log from make below make g++ -g -c -fno-rtti -o ast_h323.o -march=i686 -DPBYTE_ORDER=PLITTLE_ENDIAN -DNDEBUG -DDO_CRASH -DDEBUG_THREADS -pipe -Wall -fPIC -DP_LINUX -D_REENTRANT -D_GNU_SOURCE -DP_HAS_SEMAPHORES

I'm trying to make the chan_h323 in /usr/src/asterisk/channels/h323 But I'm getting all kinds of errors about PWLIB... I built using the newest PWLIB and OpenH323 from CVS Error log from make below make g++ -g -c -fno-rtti -o ast_h323.o -march=i686 -DPBYTE_ORDER=PLITTLE_ENDIAN -DNDEBUG -DDO_CRASH -DDEBUG_THREADS -pipe -Wall -fPIC -DP_LINUX -D_REENTRANT -D_GNU_SOURCE -DP_HAS_SEMAPHORES

Hi Daniel, I'm not sure I agree with the basic idea of using the target triple as a way of encoding all of the pieces of target data as a string. I think in a number of cases what we need to do is either open up API to the back end to specify things, or encode the information into the IR when it's different from the generic triple. Ideally the triple will have enough information to do

Hi, In http://reviews.llvm.org/D10969, Eric asked me to explain the wider context of the TargetTuple object that was replacing Triple on llvmdev so here it is. Before I start, I'm sure I don't know the full extent of GNU triple ambiguity and lack of canonicity. Additional examples are welcome. The Problem As you know, LLVM uses a GNU Triple is as a target description that can be relied

Hi Eric, Thanks for getting back to me on this. > I'm not sure I agree with the basic idea of using the target triple as a way of > encoding all of the pieces of target data as a string. I think in a number of > cases what we need to do is either open up API to the back end to specify things, > or encode the information into the IR when it's different from the generic triple.

Hi Daniel, > (from the context, you might have meant 'tuple' where you've written > 'triple'. I'm answering based on the assumption you meant 'triple') > > I did mean what I wrote. > The GNU triple is already used as a way of encoding a large amount of the > target data in a string but unfortunately, while this data is passed > throughout

> > (from the context, you might have meant 'tuple' where you've written 'triple'. I'm answering based on the assumption you meant 'triple') > I did mean what I wrote. I thought I ought to check since it's very easy to mix up triples and tuples and the context sounded off. I'm glad I picked the right assumption. > > The proposed TargetTuple

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!-- #msg dl { border: 1px #006 solid; background: #369; padding: