similar to: [LLVMdev] Issue with GetElementPtrInst in Instruction Combining pass

Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] Issue with GetElementPtrInst in Instruction Combining pass"

2012 Apr 18
0
[LLVMdev] Issue with GetElementPtrInst in Instruction Combining pass
Hi All,   Further exploring the problem I could find that, there is a address offset calculation problem, with the GEP bitcast handling code in instruction combining. Below is table which shows address offset calculation for the struct elements (described earlier).   Type Variable Actual Size(in bytes) pass fail llvm2.9 Address(pass) Size-pass (in bytes) Address (fail) Size -fail (in bytes) with
2012 Apr 17
2
[LLVMdev] Issue with GetElementPtrInst in Instruction Combining pass
With reference to the previous query, I think, i miscalculated the offset, just recalculating. 1. without instruction combining coupling member variable, is at:   %struct._FRAME_DATA* %2, i32 0, i32 5   where "%2" is defined as:   %arrayidx3 = getelementptr inbounds i16* %Data, i32 1024, !dbg !446   %2 = bitcast i16* %arrayidx3 to %struct._FRAME_DATA*, !dbg !446 i.e. at 5 offset in
2012 Apr 17
0
[LLVMdev] Issue with GetElementPtrInst in Instruction Combining pass
Hi Pankaj, your best bet is to send the entire bitcode before and after instcombine runs. Ciao, Duncan.
2012 Apr 19
0
[LLVMdev] Issue with GetElementPtrInst in Instruction Combining pass
Hi Pankaj, are you testing this on valid bitcode? The bitcode you sent me did not pass the verifier, i.e. was not valid. Optimizers can be expected to do strange and wrong things if passed invalid bitcode. That is not a bug in LLVM: it is user error if a user doesn't use valid bitcode. Ciao, Duncan. > I think, finally, I want to conclude on this. > The problem I see is that if I
2012 Apr 19
2
[LLVMdev] Issue with GetElementPtrInst in Instruction Combining pass
I think, finally, I want to conclude on this.   The problem I see is that if I comment the case for "simplificaiton of bitcast to gep of original struct in instruction combining", wherein there is a case for if the offset by which GEP moves the pointer is non-zero.   If I disable this code, then structure elements size, I get is
2008 Nov 22
0
[patch] [vuxml] net/wireshark: fix DoS in SMTP dissector
>Submitter-Id: current-users >Originator: Eygene Ryabinkin >Organization: Code Labs >Confidential: no >Synopsis: [patch] [vuxml] net/wireshark: fix DoS in SMTP dissector >Severity: serious >Priority: high >Category: ports >Class: sw-bug >Release: FreeBSD 7.1-PRERELEASE i386 >Environment: System: FreeBSD 7.1-PRERELEASE i386 >Description: Today the DoS
2001 Feb 08
0
[CORE SDI ADVISORY] SSH1 CRC-32 compensation attack detector vulnerability
CORE SDI http://www.core-sdi.com SSH1 CRC-32 compensation attack detector vulnerability Date Published: 2001-02-08 Advisory ID: CORE-20010207 Bugtraq ID: 2347 CVE CAN: CAN-2001-0144 Title: SSH1 CRC-32 compensation attack detector vulnerability Class: Boundary Error Condition Remotely Exploitable: Yes Locally Exploitable: Yes Release Mode:
2011 Aug 31
1
formatting a 6 million row data set; creating a censoring variable
List, Consider the following data. gender mygroup id 1 F A 1 2 F B 2 3 F B 2 4 F B 2 5 F C 2 6 F C 2 7 F C 2 8 F D 2 9 F D 2 10 F D 2 11 F D 2 12 F D 2 13 F D 2 14 M A 3 15 M A 3 16 M A 3 17
2017 Apr 12
2
More issues with Siren14 datalen == 0 packets
Another crash with a packet: $10 = {frametype = AST_FRAME_VOICE, subclass = {integer = 0, format = 0x12c62170, frame_ending = 0}, datalen = 0, samples = 640, mallocd = 1, mallocd_hdr_len = 324, offset = 64, src = 0x2ad290064a08 "siren14tolin32/speex", data = {ptr = 0x80893318, uint32 = 2156475160, pad = "\030\063\211\200\000\000\000"}, delivery = { tv_sec =
2003 Jun 26
2
Plots using POSIX
Is there a reason that the bottom axis changes color when POSIX data is used in plot function? For example: > timedata <- c("2/3/2003","3/4/2003","5/4/2003") > timedata2 <- strptime(timedata,format="%m/%d/%Y") > numdata <- c(2,3,4) > plot(as.POSIXct(timedata2),numdata,col="red",type="o") As compared to: >
2019 Jul 15
0
How to enable OPUS inband FEC
Hi all, I try to enable FEC in the encoder using the macro OPUS_SET_INBAND_FEC and I set the packet loss percentage to a constant value of 30%, using the macro OPUS_SET_PACKET_LOSS_PERC. Please find my encoder settings below: opus: encoder fmtp (maxplaybackrate=8000;maxaveragebitrate=24000;sprop-stereo=1;cbr=1;useinbandfec=1;usedtx=1) opus: encode bw=narrow bitrate=24000 fch=auto vbr=0 fec=1
2015 Feb 05
2
VOIP: FEC and NARROWBAND
Hello, Is FEC supposed to work in NARROWBAND mode ?(with maxaveragebitrate=12000; maxplaybackrate=8000 ) ?I am having some confusing results, it appears that FEC is enabled in the encoder, but the decoder cannot find any packet with FEC. I am also wondering if this piece of code is correct (webrtc): /* The following is to parse the LBRR flags. */? if (opus_packet_parse(payload,
2012 Feb 14
1
[LLVMdev] How to get the array size of GetElementPtrInst->getPointerOperand() ?
If I dump the Value of GetElementPtrInst->getPointerOperand(), I got this: %a = alloca [10 x i32], align 16 Obviously, there should be a way to get the dimension and element type via the "Value" returned from GetElementPtrInst->getPointerOperand(), but how? What kind of "Value" is this? Thanks! Welson -------------- next part -------------- An HTML attachment was
2012 Dec 02
3
[LLVMdev] GetElementPtrInst question
Hi all, How can I create an llvm::GetElementPtrInst in which the pointer and the index are in registers previously loaded with llvm::LoadInst ? I mean, the generated instruction will be like this: %1 = getelementptr i8* %myreg1, i32 %myreg2 here, %myreg1 and %myreg2 are previously created by load instructions (llvm::LoadInst). Please, let me know if there is an example of something similar.
2010 Mar 24
1
isdst warning when rounding a range of time data: fix or suppress?
Hi, I'm working with timeseries data. The values are every 5 seconds and each series can last up to 4-5 days. To generate the x-axis labels, I'm doing the following: ========================= # Variable for displaying hours on the x-axis rtime <<- as.POSIXct(round(range(timedata), "hours")) # Variable for displaying days on the x-axis stime <<-
2012 Dec 02
0
[LLVMdev] GetElementPtrInst question
Hi, You'd use an IRBuilder, like you did to create your LoadInsts. IRBuilder<> IRB(BB); IRB.CreateGEP(myreg1, myreg2); I assume because you asked this question, something went wrong when using the above method. What was it? :) Cheers, James ________________________________________ From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] On Behalf Of Eduardo [erocha.ssa
2012 Dec 02
1
[LLVMdev] GetElementPtrInst question
Hi James, Thanks for your quick reply. > I assume because you asked this question, something went wrong when using the above method. What was it? :) No, I am not using this method. I was trying to create a llvm::GetElementPtrInst . I didn't create IRBuilder. I am writing a ModulePass that insert new instruction to an existing Module. Besides, how can you get a reference to myreg1 ?
2013 Aug 02
1
[LLVMdev] replacing GetElementPtrConstantExpr with GetElementPtrInst ... sometimes
Hi During a pass, the XCore target lowers thread local global variables by turning them into global variable arrays indexed by the (max 8) thread ID. (see XCoreLowerThreadLocal.cpp) This works fine for instructions e.g. GetElementPtrInst But can't be done for constants e.g. GetElementPtrConstantExpr Thus I would like to replace GetElementPtrConstantExpr with GetElementPtrInst when it is
2003 Nov 21
1
[LLVMdev] GetElementPtrInst Again!
On Fri, 2003-11-21 at 14:35, Chris Lattner wrote: > On Fri, 21 Nov 2003, Reid Spencer wrote: > > When I set up the call, I get the following from that pesky :) verifier: > > Ah, but it's so helpful! :) It is actually. It is ensuring that my compiler is correct which is one of the hardest things to do! > > So, in LLVM are arrays and pointers not equivalent as in
2003 Nov 21
0
[LLVMdev] GetElementPtrInst Again!
On Fri, 21 Nov 2003, Reid Spencer wrote: > I'm trying to set up a call to printf in stacker and have managed to > confuse myself. Perhaps you can shed some light. :) > I've declared printf as a function taking a pointer to SByteTy with var > args and returning SIntTy: Sounds good. > When I set up the call, I get the following from that pesky :) verifier: Ah, but