similar to: cleaning up the BUGS list

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

R-devel Digest Monday, September 24 2001 Volume 01 : Number 314 In this issue: [Rd] R 1.3.1 fails 'make check' on arm in the Bessel example (PR#1097) [Rd] Bug list summary (automatic post) [Rd] (PR#1089) Can be closed See the end of the digest for information about r-devel-digest ---------------------------------------------------------------------- Date: Fri, 21

{why do I get more and more messages sent to "owner-r-devel" or "owner-r-help" ?? "owner-foo" by convention (even RFC ???) is the (set of) maintainer(s) of mailing list "foo".. Please *do* post to "R-help" , "R-devel", and *NOT* to "owner-...." ! Martin Maechler = current owner-r-... ------- start of forwarded

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

I'd like to fit a multinomial log-linear model for 4 categories of the form log[(P(D=i | X)/P(D=0 | X)] = alpha_i + X beta_i ; i=1,2,3 but with beta_1 constrained to zero. Is there a way to impose such a constraint in the multinom function? Brad ------------------------------------------------------------------------- Brad McNeney email: mcneney at stat.sfu.ca

I'm having sporadic problems with glm on my alpha workstation running Compaq Tru64 UNIX V5.0 (I can't replicate the problem on my Linux PC). I have the same problem whether I use a version of R built with the native C-compiler or a version compiled with gcc. In both cases I've built with g77. I want to do some simulations with a call to glm in each rep. A simplified version would be

Hi Rohith, > I'm actually working on building a dependence graph . I'm not able > to find the methods which llvm uses to build the CFG. Is it possible to > use the same functions do build a dependence graph ( i Know the CFG > nodes are basicblocks where as dependence graph nodes will be variables)?. LLVM does not have explicit methods to build the CFG because it is

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

Run the verifier pass after your pass. The bitcode readers and writers assume that the IR is well-formed, which yours may not be. Reid On Sun, May 2, 2010 at 1:08 AM, Rohith Goparaju <rgoparaj at umail.iu.edu> wrote: > Hi, > >   I've written a pass that basically does some code transformations to > enable parallel execution. After the transformation llvm runs BitCode

{again a message that was sent to owner-r-help (which is me, currently) why on earth ???!??!? reply to R-help or the original sender Brett Presnell; } I'm teaching a categorical data analysis course this term, and a minor "problem" has resurfaced that I have often thought about before. This applies equally to Splus I suppose, but my undergrads aren't using Splus. It

Just to update: What I originally thought was a glm problem appears to be a memory problem that occurs only when R is compiled with the DEC C compiler. Some variables that are still in use get clobbered during garbage collection. No problems if I compile with gcc though. I've made some attempts to see if I can identify a specific compiler optimization that is responsible, but so far no luck.