Displaying 20 results from an estimated 34371 matches for "maths".
Did you mean:
math
2017 Sep 29
2
Trouble when suppressing a portion of fast-math-transformations
Hi all,
In a mailing-list post last November:
http://lists.llvm.org/pipermail/llvm-dev/2016-November/107104.html
I raised some concerns that having the IR-level fast-math-flag 'fast' act as an
"umbrella" to implicitly turn on all the lower-level fast-math-flags, causes
some fundamental problems. Those fundamental problems are related to
situations where a user wants to
2017 Sep 29
0
Trouble when suppressing a portion of fast-math-transformations
Hi, Warren,
Thanks for writing all of this up. In short, regarding your suggested
solution:
> 4. To fix this, I think that additional fast-math-flags are likely
> needed in
>
> the IR. Instead of the following set:
>
> 'nnan' + 'ninf' + 'nsz' + 'arcp' + 'contract'
>
> something like this:
>
> 'reassoc' +
2018 Feb 06
2
libc++ cross-compile linux-armv7 and math function problems
Hello,
I am trying to cross-compile libc++ from my x86_64 linux system to armv7hf.
We have our own gcc compiler that we build with crosstools-ng (based on gcc
6.3.0) and I set my environment like this:
CC=armv7a-plex-linux-gnueabihf-gcc
CXX=armv7a-plex-linux-gnueabihf-g++
CFLAGS=-fPIC -DPIC -mfloat-abi=hard -march=armv7-a -Os -mfpu=vfpv3-d16
--sysroot=<path>
CXXFLAGS=-fPIC -DPIC
2018 Feb 06
0
libc++ cross-compile linux-armv7 and math function problems
At first glance, it looks like long double functions (such as fabsl and friends) are missing from your sysroot's <math.h>. Does your target support long double at all?
-Dimitry
> On 6 Feb 2018, at 09:51, Tobias Hieta via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> Hello,
>
> I am trying to cross-compile libc++ from my x86_64 linux system to armv7hf. We have
2018 Feb 06
1
libc++ cross-compile linux-armv7 and math function problems
Hello Dimitry and thanks for your answer.
I am pretty sure it does indeed support long double. It's configured with
vfpv3-d16 - but I noticed that c++config.h in gcc has _GLIBCXX__HAS_FABSL
and friends are undefined. I think I need to look deeper at the
configuration of our toolchain.
long double support is required in libc++ then I gather?
-- Tobias
On Tue, Feb 6, 2018 at 11:47 AM,
2006 May 15
1
Trying to get values to display on horizontal barchart
Hello,
R 2.3.0
Windows XP
I have spent quite a bit of time trying to resolve my problem below, which included a R site search.
The "vertical bars" syntax below produces a vertical bar chart with the values displayed above each bar. I want to cast this graphic horizontally, but I have not been able to arrive at a suitable outcome. The best I have been able to do, using the second block
2007 Jul 03
0
Branch 'as' - 7 commits - libswfdec/swfdec_as_math.c libswfdec/swfdec_as_object.c libswfdec/swfdec_movie.c libswfdec/swfdec_sprite_movie.c test/trace
libswfdec/swfdec_as_math.c | 16 ++++++++--------
libswfdec/swfdec_as_object.c | 3 ++-
libswfdec/swfdec_movie.c | 12 +++++-------
libswfdec/swfdec_sprite_movie.c | 3 ++-
test/trace/Makefile.am | 7 +++++++
test/trace/math-constants-5.swf |binary
test/trace/math-constants-5.swf.trace | 8 ++++++++
2018 Feb 05
0
Cross-compiling libc++ to linux-armv7hf gives undefined symbols in cmath / math.h
Hello,
I am trying to cross-compile libc++ from my x86_64 linux system to armv7hf.
We have our own gcc compiler that we build with crosstools-ng (based on gcc
6.3.0) and I set my environment like this:
CC=armv7a-plex-linux-gnueabihf-gcc
CXX=armv7a-plex-linux-gnueabihf-g++
CFLAGS=-fPIC -DPIC -mfloat-abi=hard -march=armv7-a -Os -mfpu=vfpv3-d16
--sysroot=<path>
CXXFLAGS=-fPIC -DPIC
2009 Apr 09
0
Processed: Update submitter address for my bugs
Processing commands for control at bugs.debian.org:
> # bugs from schepler at math.unipd.it
> submitter 390095 !
Bug#390095: klash: No control keys working
Changed Bug submitter from Daniel Schepler <schepler at math.unipd.it> to Daniel Schepler <dschepler at gmail.com>.
> submitter 419472 !
Bug#419472: aegis: FTBFS under pbuilder even building as non-root
Changed Bug
2016 Nov 16
3
RFC: Consider changing the semantics of 'fast' flag implying all fast-math-flags
Hi all,
This is about https://reviews.llvm.org/D26708
Currently when the command-line switch '-ffast-math' is specified, the
IR-level fast-math-flag 'fast' gets attached to appropriate FP math
instructions. That flag acts as an "umbrella" to implicitly turn on all the
other fast-math-flags ('nnan', 'ninf', 'nsz' and 'arcp'):
2016 Nov 17
2
RFC: Consider changing the semantics of 'fast' flag implying all fast-math-flags
On 17.11.2016 09:51, Ristow, Warren wrote:
> Those are all good points. Your reassociation point in the context of
> inlining is particularly interesting.
>
>
>
> FWIW, we also have a case where a customer wants '-fno-associative-math'
> to suppress reassociation under '-ffastmath'. It would take me a while
> to find the specifics of the issue, but it was
2020 May 27
4
default behavior or
Hi Devs,
going by this link https://llvm.org/docs/LangRef.html#floatenv
it says that floating point operation does not have side effects by
defaults.
but when compile a test case
i.e.
cat a.c
float foo(float a, float b)
{
return a+b;
}
$clang a.c -O2 -S -emit-llvm
emit ir like:
$cat a.ll
---------------------------------------
; ModuleID = 'a.c'
source_filename = "a.c"
target
2016 Nov 16
5
RFC: Consider changing the semantics of 'fast' flag implying all fast-math-flags
----- Original Message -----
> From: "Mehdi Amini via llvm-dev" <llvm-dev at lists.llvm.org>
> To: "Warren Ristow" <warren.ristow at sony.com>
> Cc: llvm-dev at lists.llvm.org
> Sent: Tuesday, November 15, 2016 11:10:48 PM
> Subject: Re: [llvm-dev] RFC: Consider changing the semantics of
> 'fast' flag implying all fast-math-flags
> Hi,
2012 Nov 15
3
[LLVMdev] [PATCH] fast-math patches!
New patches with review feedback incorporated:
* Changed single letter flags to short abbreviations ('S' ==> 'nsz')
* Indentation fixes
* Comments don't state function names
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Fast-math-flags-added-to-FPMathOperator.patch
Type: application/octet-stream
Size: 4937 bytes
Desc: not
2016 Nov 17
2
RFC: Consider changing the semantics of 'fast' flag implying all fast-math-flags
> On Nov 17, 2016, at 8:03 AM, Sanjay Patel <spatel at rotateright.com> wrote:
>
> On Thu, Nov 17, 2016 at 2:31 AM, Nicolai Hähnle via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> On 17.11.2016 09:51, Ristow, Warren wrote:
> Those are all good points. Your reassociation point in the context of
> inlining is particularly
2016 Sep 20
4
LLVM v3.9.0 and math built-ins
Hi Mehdi,
The ISO C specification does permit the math functions to modify ‘errno’, but I thought that the ‘-fno-math-errno’ option was to tell the optimiser to assume that ‘errno’ is not modified by the math functions. Explicitly providing ‘-fno-math-errno’ is not restoring the elision optimisation that was performed by LLVM v3.8, and this is really only a driver option, with ‘-fmath-errno’
2012 Nov 15
0
[LLVMdev] [llvm-commits] [PATCH] fast-math patches!
Trying to apply patches..
What's your base revision?
Joe
On Nov 15, 2012, at 5:44 PM, Michael Ilseman <milseman at apple.com> wrote:
> New patches with review feedback incorporated:
> * Changed single letter flags to short abbreviations ('S' ==> 'nsz')
> * Indentation fixes
> * Comments don't state function names
>
>
2017 Mar 20
2
-ffast-math optimizations impacted by symbol renaming in header files
Hi,
I came across an issue where some optimizations that would normally be applied to standard math function calls are not getting applied when the –ffast-math option is enabled on the Clang command line on a Linux x86_64 target.
I tracked down the issue to occurring because the –ffast-math option is triggering Clang to preprocess the math.h header file with the __FINITE_MATH_ONLY__ macro set
2016 Sep 16
2
LLVM v3.9.0 and math built-ins
A little while ago I asked a question on CFE-Dev about a change in the
behaviour of programs using the ISO C math functions, although that question
should have been put to LLVM-Dev. But I got excellent clarification of the
problem anyway. However, since then I have been trying to adapt our
out-of-tree implementation to get the previous behaviour. The problem is
that something like:
#include
2016 Nov 17
2
RFC: Consider changing the semantics of 'fast' flag implying all fast-math-flags
If we take this argument to its end: any one of those relaxed FP settings
*guarantees* that we cannot ensure that the result will be the same between
two versions of clang. Therefore, we can no-op all of them, and greatly
simplify the optimizer.
I know that's not what you're advocating, but the suggestion that we remove
'arcp' is the first step on that path. We can't do that.