search for: emiss

.... So if there are any experts in IDL-to-R porting out there, I'd appreciate your assistance. TIA, Tom Roche <Tom_Roche at pobox.com>---2 IDL routines follow to EOF--- from ftp://gfed3:dailyandhourly at zea.ess.uci.edu/GFEDv3.1/Readme.pdf ;++++++++++++++++++++ idl code to generate daily emissions +++++++++ nlon=720 ; number of grid points by longitude nlat=360 ; number of grid points by latitude gfedmly=fltarr(nlon,nlat) ; array containing monthly emissions gfeddly=fltarr(nlon,nlat) ; array containing daily emissions ; You must read monthly emissions to generate daily fluxes. ; For exa...

I have been trying to figure out how to get superscript/subscript in the main title for a plot. I have tried various approaches and suggestions but none of them work. I am trying to get the following as the main title of my plot: Emission of CO2 with time (but note that 2 is subscript.) I have tried plot(main="Emission of C"expression(O[2]) "with time") and I get error message. I have also tried plot(main="Emission of C"quote(O[2]) "with time") I have also tried plot(main""...

I've recently changed the XCore target to implement BR_JT as a jump to a series jumps. The jump table entries are expand inline in the function so there is no longer a need to emit jump tables at the end of the function. However the emission of jump tables at the end of a function is done inside the AsmPrinter base class and there seems to be no way of disabling this. This also seems to effect code produced for ARM Thumb2. Again each jump table is emitted twice - once inline in the code and once at the end of the function. The...

...s. I have the following dataframe:? A ? ? ? ? ? ? ? ?? B ? ? ? ? ? ? ? ? C ? ? ? ? ? D ? ? ? ?? E ? ? ? ? ? ? ? ? ?? F ? ? ? ? ? ? ? ? ?? G ? ? ? ? ? ? ? ?0.0.24 ? ? ? ?? 152460 ? ? ? ? 474 ? ? ? 5.5 ? ? ?? 612000 ? ? ? ? ? 59061000 ? ? ? 1540313 and here is the script: setwd("~/Desktop") emission<-read.csv("emission from land.csv") attach(emission) #define the formulas Emission_from_Land<-A*B*C*DEmission_from_Access_Road<-E*(F/1000000)*CEmissions_from_well<-(G/1000000)*E*C #combine my outputs into a new dataframe dat<-cbind(Emission_from_Land, Emission_from_Acces...

On 23/02/10 14:58, Richard Osborne wrote: > I've recently changed the XCore target to implement BR_JT as a jump to a > series jumps. The jump table entries are expand inline in the function > so there is no longer a need to emit jump tables at the end of the > function. However the emission of jump tables at the end of a function > is done inside the AsmPrinter base class and there seems to be no way of > disabling this. > > This also seems to effect code produced for ARM Thumb2. Again each jump > table is emitted twice - once inline in the code and once at the end o...

...wing dataframe: > A ? ? ? ? ? ? ? ?? B ? ? ? ? ? ? ? ? C ? ? ? ? ? D ? ? ? ?? E ? ? ? ? ? ? ? ? ?? F ? ? ? ? ? ? ? ? ?? G ? ? ? ? ? ? ? ?0.0.24 ? ? ? ?? 152460 ? ? ? ? 474 ? ? ? 5.5 ? ? ?? 612000 ? ? ? ? ? 59061000 ? ? ? 1540313 > and here is the script: > setwd("~/Desktop") > emission<-read.csv("emission from land.csv") > attach(emission) > #define the formulas > Emission_from_Land<-A*B*C*DEmission_from_Access_Road<-E*(F/1000000)*CEmissions_from_well<-(G/1000000)*E*C > #combine my outputs into a new dataframe > dat<-cbind(Emission_from_...

...58, Richard Osborne wrote: >> I've recently changed the XCore target to implement BR_JT as a jump to a >> series jumps. The jump table entries are expand inline in the function >> so there is no longer a need to emit jump tables at the end of the >> function. However the emission of jump tables at the end of a function >> is done inside the AsmPrinter base class and there seems to be no way of >> disabling this. >> >> This also seems to effect code produced for ARM Thumb2. Again each jump >> table is emitted twice - once inline in the code...

...> >>> I've recently changed the XCore target to implement BR_JT as a jump to a >>> series jumps. The jump table entries are expand inline in the function >>> so there is no longer a need to emit jump tables at the end of the >>> function. However the emission of jump tables at the end of a function >>> is done inside the AsmPrinter base class and there seems to be no way of >>> disabling this. >>> >>> This also seems to effect code produced for ARM Thumb2. Again each jump >>> table is emitted twice - once...

...ave noticed that the new NVPTX backend requires new metadata to identify the kernels in the module: define void @metadata_kernel(float* %a) { ret void } !nvvm.annotations = !{!1} !1 = metadata !{void (float*)* @metadata_kernel, metadata !"kernel", i32 1} Is clang going to support the emission of this metadata soon ? Or do I have to write it on my own ? :) Thanks, Alberto -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120507/8b7b83d2/attachment.html>

I am trying to reproduce some old SAS PROC MIXED code using R and nlme. The data consists of emission readings from vehicles and fuel properties. All variables are real numbers except "study" and "vehicle", which are character. Unfortunately, since the data are confidential, I'm unable to provide an example. The original SAS v6.12 code is provided below: ------------...

...wing dataframe: > A ? ? ? ? ? ? ? ?? B ? ? ? ? ? ? ? ? C ? ? ? ? ? D ? ? ? ?? E ? ? ? ? ? ? ? ? ?? F ? ? ? ? ? ? ? ? ?? G ? ? ? ? ? ? ? ?0.0.24 ? ? ? ?? 152460 ? ? ? ? 474 ? ? ? 5.5 ? ? ?? 612000 ? ? ? ? ? 59061000 ? ? ? 1540313 > and here is the script: > setwd("~/Desktop") > emission<-read.csv("emission from land.csv") > attach(emission) > #define the formulas > Emission_from_Land<-A*B*C*DEmission_from_Access_Road<-E*(F/1000000)*CEmissions_from_well<-(G/1000000)*E*C > #combine my outputs into a new dataframe > dat<-cbind(Emission_from_...

...gt;>> I've recently changed the XCore target to implement BR_JT as a jump to a >>>> series jumps. The jump table entries are expand inline in the function >>>> so there is no longer a need to emit jump tables at the end of the >>>> function. However the emission of jump tables at the end of a function >>>> is done inside the AsmPrinter base class and there seems to be no way of >>>> disabling this. >>>> >>>> This also seems to effect code produced for ARM Thumb2. Again each jump >>>> table is...

...h. > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Alberto Magni > Sent: Monday, May 07, 2012 6:09 AM > To: LLVM Developers Mailing List; clang-dev Developers > Subject: [LLVMdev] NVPTX annotation metadata emission > > Hi everybody, > > I have noticed that the new NVPTX backend requires new metadata to > identify the kernels in the module: > > define void @metadata_kernel(float* %a) { > ret void > } > > > !nvvm.annotations = !{!1} > !1 = metadata !{void (float*...

Hi everybody, As you know, Cuda/NVPTX target has very limited support of the debug info in Clang/LLVM. Currently, LLVM supports only emission of the line numbers debug info. This is caused by limitations of the Cuda/NVPTX codegen. Clang/LLVM translates the source code to LLVM IR, which is then lowered to PTX (parallel thread execution) intermediate file. This PTX file represents special kind of the assembler code in text format, whic...

...special case handler. At the current time, for the assembly printing, MCAsmStreamer::EmitInstruction(const MCInst &Inst) calls out to MCExpr::print(raw_ostream &OS) which then calls out to MCSymbolRefExpr::getVariantKindName() to print the magic :lower16: and :upper16: asm tags for .s emission Currently, movt/movw emission works correctly in .s, but not in .o emission This lead me to believe that the correct place to put the code to handle MCSymbolRefExpr::VK_ARM_(HI||LO)16 for the .o path was to place a case in getMachineOpValue() (i.e. not ARMMCCodeEmitter::getBinaryCodeForInstr li...

...I've recently changed the XCore target to implement BR_JT as a jump to a >>>>> series jumps. The jump table entries are expand inline in the function >>>>> so there is no longer a need to emit jump tables at the end of the >>>>> function. However the emission of jump tables at the end of a function >>>>> is done inside the AsmPrinter base class and there seems to be no way of >>>>> disabling this. >>>>> >>>>> This also seems to effect code produced for ARM Thumb2. Again each jump >>&gt...

Hi Robert: Thanks for your response, as well. I'm sorry. As you've discovered, I made some capitalization errors when posting my R code. The actual R code does use "lme", "data", and "random". The dataframe is indeed named "emiss" and each item in the formula is a column in the dataframe. I used the following R code to read in the comma-delimited file (first line contains headings): emiss <- read.table("data.csv", header=TRUE, sep=",") # NA for missing data (default) A review of the dat...

...ently changed the XCore target to implement BR_JT as a jump to a >>>>>> series jumps. The jump table entries are expand inline in the function >>>>>> so there is no longer a need to emit jump tables at the end of the >>>>>> function. However the emission of jump tables at the end of a function >>>>>> is done inside the AsmPrinter base class and there seems to be no way of >>>>>> disabling this. >>>>>> >>>>>> This also seems to effect code produced for ARM Thumb2. Again each...

...le ); builder.setEngineKind( llvm::EngineKind::Either ); // it will use JIT if available builder.setUseMCJIT ( true ); engine = builder.create(); These calls are successful in windows. But when I try in Linux (Ubuntu), the create() function fails with the error message: Target does not support MC emission Any ideas why and how to fix it? Thanks. -- Xinglin Zhang -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120807/5227c0e7/attachment.html>

...d the XCore target to implement BR_JT as a jump to a >>>>>>> series jumps. The jump table entries are expand inline in the function >>>>>>> so there is no longer a need to emit jump tables at the end of the >>>>>>> function. However the emission of jump tables at the end of a function >>>>>>> is done inside the AsmPrinter base class and there seems to be no way of >>>>>>> disabling this. >>>>>>> >>>>>>> This also seems to effect code produced for ARM Thu...