search for: preprocssing

Hi, I am trying to make my tablegen files more flexible and for that I would like to have a name that in the end will be replaced with a type. If tablegen would support c preprocssing, I would do it like this: --- #define myBaseType i32 ... def imm32 : Operand<myBaseType>; def immZExt10 : ImmLeaf<myBaseType, [{return isUInt<10>(Imm);}]>; ... --- Is there a way to achieve something like this with tablegen ? Greetings, Jeroen Dobbelaere

...07, 2013 1:33 AM > To: llvmdev at cs.uiuc.edu > Subject: [LLVMdev] tablegen question > > Hi, > > I am trying to make my tablegen files more flexible and for that I would like > to have a name that in the end will be replaced with a type. > > If tablegen would support c preprocssing, I would do it like this: > > --- > #define myBaseType i32 > ... > def imm32 : Operand<myBaseType>; > def immZExt10 : ImmLeaf<myBaseType, [{return isUInt<10>(Imm);}]>; ... > --- > > Is there a way to achieve something like this with tablegen ? > &...

...y. Here is the code that I ran, if it helps to diagnose the problems. library(simpleaffy); library(affy); ampli.data <- ReadAffy() # normalize the data using call.exprs and mas5 ampli.eset <- call.exprs(ampli.data, "mas5") # see what data is stored in ampli.eset at description@preprocssing names(ampli.eset at description@preprocessing) # acess each piece of information within ampli.eset at description@preprocessing scale factors ampli.eset at description@preprocessing$sfs # filenames so that the scale factors can be related to their chips ampli.eset at description@preprocessing$fi...

Greetings, is there a way to specify probes and other dtrace operations via command line parameters, like " BEGIN { usr_exec=$$1; usr_syscall=$$2; } syscall::usr_syscall:entry /execname == usr_exec && guard++ == 0/ { ... " [this does not work] This would make it possible to create "generic" dtrace scripts. Otherwise, some shellscript with sed-magic would