search for: rel

Dear R-users, I am a new user for R. I am eager to lean about it. I wanted to read and summary of the a simple data file I used the following, rel <- read.table("C:/Documents and Settings/ashta/My Documents/R_data/rel.dat", quote="",header=FALSE,sep="",col.names= c("id","orel","nrel")) summary(rel) Below is the error message, rel <- read.table("C:/Documents and S...

...$(KLIBCARCH)/klibc.ld diff --git a/usr/klibc/arch/ia64/crt0.S b/usr/klibc/arch/ia64/crt0.S index 722276e..2394cc4 100644 --- a/usr/klibc/arch/ia64/crt0.S +++ b/usr/klibc/arch/ia64/crt0.S @@ -14,10 +14,6 @@ _start: movl r3 = FPSR_DEFAULT ;; adds out0= 16,sp /* argc pointer */ - movl gp = @gprel(0f) -0: mov r9 = ip - ;; - sub gp = r9, gp /* back-compute gp value */ .body br.call.sptk.few rp = __libc_init diff --git a/usr/klibc/arch/ia64/klibc.ld b/usr/klibc/arch/ia64/klibc.ld new file mode 100644 index 0000000..d203d0a --- /dev/null +++ b/usr/klibc/arch/ia64/klibc.ld @@ -0,0 +1,2...

...h easier and faster to match against names. > This can be important in large programs compiled -ffunction-sections as there can be millions of sections to match. I understand the reason of having these conventions in linkers. On the other hand, there already exists a format with the fixed ".rel.ro" suffix for .data and .bss. Custom suffixes would also mean that the user code would depend more on implementation-specific things, i.e. prefixes. For example, one would wonder, should they annotate their data with __attribute__((section(...))) for ".data.rel.ro.my_section" or &qu...

...$(KLIBCARCH)/klibc.ld diff --git a/usr/klibc/arch/ia64/crt0.S b/usr/klibc/arch/ia64/crt0.S index 722276e..2394cc4 100644 --- a/usr/klibc/arch/ia64/crt0.S +++ b/usr/klibc/arch/ia64/crt0.S @@ -14,10 +14,6 @@ _start: movl r3 = FPSR_DEFAULT ;; adds out0= 16,sp /* argc pointer */ - movl gp = @gprel(0f) -0: mov r9 = ip - ;; - sub gp = r9, gp /* back-compute gp value */ .body br.call.sptk.few rp = __libc_init diff --git a/usr/klibc/arch/ia64/klibc.ld b/usr/klibc/arch/ia64/klibc.ld new file mode 100644 index 0000000..d203d0a --- /dev/null +++ b/usr/klibc/arch/ia64/klibc.ld @@ -0,0 +1,2...

...lector that implements some RTTI machinery in the form of a table. This table is used by the collector to trace and finalize garbage collected objects. We're thinking of using __attribute__((section(...))) so that the table can be created and merged at link time. We also use -fPIC and therefore rely on the dynamic linker to process relocations in this table after the program is loaded. At the same time, we want the table to be read-only after relocations are applied, in the same fashion as e.g. .got sections are write protected after eager binding (with -z,relro,-z,now). The custom section ca...

...: { *(.reginfo) } - .dynamic : { *(.dynamic) } - .hash : { *(.hash) } - .dynsym : { *(.dynsym) } - .dynstr : { *(.dynstr) } - .gnu.version : { *(.gnu.version) } - .gnu.version_d : { *(.gnu.version_d) } - .gnu.version_r : { *(.gnu.version_r) } - .rel.dyn : - { - *(.rel.init) - *(.rel.text .rel.text.* .rel.gnu.linkonce.t.*) - *(.rel.fini) - *(.rel.rodata .rel.rodata.* .rel.gnu.linkonce.r.*) - *(.rel.data .rel.data.* .rel.gnu.linkonce.d.*) - *(.rel.tdata .rel.tdata.* .rel.gnu.linkonce.td.*) - *(.rel.tb...

Hi all, I have a dataset of individuals where the variable ID corresponds to the identification of the household where the individual lives. rel.head stands for the relationship with the household head. so rel.head=1 is the household head, rel.head=2 is the spouse, rel.head=3 is the children. Here is an example to see how it looks like: df<-data.frame(ID=c("17100", "17100", "17101", "17102", &quo...

...ecord is a set of variable names, tab-separated like the rest of the rows. There are no row labels, thus the same number of tab-delimited fields in the header record and the following records. The read.table returns silently, and I can get a reasonable summary(con). But if I try something like plot(rel,len), where rel and len are two of the labels from the header row, I get Error in plot(rel, len) : object 'rel' not found I've tried many variations (different variables, adding "con." on the front, quoting, using field numbers instead of names, etc. I've also read...

Hello again, I m trying to use timereg package as you suggested (R2.7.1 on XP Pro). here is my script based on the example from timereg for a fine & gray model in which relt = time to event, rels = status 0/1/2 2=competing, 1=event of interest, 0=censored random = covariate I want to test library(timereg) rel<-read.csv("relapse2.csv", header = TRUE, sep = ",", quote="\"", dec=".", fill = TRUE, comment.char=""...

...t; > I was looking at the ARM ABI > docs(http://infocenter.arm.__com/help/topic/com.arm.doc.__ihi0044e/IHI0044E_aaelf.pdf > <http://infocenter.arm.com/help/topic/com.arm.doc.ihi0044e/IHI0044E_aaelf.pdf>) > and they mention. > > "A binary file may use REL or RELA relocations or a mixture of the > two (but multiple relocations for the same > address must use only one type)." > > Does LLVM emit rel/rela relocations with ARM ? > > > I hope not. Ew. The only reason this is Ew is that llvm has decided not to prepare...

..._linear_mapping(0, __PAGE_OFFSET, max_low_pfn, 0); } /* - * Return a pointer to the VMI function or a NOP stub + * Return a pointer to a VMI function or NULL if unimplemented */ static void *vmi_get_function(int vmicall) { @@ -678,12 +679,13 @@ static void *vmi_get_function(int vmical if (rel->type == VMI_RELOCATION_CALL_REL) return (void *)rel->eip; else - return (void *)vmi_nop; + return NULL; } /* * Helper macro for making the VMI paravirt-ops fill code readable. - * For unimplemented operations, fall back to default. + * For unimplemented operations, fall back to...

..._linear_mapping(0, __PAGE_OFFSET, max_low_pfn, 0); } /* - * Return a pointer to the VMI function or a NOP stub + * Return a pointer to a VMI function or NULL if unimplemented */ static void *vmi_get_function(int vmicall) { @@ -678,12 +679,13 @@ static void *vmi_get_function(int vmical if (rel->type == VMI_RELOCATION_CALL_REL) return (void *)rel->eip; else - return (void *)vmi_nop; + return NULL; } /* * Helper macro for making the VMI paravirt-ops fill code readable. - * For unimplemented operations, fall back to default. + * For unimplemented operations, fall back to...

I'm looking over good-code a post-doc in my lab wrote and trying to learn how it works. I came across the following: rel.abundance <- as.matrix(read.delim("rel.abundance.csv",row.names=1,as.is =TRUE)) rel.abundance <- log2(rel.abundance-min(rel.abundance)+1) I'm not sure what the second line is doing. I ran each line in R and couldn't see a noticeable difference in the output. I assume log2...

...I was looking at the ARM ABI >> docs(http://infocenter.arm.__com/help/topic/com.arm.doc.__ihi0044e/IHI0044E_aaelf.pdf >> <http://infocenter.arm.com/help/topic/com.arm.doc.ihi0044e/IHI0044E_aaelf.pdf>) >> and they mention. >> >> "A binary file may use REL or RELA relocations or a mixture of the >> two (but multiple relocations for the same >> address must use only one type)." >> >> Does LLVM emit rel/rela relocations with ARM ? >> >> >> I hope not. Ew. > > The only reason this is Ew is...

Hi, I was looking at the ARM ABI docs(http://infocenter.arm.com/help/topic/com.arm.doc.ihi0044e/IHI0044E_aaelf.pdf) and they mention. "A binary file may use REL or RELA relocations or a mixture of the two (but multiple relocations for the same address must use only one type)." Does LLVM emit rel/rela relocations with ARM ? Any tests ? Thanks Shankar Easwaran -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Lin...

Hi, I noticed that klibc started crashing on 64-bit MIPS and in my quest to fix the bug I got a bit carried away and fixed a few other things as well. Here are various miscellaneous MIPS patches, although the first patch is the important one. Thanks, James *** BLURB HERE *** James Cowgill (5): mips64: compile with -mno-abicalls mips: use -Ttext-segment when linking shared library

...: { *(.reginfo) } + .dynamic : { *(.dynamic) } + .hash : { *(.hash) } + .dynsym : { *(.dynsym) } + .dynstr : { *(.dynstr) } + .gnu.version : { *(.gnu.version) } + .gnu.version_d : { *(.gnu.version_d) } + .gnu.version_r : { *(.gnu.version_r) } + .rel.dyn : + { + *(.rel.init) + *(.rel.text .rel.text.* .rel.gnu.linkonce.t.*) + *(.rel.fini) + *(.rel.rodata .rel.rodata.* .rel.gnu.linkonce.r.*) + *(.rel.data .rel.data.* .rel.gnu.linkonce.d.*) + *(.rel.tdata .rel.tdata.* .rel.gnu.linkonce.td.*) + *(.rel.tb...

i want my html output to look like this: <a href="/path/to/page/" rel="tag">link text</a> how do i tell the link_to method that i need: rel="tag"? thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to thi...

...nt nva3_clock_pll_calc(struct nouveau_clock *, struct >> nvbios_pll *, >> int clk, struct nouveau_pll_vals *); >> int nouveau_clock_ustate(struct nouveau_clock *, int req, int pwr); >> -int nouveau_clock_astate(struct nouveau_clock *, int req, int rel); >> +int nouveau_clock_astate(struct nouveau_clock *, int req, int rel, bool >> wait); >> int nouveau_clock_dstate(struct nouveau_clock *, int req, int rel); >> int nouveau_clock_tstate(struct nouveau_clock *, int req, int rel); >> diff --git a/nvkm/subdev/clock...

...: { *(.reginfo) } + .dynamic : { *(.dynamic) } + .hash : { *(.hash) } + .dynsym : { *(.dynsym) } + .dynstr : { *(.dynstr) } + .gnu.version : { *(.gnu.version) } + .gnu.version_d : { *(.gnu.version_d) } + .gnu.version_r : { *(.gnu.version_r) } + .rel.dyn : + { + *(.rel.init) + *(.rel.text .rel.text.* .rel.gnu.linkonce.t.*) + *(.rel.fini) + *(.rel.rodata .rel.rodata.* .rel.gnu.linkonce.r.*) + *(.rel.data .rel.data.* .rel.gnu.linkonce.d.*) + *(.rel.tdata .rel.tdata.* .rel.gnu.linkonce.td.*) + *(.rel.tb...