search for: flag1

Dear R-help, I am trying to write a function to simulate datasets of size n which contain two time-to-event outcome variables with associated 'Event'/'Censored' indicator variables (flag1 and flag2 respectively). One of these indicator variables needs to be dependent on the other, so I am creating the first and trying to use this to create the second using an if/else statement. My data structure needs to follow this algorithm (for each row of the data): If flag1=1 then flag2 shoul...

...lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: passdb: driver: pam userdb: driver: passwd -- George Greer -------------- next part -------------- 1 LOGIN sandbox password 2 SELECT INBOX 3 UID STORE 1 +FLAGS (Flag1) 4 UID STORE 2 +FLAGS (Flag2) 5 UID STORE 3 +FLAGS (Flag3) 6 UID STORE 4 +FLAGS (Flag4) 7 UID STORE 5 +FLAGS (Flag5) 8 UID STORE 6 +FLAGS (Flag6) 9 UID STORE 7 +FLAGS (Flag7) 10 UID STORE 8 +FLAGS (Flag8) 11 UID STORE 9 +FLAGS (Flag9) 12 UID STORE 10 +FLAGS (Flag10) 13 UID STORE 11 +FLAGS (Flag11)...

...; it needs some arguments to run (ie, to choose the backend). > I have the same problem with clang-proto-fuzzer, which uses the same approach with flags as llvm-isel-fuzzer. The solution I was thinking about is (drum roll!) to encode the flags in the binary name, e.g. "./llvm-isel-fuzzer,-flag1,-flag2" and then read these flags from argv[0] in LLVMFuzzerInitialize() Then in oss-fuzz build.sh we will just do this: for flags in -flag1a,-flag1b -flag2a,-flag2b; do cp llvm-isel-fuzzer $OUT/llvm-isel-fuzzer,$flags done > > > Who else wants to be automatically CC-ed to all tr...

...3. Create a project_list.json file and write a configuration of the form: { "single-file" : { "tests" : [ { "path" : "path to single source file", "pch_input" : "PCH if there is one" "extra_flags": [ "flag1", "flag2", ... ] }, { ... } ], "pch" : [ { "path" : "PCH Header", "name" : "PCH Name", "output": "PCH Output name" } ] }, "projects" : [ { "name"...

Hi, I was looking at LNT's "compile" tests, listed here: $ lnt-sandbox/bin/lnt showtests Available tests: compile - Single file compile-time performance testing nt - LLVM test-suite compile and execution tests When trying to run it, I get Python exceptions in the code trying to parse the output of 'ifconfig' in order to infer my MAC address (this is on 64-bit

...ar = RecPack[31] + ( RecPack[32] * 100 ); */ + /* Month = RecPack[30]; */ + /* Day = RecPack[29]; */ /* UPS internal time */ - ihour = RecPack[26]; - imin = RecPack[27]; - isec = RecPack[28]; + /* ihour = RecPack[26]; */ + /* imin = RecPack[27]; */ + /* isec = RecPack[28]; */ /* Flag1 */ /* SobreTemp = ( ( 0x01 & RecPack[33]) = 0x01 ); */ @@ -546,18 +530,8 @@ static void getbaseinfo(void) unsigned char temp[256]; unsigned char Pacote[37]; int tam, i, j=0; - time_t *tmt; - struct tm *now; const char *Model; - tmt...

.... My final question at the time was (http://dovecot.org/pipermail/dovecot/2009-January/036292.html): can one delete the dovecot-keywords and rerun the script (leaving alone the dovecot-uidlist)? There is a problem if this cannot be done, as those files have the following structure: 0 flag0 1 flag1 ... m binary garbage [optionally followed by more lines like the last] and if a new keyword is added, the file ends up like (this is copy and paste example): 0 JunkRecorded 1 $NotJunk 2 $Junk 3 Redirected 4 ^A<F0># 5 <B0><96># 6 $Forwarded It does not look like a nice thing t...

On Tue, Aug 22, 2017 at 4:34 PM, Kostya Serebryany <kcc at google.com> wrote: > > > On Tue, Aug 22, 2017 at 4:21 PM, George Karpenkov <ekarpenkov at apple.com> > wrote: > >> Hi, >> >> As a part of a recent move of libFuzzer from LLVM to compiler-rt I am >> looking into updating the build code >> for the libraries which use libFuzzer.

...+ AC_CACHE_CHECK([if $CC supports $1 flag], + AS_TR_SH([cc_cv_cflags_$1]), + CC_CHECK_CFLAGS_SILENT([$1]) dnl Don't execute actions here! + ) + + AS_IF([eval test x$]AS_TR_SH([cc_cv_cflags_$1])[ = xyes], + [CFLAGS="$CFLAGS $1"; $2], [$3]) +]) + +dnl CC_CHECK_CFLAGS_APPEND([FLAG1 FLAG2], [action-if-found], [action-if-not]) +AC_DEFUN([CC_CHECK_CFLAGS_APPEND], [ + for flag in $1; do + CC_CHECK_CFLAG_APPEND($flag, [$2], [$3]) + done +]) + +dnl Check if the flag is supported by linker (cacheable) +dnl CC_CHECK_LDFLAGS([FLAG], [ACTION-IF-FOUND],[ACTION-IF-NOT-FOUND]) + +AC_...

...+ AC_CACHE_CHECK([if $CC supports $1 flag], + AS_TR_SH([cc_cv_cflags_$1]), + CC_CHECK_CFLAGS_SILENT([$1]) dnl Don't execute actions here! + ) + + AS_IF([eval test x$]AS_TR_SH([cc_cv_cflags_$1])[ = xyes], + [CFLAGS="$CFLAGS $1"; $2], [$3]) +]) + +dnl CC_CHECK_CFLAGS_APPEND([FLAG1 FLAG2], [action-if-found], [action-if-not]) +AC_DEFUN([CC_CHECK_CFLAGS_APPEND], [ + for flag in $1; do + CC_CHECK_CFLAG_APPEND($flag, [$2], [$3]) + done +]) + +dnl Check if the flag is supported by linker (cacheable) +dnl CC_CHECK_LDFLAGS([FLAG], [ACTION-IF-FOUND],[ACTION-IF-NOT-FOUND]) + +AC_...

...+ AC_CACHE_CHECK([if $CC supports $1 flag], + AS_TR_SH([cc_cv_cflags_$1]), + CC_CHECK_CFLAGS_SILENT([$1]) dnl Don't execute actions here! + ) + + AS_IF([eval test x$]AS_TR_SH([cc_cv_cflags_$1])[ = xyes], + [CFLAGS="$CFLAGS $1"; $2], [$3]) +]) + +dnl CC_CHECK_CFLAGS_APPEND([FLAG1 FLAG2], [action-if-found], [action-if-not]) +AC_DEFUN([CC_CHECK_CFLAGS_APPEND], [ + for flag in $1; do + CC_CHECK_CFLAG_APPEND($flag, [$2], [$3]) + done +]) + +dnl Check if the flag is supported by linker (cacheable) +dnl CC_CHECK_LDFLAGS([FLAG], [ACTION-IF-FOUND],[ACTION-IF-NOT-FOUND]) + +AC...

Hi, I'm having issues connecting Garmin GPS 18 to COM1 on 9.1, I get nothing but silence. Identical setup works absolutely fine with Linux. I've got PPS wire connected to DCD, but that seems to make no difference on Linux, so I presume it shouldn't affect fbsd either. On Linux, I get: $ uname -a Linux ubuntu 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 x86_64 x86_64

...s. This involves telling the replication master about the problem, so both servers can figure out together the new UIDs. I haven't thought this through yet. - Conflict resolution for message flags/keywords. The protocol would normally send flag changes incrementally, such as "add flag1, remove flag2". Besides that there could be a 8bit checksom of all the resulting flags/keywords. If the checksum doesn't match, request all the current flags. It would be of course possible to send the current flags always instead of incremental updates, but this would waste sp...