search for: aco

I'm trying to figure out exactly how the intrinsics/libc/libm work in llvm. For example, this code return user defined function: float acos(float x, float y) { return x+y; } float a; void foo(float b, float c) { a = acos(b, c); } But this code returns llvm.intrinsic: float acos(float, float); float a; void foo(float b, float c) { a = acos(b, c); } float acos(float x, float y) { return x+y; } What is the expected behavio...

Hello, I don't know if the result of acos(0.5) == pi/3 is a bug or not. It looks strange to me. Inaki Murillo

Hi all, I have to calculate an expression using acos -function. A strange result of acos appears *1. case with error* ss <- sin(10.74*pi/180)**2 +(cos(10.74*pi/180)*cos(10.74*pi/180)*cos(0*pi/180)) ss acos(ss) [1] NaN Warning message: NaNs produced in: acos(ss) *2. case without error* ss <- sin(10.7*pi/180)**2 +(cos(10.7*pi/180)*...

Hello, I'm looking at compiling some pieces of the standard library with llvm but I'm running into problems with some functions being renamed by dragonegg. For example, when I compile the acos implementation with plain gcc I get: $ nm acos.o 0000000000000000 r .LC1 0000000000000048 r .LC10 0000000000000050 r .LC11 0000000000000058 r .LC12 0000000000000060 r .LC13 0000000000000068 r .LC14 0000000000000070 r .LC15 0000000000000008 r .LC2 0000000000000010 r .LC3 0000000000000018 r .LC4 00...

In the first code I see a 'tail call @acos', in the second code I see a tail call @llvm.acos.f32'. (sorry, there should be only one input for acos, I've been trying many libm/libc functions). Not sure why it's called TargetLibraryInfo if it's not in target specific code? It seems that ALL targets use this code, making...

Hi Gregory, > I'm looking at compiling some pieces of the standard library with llvm but I'm > running into problems with some functions being renamed by dragonegg. For > example, when I compile the acos implementation with plain gcc I get: > > $ nm acos.o > 0000000000000000 r .LC1 > 0000000000000048 r .LC10 > 0000000000000050 r .LC11 > 0000000000000058 r .LC12 > 0000000000000060 r .LC13 > 0000000000000068 r .LC14 > 0000000000000070 r .LC15 > 0000000000000008 r .LC2 &...

Hello all. I''m the tech writer at XenSource, Inc., and I''ve been asked to ride herd on getting the revised Xen 3.0 User''s Manual put together, reviewed, etc. We are targeting a review draft for 11/21 and it would be great if any significant additions or changes that any contributers might be making could get checked in before then so the review process can be as

Hi, Before I try to code this myself, I'd like to know if anyone has a fixed-point routine to compute the cos and acos functions. All I need is around 3-digit accuracy. Thanks. Jean-Marc -- Jean-Marc Valin, M.Sc.A., ing. jr. LABORIUS (http://www.gel.usherb.ca/laborius) Université de Sherbrooke, Québec, Canada -------------- next part -------------- A non-text attachment was scrubbed... Name: signat...

...Bougacha <ahmed.bougacha at gmail.com> > wrote: > >> On Thu, Jun 9, 2016 at 11:28 AM, Ryan Taylor <ryta1203 at gmail.com> wrote: >> > I'm assuming that "__builtin_" is a keyword in LLVM. If I have code >> like: >> > >> > #define acos __builtin_acos >> > >> > extern double acos(double, double); >> > >> > double a; >> > void foo(float b) { >> > a = acos(b); >> > } >> > >> > I never see a call to "__builtin_acos", is LLVM removing the pre...

Hi. I have a question about the taylor.diagram() in plotrix package. How can I control the label "correlation"? In the embedded figure you can see the label "correlation" is too close to the ticks. How can I move it and make it larger? Another problem is the labels "0.95" and "0.99" are too close to the plotting area. I do not find any method to control

...solve a related but different - CodeGen - problem. RTLIB libcalls are used when we're not able to select some IR instruction/intrinsic so have to rely on a runtime library helper function (e.g., the stuff in compiler-rt/lib/builtins/). So, #1 and #2 would make LLVM able to emit calls to __xxx_acos when it sees "@llvm.acos.f32", but it won't let LLVM optimize (constant fold, transform into the intrinsic, ...) "__xx_acos()" when it sees it. It sounds like you also want to recognize and optimize these calls. That involves (pre-CodeGen) IR-level optimizations. No, I don...

Hi Duncan, Ah, non-unicode email... In the llvm output there should be a "1" character, i.e. (char) 0x01, prepended to acos and __GI_acos. I'm unable to get it on smaller things, but it happens when I try to compile uClibc with llvm. I've attached the .o and the .bc for comparison. The text file is the result after preprocessing (to avoid having to download a bunch of stuff). Here is the compile line that I...

...nrow(x), nrow(x)) for (i in 1:nrow(x)){ for(j in 1:nrow(x)){ if (i > j) res[i, j] <- res[j, i] else { v1 <- x[i,] v2 <- x[j,] good <- !is.na(v1) & !is.na(v2) v1 <- v1[good] v2 <- v2[good] theta <- acos(v1%*%v2 / sqrt(v1%*%v1 * v2%*%v2 )) / pi * 180 res[i,j] <- theta } } } as.dist(res) }

...ind == 1) { panel.abline(h = 0, lty = "dashed") panel.abline(v = 0, lty = "dashed") if(ncol(rotation) == 2) { ## Sometimes rotation[1,1] is 2.2e-16 above one rotation[1,1] <- min(rotation[1,1], 1) panel.abline(0, tan(acos(rotation[1, 1])), lty = "solid") panel.abline(0, 1/tan(acos(-rotation[1, 1])), lty = "solid") } else { Y <- cbind(x,y) %*% t(rotation) for (k in seq_len(ncol(Y))) { tmp <- matrix(0, nrow = 2, ncol = ncol(Y))...

Tim, Are you referring to setLibcallName? That is target specific yes but there isn't RTLIB for most of the libm functions, for example, for acos this doesn't apply. Ideally what I would like is to create a libc with functions like acos called something like __xxx_acos that can still be recognized to be optimized. RTLIB is pretty limited but it works fine, I can just use setLibcallName(RTLIB::floor, "__xxx_floor")... but a...

Full_Name: Robin Hankin Version: 2.4.0 RC OS: MacOSX 10.4.7 Submission from: (NULL) (139.166.242.29) The first cut line described in Trig.Rd for asin() is incorrect in the ascii version of the manpage. The Rd file reads: For \code{asin()} and \code{acos()}, there are two cuts, both along the real axis: \eqn{\left(-\infty, -1\right]}{\(-Inf,...

...me structure so that all the things in cache for search engines and/or articles pointing to wiki can still work) or move to something different and indeed keeping existing wiki.centos.org in Read-Only mode I'd like to avoid Github specifically but having something else that would permit to use ACO (https://acccounts.centos.org) as auth source. I already played with gitea and it works with openid so self-hosted git instance using ACO works fine. (but that's a different thread) We should divide all parts into specific areas. Benefits of using .md means being able to switch to something el...

...gets converted to be ‘__exp_finite’ in the IR. Because some of the optimizations like constant folding or vectorization are looking for the original function name, those optimizations do not get triggered under –ffast-math due to these alternative function names. Other affected functions include: acos, asin, exp2, log, log2, log10, and a few others. Anybody know if this is intentional, or have input regarding whether these optimizations should be extended to also look for the renamed versions of these functions? Thanks, Chris A couple of example cases: // File: test_folding.c // Cons...

Dear all, I am new to plotting Taylor Diagram using plotrix package within R, hence this post. I have written a script which plots Taylor Diagram with one reference and 7 model values. However the font size, line width and line type are not clear when saving the diagram as a jpeg file. I tried the functions lty, lwd and font but no apparent change. I am attaching the script here. Any help would

...t;- length(b) h <- hist( dd, breaks=b, plot=FALSE) FisherAvgdPdf <- function(theta,theta0,kappa){ A <- kappa/(2*sinh(kappa)) A * I.0( kappa*sin(theta)*sin(theta0) ) * exp( kappa*cos(theta)*cos(theta0) ) } nls(dens ~ FisherAvgdPdf(theta,theta0,kappa), data = data.frame( theta=acos(h$mids), dens=h$density ), start=c( theta0=0.5, kappa=4.0 ), algorithm="port", lower=c(0,0), upper=c(acos(xlims[1]),500), control=list(warnOnly=TRUE) ) ##------------------------------------------------------------------ On one machine, nls converges, and on the other it...