search for: mpra

When I run R CMD Rd2pdf on the man pages of a package, ie R CMD Rd2pdf man I get Converting Rd files to LaTeX Warning in parse_Rd("man/mpra-package.Rd", encoding = "unknown", fragment = FALSE, : man/mpra-package.Rd:6: unknown macro '\packageTitle' Warning in parse_Rd("man/mpra-package.Rd", encoding = "unknown", fragment = FALSE, : man/mpra-package.Rd:9: unknown macro '\packageDescrip...

No, I do not get the same as you. I have tested with R-devel and R-patched compiled today. When I do R CMD Rd2pdf mpra I get (as reported a few days ago) Hmm ... looks like a package Converting Rd files to LaTeX Error : mpra/man/mpra-package.Rd:6: file './DESCRIPTION' does not exist whereas you (Kurt) reports that this works on zTree. When I do R CMD Rd2pdf mpra/man I get - a pdf produced - warni...

...I'm reading this right. The constraints are that: > a) All four operands have distinct registers. > b) The first two are in a consecutive pair (second > first) > c) The second two are in a consecutive pair (fourth > third) Constraints b & c are OK, but a is too strict : "mpra %R0, %R1, %R0, %R1" is OK. But I though, may be wrongly, that "mpra %vreg1, %vreg2, %vreg3, %vreg4" meant %vreg1 and %vreg3 will be allocated to different physical registers, or they would have been coalesced. For example, the pass I added after the coalescer ensures that instruction...

When I include the macros \packageAuthor, \packageDescription, \packageTitle, \packageMaintainer in a XX-package.Rd file, R CMD Rd2pdf fails with $ R CMD Rd2pdf mpra Hmm ... looks like a package Converting Rd files to LaTeX Error : mpra/man/mpra-package.Rd:6: file './DESCRIPTION' does not exist This does not happen if I comment out 4 occurrences of these 4 macros in mpra-package.Rd. This is with R Under development (unstable) (2017-09-26 r73351) -- &...

Hi Arnaud, The patch looks good. I've committed it in r133249. > > > I noticed an unexpected --- to me at least --- behaviour of the allocator. > > I have some instructions using 2 pairs of registers, say “mpra R_x, R_x+1, > R_y, R_y+1”, and setting the pairing constraints R_x -> R_x+1 and R_y -> > R_y+1 could silently produce wrong code like “mpra %R0, %R2, %R1, %R3”. I > add to explicitly add another constraint to describe that y must differ > from x, x-1 and x+1 to make the allocator...

...f the pbqp. I used it to undo some of the coalescer work, and make sure that I have different virtual registers, inserting a copy if necessary, to build a pair. I noticed an unexpected --- to me at least --- behaviour of the allocator. I have some instructions using 2 pairs of registers, say "mpra R_x, R_x+1, R_y, R_y+1", and setting the pairing constraints R_x -> R_x+1 and R_y -> R_y+1 could silently produce wrong code like "mpra %R0, %R2, %R1, %R3". I add to explicitly add another constraint to describe that y must differ from x, x-1 and x+1 to make the allocator buil...

...duncan at gmail.com> wrote: > On 26/09/2017 10:27 PM, Kasper Daniel Hansen wrote: > >> When I include the macros \packageAuthor, \packageDescription, >> \packageTitle, \packageMaintainer in a XX-package.Rd file, R CMD Rd2pdf >> fails with >> >> $ R CMD Rd2pdf mpra >> Hmm ... looks like a package >> Converting Rd files to LaTeX Error : mpra/man/mpra-package.Rd:6: file >> './DESCRIPTION' does not exist >> >> This does not happen if I comment out 4 occurrences of these 4 macros in >> mpra-package.Rd. >> >>...

On 26/09/2017 10:27 PM, Kasper Daniel Hansen wrote: > When I include the macros \packageAuthor, \packageDescription, > \packageTitle, \packageMaintainer in a XX-package.Rd file, R CMD Rd2pdf > fails with > > $ R CMD Rd2pdf mpra > Hmm ... looks like a package > Converting Rd files to LaTeX Error : mpra/man/mpra-package.Rd:6: file > './DESCRIPTION' does not exist > > This does not happen if I comment out 4 occurrences of these 4 macros in > mpra-package.Rd. > > This is with > > R Und...

Hi Arnaud, That sounds great. I look forward to seeing a patch. You may also look forward to big performance improvements in the PBQP allocator: I'm working on updates which will improve compile speeds and massively reduce memory use. Regards, Lang. On Tue, Jun 7, 2011 at 7:02 PM, Arnaud Allard de Grandmaison < Arnaud.AllardDeGrandMaison at dibcom.com> wrote: > > I also

I also considered this approach, but did not want to dive in the constraint handling for now. The PBQP path seemed easier at first sight --- and was easy to setup. And I always wanted to give a try to the pbqp :) I will add the hook to the pbqp and propose a patch if this looks clean enough. Thanks, -- Arnaud de Grandmaison -----Original Message----- From: Jakob Stoklund Olesen

Hola, ¿qué tal? Tengo una pregunta de esta