search for: logerror

...at llvm-config --cxxflags includes the -fno-exceptions flag. Do I need to throw no exceptions whatsoever in my application to use LLVM JIT? As a minimal example, I modified the code in https://github.com/llvm-mirror/llvm/tree/master/examples/Kaleidoscope/BuildingAJIT/Chapter2. In toy.cpp, I update LogError to throw an exception: std::unique_ptr<ExprAST> LogError(const char *Str) { fprintf(stderr, "Error: %s\n", Str); throw std::runtime_error(""); } and I catch that exception in MainLoop: static void MainLoop() { while (true) { fprintf(stderr, "ready> &qu...

Hi I've got a script like this exten => s,1,SetVar(CALLFILENAME=/var/www/recordings/${TIMESTAMP:0:8:7}/${UNIQUEID}) exten => s,2,AGI(recordstart.py,${ARG1},${CALLERIDNUM},${CALLFILENAME},Ind) exten => s,3,DIAL(ZAP/g2/${ARG1},70) exten => s,4,AGI(logerror.py,${ARG1},${CALLERIDNUM},${CHANNEL},${DIALSTATUS},${DATETIME}, ${CAUSECODE}) exten => s,5,hangup exten => s,104,AGI(logerror.py,${ARG1},${CALLERIDNUM},${CHANNEL},${DIALSTATUS},${DATETIME}, ${CAUSECODE}) exten => h,1,stopmonitor exten => h,2,SetVar(CALLFILEDIR=/var/www/recordings/${T...

...itates the system administrator greatly (see also the recent bugtraq messages about this). Here is a patch to fix this: --- sysklogd-1.3/syslogd.c-o Wed Sep 3 22:19:26 1997 +++ sysklogd-1.3/syslogd.c Wed Sep 3 22:19:39 1997 @@ -791,7 +791,7 @@ (char *) &on, sizeof(on)) < 0 ) { logerror("setsockopt, suspending inet"); } - else { + else if (AcceptRemote) { if (bind(finet, (struct sockaddr *) &sin, \ sizeof(sin)) < 0) { logerror("bind, suspending inet"); @@ -1834,7 +1834,7 @@ /* Close the sockets. */ close(funix); - cl...

...data(const FLAC__SeekableStreamDecoder *decoder, const FLAC__StreamMetadata *metadata, void *client_data) { } static void flac_error(const FLAC__SeekableStreamDecoder *decoder, FLAC__StreamDecoderErrorStatus status, void *client_data) { fprintf(stderr, "flac_error %d\n", status); logerror("flac decode error %d\n", status); } static void init_flac(void) { fprintf(stderr, "init flac\n"); sprintf(flacFilename, "%s.flac", Machine->gamedrv->name); flacFile = mame_fopen(Machine->gamedrv->name, flacFilename, FILETYPE_LASERDISK_FLAC, 0); if(fla...

...e" out of INVALID macro. Great. Committed in r186805. I propose two more patches: 1) Transform the INVALID macro into function calls, that format the text and that set LastFailure. 2) Add checks at the beginning of those function calls and continue only if LogErrors is set The second one is slightly more involved as we would like to turn this option on automatically either in -debug mode or if -polly-show or -polly-show-only is set. What do you think? Does this sound right? Cheers, Tobias

...should translate INVALID macro into a serial of functions like "invalid_CFG, invalid_IndVar, invalid_IndEdge, ... ? In that case, I could provide a small patch file for this purpose -:) > 2) Add checks at the beginning of those function calls and > continue only if LogErrors is set Those invalid log strings are used for two separate cases: 1) The first case is for detailed debugging, which is controlled by the macro DEBUG(dbgs() << MESSAGE). In such a case, string operations will automatically skipped in normal execution mode with the following if-statement: if...

...LogFacPri++; break; @@ -489,6 +498,16 @@ if (fp != NULL) { fprintf(fp, "%d\n", getpid()); (void)fclose(fp); + } + + if (runAs != getuid()) { + if (setuid(runAs) == -1) { + (void)snprintf(line, sizeof(line), + "failed to change uid to %d\n", runAs); + logerror(line); + die(0); + } + dprintf("changed running uid to %d\n", runAs); } dprintf("off & running....\n"); -------------- next part -------------- Index: src/usr.sbin/syslogd/syslogd.8 =================================================================== RCS file: /expo...

...ike it. Also noticed the spew looks simular to the contents of the "initlog.conf" file, attched also. I'm guessing it's an upstream problem? I also don't this is a big concern? Any thoughts? -------------- next part -------------- A non-text attachment was scrubbed... Name: logerrors Type: application/octet-stream Size: 1641 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20051113/df26bf90/attachment.obj> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: initlog.conf URL: <http:/...

...in red is never executed since the value may never be casted to a ConstantInt. ( I saw this approach on SO - https://stackoverflow.com/questions/5315176/llvm-get-constant-integer-back-from-value ) //========= Relevant code below ========== Value* val = e->codegen() ; if(!val) { return logError("Error evaluating argument to function call"); } if(val->getType()->isIntegerTy() ) { if(val->getType()->getIntegerBitWidth() <= 64) { tempString = tempString + "%+d,"; } // Is this correct ? else { if(ConstantInt* CI = dyn_cast<Con...

...main scop detection. However, this issue is not directly related to the speedup work, so you are welcome to skip it for now. (Btw. thanks for not blindly following my suggestions!) >> 2) Add checks at the beginning of those function calls and >> continue only if LogErrors is set > Those invalid log strings are used for two separate cases: > 1) The first case is for detailed debugging, which is controlled by the macro DEBUG(dbgs() << MESSAGE). In such a case, string operations will automatically skipped in normal execution mode with the following if-stat...

...owever, this issue is not directly related to the speedup work, so >you are welcome to skip it for now. > >(Btw. thanks for not blindly following my suggestions!) > >>> 2) Add checks at the beginning of those function calls and >>> continue only if LogErrors is set >> Those invalid log strings are used for two separate cases: >> 1) The first case is for detailed debugging, which is controlled by the macro DEBUG(dbgs() << MESSAGE). In such a case, string operations will automatically skipped in normal execution mode with the following...

At 2013-07-22 01:40:31,"Tobias Grosser" <tobias at grosser.es> wrote: >On 07/21/2013 09:49 AM, Star Tan wrote: >> Hi all, >> >> >> I have attached a patch file to reduce the polly-detect overhead. > >Great. > >> My idea is to avoid calling TypeFinder in Non-DEBUG mode, so >> TypeFinder is only called in DEBUG mode with the DEBUG

On 07/21/2013 09:49 AM, Star Tan wrote: > Hi all, > > > I have attached a patch file to reduce the polly-detect overhead. Great. > My idea is to avoid calling TypeFinder in Non-DEBUG mode, so > TypeFinder is only called in DEBUG mode with the DEBUG macro. This > patch file did this work with following modifications: > > > First, it keeps most of string information