search for: problem2

...ow the complete list of ISD:: instruction (SelectionDAG) I have to implement (either by promoting, customizing and expanding)? A possible solution is to implement all of them, taking the list defined in the file mentioned above or taking the list from an already existing target (e.g. MSP430 Mips). Problem2: even if I implement the complete list, how can I test it? I cannot write a .ll file containing directly the ISD:: instruction, but rather IR one that causes the former to appear in the SelectionDAG. In such case, what is the relationship between IR instructions and ISD:: ones? Note to problem2: t...

Dear Tom, thank you for your reply. What you suggest is something I was considering doing, however there still no solution to my Problem2. How do I test the ISD instructions if I can only write IR instructions? -----Original Message----- From: Tom Stellard [mailto:thomas.stellard at amd.com] Sent: Wednesday, June 20, 2012 4:14 PM To: Christian Nastasi Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] Back-end: how to test all lower...

...target (e.g. MSP430 Mips). > The complete list of ISD opcodes is located in include/llvm/CodeGen/ISDOpcodes.h, as far as I know you need to handle all of them, however some of these are handled for you in the TargetLowering constructor in lib/CodeGen/SelectionDAG/TargetLowering.cpp. -Tom > Problem2: even if I implement the complete list, how can I test it? I cannot write a .ll file containing directly the ISD:: instruction, but rather IR one that causes the former to appear in the SelectionDAG. In such case, what is the relationship between IR instructions and ISD:: ones? > > Note to p...

...e how quick I'll be. (My house is full of contractors right now, so not a very nice place to work.) I don't know any workaround other than "avoid doing the buggy thing". But I can't tell you what that is.... Duncan Murdoch > Once you start the function with the "problem2()" command, the function > will print to the screen once every 400 iterations. You can monitor the > progress by clicking the scroll button. The R GUI should crash somewhere > between i=200 and i=2000. Although the problem is repeatable, the time > at which the crash occurs is...

...et of code that will cause the crash. As you will see, there are two do-loops within which is a "load" command. The crash usually occurs after 200*400 (=80,000) to 2,000*400(=800,000) iterations. Do you have any suggestions on work-arounds? Once you start the function with the "problem2()" command, the function will print to the screen once every 400 iterations. You can monitor the progress by clicking the scroll button. The R GUI should crash somewhere between i=200 and i=2000. Although the problem is repeatable, the time at which the crash occurs is random. Thanks in a...

...= 1,] subset1<-subset1[subset1$Category == 1,] Now, this works, but is UGLY! I tried using "&&" or "&" , for isntance : subset1<-subset1[ (subset1$Class == 1)&& (subset1$Category == 1),] but it returns an empty data frame. Anyway, the main problem is Problem2: I have a second data frame - a square matrix (rownames == colnames), distm: distm<-read.table(file=f_simmatrix, sep = ","); what I want is select ONLY the columns and rows entries matching the above subset1: subset2<-distm[subset1$Dataset,subset1$Dataset] returns a matrix of co...