search for: uminers

...5: independent variable 2 (0/1), 1/2+ pack/dat at age 25 logw: weight to be used as an offset in the model rstime2: indicator variable to indicate whether age is below 50, 50-69 or >=70, used as strata in the model The SAS code is (if this helps to address my question/problem) proc phreg data=uminers; model rstime*cc(0)=cr500 smoke25/ entry=rsentry offset=logw rl; baseline out=ch covariates=covs cumhaz=cumhaz stdcumhaz=secumhaz lowercumhaz=lci uppercumhaz=uci/ nomean; strata rstime2; run; My R code is: library(survival) library(Design) > uminers<-read.table("uminers.txt&quot...

declare i8 @llvm.atomic.load.max.i8.p0i8( i8* <ptr>, i8 <delta> ) declare i16 @llvm.atomic.load.max.i16.p0i16( i16* <ptr>, i16 <delta> ) declare i32 @llvm.atomic.load.max.i32.p0i32( i32* <ptr>, i32 <delta> ) declare i64 @llvm.atomic.load.max.i64.p0i64( i64* <ptr>, i64 <delta> ) declare i8 @llvm.atomic.load.min.i8.p0i8( i8* <ptr>, i8

Full_Name: Christian Marquardt Version: 2.1.0 OS: Linux (Redhat 9) Submission from: (NULL) (151.170.240.10) Following the advice of a reader of R-help, I would now like to submit this as a bug report: Say we have x = seq(1,3, by = 0.01) y = exp(x) Plotting and reversing linear axis is fine plot(x,y) plot(x,y, ylim = c(30,1)) as is a usual log-plot: plot(x,y, log =

Its seems an bug in langref, is there anyone have an look or give an explain? 2010/5/5, 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com>: > declare i8 @llvm.atomic.load.max.i8.p0i8( i8* <ptr>, i8 <delta> ) > declare i16 @llvm.atomic.load.max.i16.p0i16( i16* <ptr>, i16 <delta> ) > declare i32 @llvm.atomic.load.max.i32.p0i32( i32* <ptr>, i32

On 9/17/2019 3:17 AM, Renato Golin wrote: > Hi Philip, > > Apologies for leaving this thread linger so long. It was in my > back-burner but Alex's weekly remind me to reply (thanks again, > Alex!). Starting from the end... > > On Mon, 9 Sep 2019 at 18:53, Philip Reames via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Current Plans >> >> At

Hi George, Have you considered changing our existing behavior to match GCC's builtin_object_size instead of adding a new parameter? That may be simpler overall. There's also a clear upgrade strategy -- fold every old style call to "<min> ? 0 : 1". You probably already know this, but GCC folds builtin_object_size(0, 0) to -1 and builtin_object_size(0, 2) to 0. We'll

I have been working on a patch to add support for max/min reductions in LoopVectorize. One of the comments that came up in review is that the implementation could be simplified (and less fragile) if max and min intrinsics were recognized rather than looking for compare-select sequences. The suggestion was to change compare-selects into max and min intrinsic calls during instcombine. The

Hi George, On Mon, Jan 2, 2017 at 10:41 AM, George Burgess IV <george.burgess.iv at gmail.com> wrote: > Thanks for the comments! > >> Have you considered changing our existing behavior to match GCC's >> builtin_object_size instead of adding a new parameter > > Yup! My issue with turning `i1 %min` into `i8 %flags` is that > __builtin_object_size would get

Hi there, This is summary and patch for a bug in read.dbf, demonstrating in Message-Id: <20050818150446.697835cb.stanimura-ngs at umin.ac.jp>. After consulting Rjpwiki, a cyber-community of R user in Japan, the cause was found, and the patch of solution was proposed. Overflowing occurs when we use read.dbf for reading a dbf file having a field of longer signed integer. For example, $

tl;dr: We'd like to add a bit to @llvm.objectsize to make it optionally be conservative when it's handed a null pointer. Happy Wednesday! We're trying to fix PR23277, which is a bug about how clang+LLVM treat __builtin_object_size when it's given a null pointer. For compatibility with GCC, clang would like to be able to hand back a conservative result (e.g. (size_t)-1), but the

I use R-1.5.1-1 on VineLinux2.6, which is modified and developed from RedHat7.2. Today I tried version-up R system, but I could not rebuild. Rebuilding R-1.6.2-1.src.rpm failed with the following message. make[5]: Leaving directory `/home/umusus/rpm/BUILD/R-1.6.2/src/library' running code in 'tcltk-Ex.R' ...X11 connection rejected because of wrong authentication. X connection to

On Dec 5, 2012, at 8:26 AM, "Redmond, Paul" <paul.redmond at intel.com> wrote: > I have been working on a patch to add support for max/min reductions in LoopVectorize. One of the comments that came up in review is that the implementation could be simplified (and less fragile) if max and min intrinsics were recognized rather than looking for compare-select sequences. > >

LLVM Weekly - #228, May 14th 2018 ================================= If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/228>. Welcome to the two hundred and twenty-eighth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by [Alex

I've recently mentioned in a few places that I'm interested in enhancing the loop vectorizer to handle multiple exit loops, and have been asked to share plans.  This email is intended to a) share my current thinking and b) help spark discussion among interested parties.  I do need to warn that my near term plans for this have been delayed; I got pulled into an internal project

Hi there, No information was found which version of XFree86 get along with R. I could not compile R version 1.8.1 with XFree86 4.3.99.902. Here is error message. gcc -I. -I../../../src/include -I../../../src/include -DI18N_MB -I/usr/X11R6/include -I/usr/local/include -DHAVE_CONFIG_H -D__NO_MATH_INLINES -mieee-fp -fPIC -O2 -pipe -march=i386 -mcpu=i686 -c dataentry_mb.c -o dataentry_mb.lo In

The Wine development release 1.9.15 is now available. What's new in this release (see below for details): - More shader instructions in Direct3D. - Performance improvements in GDI. - Better multi-joystick support on macOS. - Active Scripting improvements. - Additional stream support in the C++ runtime. - Various bug fixes. The source is available from the following locations:

Hi Tom, Matt, I'm running into strange issues with the cos test (piglit generated_tests/cl/builtin/math/builtin-float-cos-1.0.generated.c) I have been seeing random failures (incorrect results) for some time and tried to investigate. the weird part is that the failures are not 100% reproducible, sometimes the tests pass, or partly pass (it's usually float8 and float16 subtests that

Tom, I think it might be productive to fork this thread to discuss making the requirements for upstreaming a new LLVM target more explicit and open. I'd also like to gauge interest in an idea I've discussed privately with a few community members, namely the concept of having a semi-official "incubation" system whereby proposed backends could get a trial run before becoming part

The Wine development release 2.3 is now available. What's new in this release (see below for details): - Obsolete wineinstall script removed. - More Direct3D command stream work. - A few more Shader Model 5 instructions. - Better underline rendering in DirectWrite. - Improved ODBC support on 64-bit. - Various bug fixes. The source is available from the following locations:

On 05/04/2019 09:37, Simon Pilgrim via llvm-dev wrote: > On 04/04/2019 14:11, Sander De Smalen wrote: >> Proposed change: >> >> ---------------------------- >> >> In this RFC I propose changing the intrinsics for >> llvm.experimental.vector.reduce.fadd and >> llvm.experimental.vector.reduce.fmul (see options A and B). I also >> propose renaming