search for: dis

...ed a bivariate mixed model and use SAS proc mixed to adjust the estimates. I thinks use R to make the same and try with this code: base<-read.csv("base.csv") adj<-.5 attach(base) sens<-(VP+adj)/(VP+FN+2*adj) log.S<-log(sens/(1-sens)) var.log.S<-1/(sens*(1-sens)*(VP+FN)) dis<-rep(1,length(log.S)) non.dis<-rep(0,length(log.S)) data.S<-data.frame(id,Modality,log.S,var.log.S,dis,non.dis) names(data.S)<-c("id","Modality","logit","var.logit","dis","non.dis") esp<-(VN+adj)/(VN+FP+2*adj) log.E<-log...

Hi, I am trying to generate LLVM bytecode using CLANG and I ran into the following problem. If I run clang with the -emit-llvm option and then try to get a textual representation of the output using llvm-dis, the latter crashes because of a failed assertion in BitCodeReader.cpp, mentioning a "Type mismatch in value table" (the exact error message is appended at the end of this email). However, if I generate the bytecode from the same source using llvm-gcc instead of clang, llvm-dis works fine...

Hi, For the first problem, try clang -S -emit-llvm test.c -o test.ll you should get the llvm IR and you don't need to use llvm-dis. Although I have tried your example with the exact commands and source code you posted and it worked just fine for me. I also use clang and LLVM 2.8 compiled from sources. For the second problem, suppress -emit-llvm, since you want the executable, not an object file: clang test.c -o test. Hope th...

...able-assertions --enable-optimized --enable-shared --prefix=/usr/local/llvm --- llvm[2]: Compiling llc.cpp for Release build gmake[2]: Entering directory `/tmp/llvm-build/2.7/llvm-objects/tools/llvm-ld' llvm[2]: Compiling Optimize.cpp for Release build llvm[2]: Linking Release executable llvm-dis (without symbols) llvm[2]: Compiling GraphPrinters.cpp for Release build /tmp/llvm-build/2.7/llvm-objects/tools/llvm-dis/Release/llvm-dis.o(.text+0x42): In function `main': : undefined reference to `llvm::sys::PrintStackTraceOnErrorSignal()' /tmp/llvm-build/2.7/llvm-objects/tools/llvm-dis/...

Thanks to everyone for the quick replies! I spent some time looking into the issue. It turns out that llvm-dis crashes on CLANG-generated bytecode if LLVM is compiled for a 64-bit architecture. The problem disappears when compiling for a 32-bit architecture. Should I file a bug report? Lorenzo On Tue, Oct 26, 2010 at 3:34 AM, Xinfinity <xinfinity_a at yahoo.com> wrote: > > Hi, > > For th...

...;Zap/1-1' -- Executing RxFAX("Zap/1-1", "/var/spool/asterisk/incoming/0722123456.tif") in new stack Changed from phase 0 to 1 Start receiving document Changed from phase 1 to 4 Sending ident >>> CSI: 40 38 37 36 35 34 33 32 31 20 20 20 20 20 20 20 20 20 20 20 20 DIS: Store and forward Internet fax: no Real-time Internet fax: no Preferred octets: 256 Can receive fax Data signalling rate: V.29 R8x7.7lines/mm and/or 200x200pels/25.4mm OK 2D coding OK Scan line length: 215mm Recording length: A4 (297mm) Receiver's minimum scan line time: 0ms at 3.85 l/mm: T7.7...

If you submit these lines, you end up with variable "vare.dis". I want to export vare.dis to csv. Stuck I am. library(vegan,logical.return = TRUE) #return=true verifies package is available library(MASS,logical.return=TRUE) #return=true verifies package is available data(varespec) #varespec is an example data file in the vegan package vare.di...

...t;, "/tmp/testfax.tif") in new stack -- CAPI Answering for MSN 2258589 Changed from phase 0 to 1 > sent FACILITY_REQ (PLCI=0x101) Start receiving document Changed from phase 1 to 4 Sending ident >>> CSI: 40 38 37 36 35 34 33 32 31 20 20 20 20 20 20 20 20 20 20 20 20 DIS: Store and forward Internet fax: no Real-time Internet fax: no Preferred octets: 256 Can receive fax Data signalling rate: V.29 R8x7.7lines/mm and/or 200x200pels/25.4mm OK 2D coding OK Scan line length: 215mm Recording length: A4 (297mm) Receiver's minimum scan line time: 0ms at 3.85 l/mm: T7.7...

...-- Executing RxFAX("Modem[i4l]/ttyI0", "/tmp/minfax.tif") in new stack Changed from phase 0 to 1 Slow carrier up Slow carrier down Start receiving document Changed from phase 1 to 4 Sending ident >>> CSI: 40 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 DIS: Preferred octets: 256 Can receive fax Supported data signalling rates: V.27ter and V.29 R8x7.7lines/mm and/or 200x200pels/25.4mm OK 2D coding OK Scan line length: 215mm Recording length: A4 (297mm) Receiver's minimum scan line time: 0ms at 3.85 l/mm: T7.7 = T3.85 R8x15.4lines/mm OK Minimum sca...

...imized --enable-shared > --prefix=/usr/local/llvm --- > llvm[2]: Compiling llc.cpp for Release build > gmake[2]: Entering directory > `/tmp/llvm-build/2.7/llvm-objects/tools/llvm-ld' > llvm[2]: Compiling Optimize.cpp for Release build > llvm[2]: Linking Release executable llvm-dis (without symbols) > llvm[2]: Compiling GraphPrinters.cpp for Release build > /tmp/llvm-build/2.7/llvm-objects/tools/llvm-dis/Release/llvm-dis.o(.text+0x42): > In function `main': > : undefined reference to `llvm::sys::PrintStackTraceOnErrorSignal()' > /tmp/llvm-build/2.7/llvm...

I am trying to disassemble some bytecode using llvm-dis: llvm-dis -f -o llvmtest/sliceme2.cbc.ll llvmtest/sliceme2.cbc However, I am getting the following error. llvm-dis: Invalid bytecode signature: 464C457F (Vers=0, Pos=4) How do I go about figuring out what the problem is? llvmtest/sliceme2.cbc is newly compil...

Hi all, I have installed FAX app as described in several mails. When a fax call is received, I get the following in the * console: -- Starting simple switch on 'Zap/1-1' -- Executing Answer("Zap/1-1", "") in new stack -- Executing Ringing("Zap/1-1", "") in new stack -- Executing Wait("Zap/1-1", "2") in new stack

...39;s position is: >> >> - don't create a new format if there is already one. >> - if you really have a good reason to create a new format, it should >> replace the existing one (i.e. don't maintain two). >> - ideally we should be able to pipe the output if llvm-dis to llvm-as in >> a lossless manner (if our layering requires to use another tool than >> llvm-as, so be it). >> > > I don't disagree with these points. I was the one who suggested that > Charles implement this as a learning experience for his ThinLTO GSoC > project...

...on this is close to what I perceive Peter's position is: - don't create a new format if there is already one. - if you really have a good reason to create a new format, it should replace the existing one (i.e. don't maintain two). - ideally we should be able to pipe the output if llvm-dis to llvm-as in a lossless manner (if our layering requires to use another tool than llvm-as, so be it). -- Mehdi 2017-06-02 20:36 GMT-07:00 Mehdi AMINI <joker.eph at gmail.com>: > > > 2017-06-02 8:46 GMT-07:00 Charles Saternos via llvm-dev < > llvm-dev at lists.llvm.org&gt...

Hi, I am trying to generate all unordered combinations of a set of numbers / characters, and I can only find a (very) clumsy way of doing this using expand.grid. For example, all unordered combinations of the numbers 0, 1, 2 are: 0, 0, 0 0, 0, 1 0, 0, 2 0, 1, 1 0, 1, 2 0, 2, 2 1, 1, 1 1, 1, 2 1, 2, 2 2, 2, 2 (I have not included, for example, 1, 0, 0, since it is equivalent to 0, 0, 1). I have

Author: dmick Repository: /hg/zfs-crypto/gate Revision: 2120ccf2018170cfe16915dac09370ad30dc5285 Log message: 6251453 dis should decode rip-relative memory accesses 6279427 mdb''s x64 disassembler doesn''t decode %rip-relative addresses for data access 6427698 mdb/kmdb/dis should look up symbols for immediate operands 6428349 mdb/kmdb/dis (libdisasm) show odd offset for x86 IP-relative instructions Fi...

...vm-dev at lists.llvm.org> wrote: > Why do we need a custom dumping format for the summary? Since we already > need the YAML format anyway, wouldn't it be better to extend that to cover > the entire summary? > IMO it is useful/convenient to be able to see the summary in the llvm-dis output. Teresa > Peter > > On Fri, Jun 2, 2017 at 8:46 AM, Charles Saternos via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hey all, >> >> Below is the proposed format for the dump of the ThinLTO module summary >> in the llvm-dis utility: >...

Hey all, Below is the proposed format for the dump of the ThinLTO module summary in the llvm-dis utility: > ../build/bin/llvm-dis t.o && cat t.o.ll ; ModuleID = '2.o' source_filename = "2.ll" target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128" target triple = "x86_64-unknown-linux-gnu" @X = constant i32 42, section "foo", ali...

...tif") in new stack Changed from phase 0 to 1 Slow carrier up Slow carrier down Slow carrier up Slow carrier down Slow carrier up Slow carrier down Start receiving document Changed from phase 1 to 4 Sending ident >>> CSI: 40 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 DIS: Preferred octets: 256 Can receive fax Supported data signalling rates: V.27ter and V.29 R8x7.7lines/mm and/or 200x200pels/25.4mm OK 2D coding OK Scan line length: 215mm Recording length: A4 (297mm) Receiver's minimum scan line time: 0ms at 3.85 l/mm: T7.7 = T3.85 R8x15.4lines/mm OK Minimum sca...

On Wed, 11 Jan 2006, Reid Spencer wrote: > llvm-as file.bc | opt -mem2reg | llvm-dis > file.ll llvm-as < file.bc | opt -mem2reg | llvm-dis > file.ll Note the extra "<". -Chris > On Wed, 2006-01-04 at 09:12 +0800, lizhuo wrote: >> meone tell me how to convert LLVM bytecode into minimal SSA form ? >> or just depend on GCC frontend ? > -Chr...