Displaying 20 results from an estimated 3000 matches similar to: "[LLVMdev] FPOpFusion = Fast and Multiply-and-add combines"
2014 Jul 31
2
[LLVMdev] FPOpFusion = Fast and Multiply-and-add combines
Hi Tim,
Thanks for the thorough explanation. It makes perfect sense.
I was not aware fast-math is supposed to prevent more precision being used
than what is in the standard.
I came across this issue while looking into the output or different
compilers. XL and Microsoft compiler seem
to have that turned on by default. But I assume that clang follows what gcc
does, and have that turned off.
2014 Aug 07
2
[LLVMdev] FPOpFusion = Fast and Multiply-and-add combines
Hi Sanjay,
You are right. I tried XL and gcc 4.8.2 for PPC and I also got
multiply-and-add operations.
I supported my statement on what I read in the gcc man page. -ffast-math is
used in clang to set fp-contract to fast (default is standard) and in gcc
it activates (among others) the flag -funsafe-math-optimizations whose
description includes:
"Allow optimizations for floating-point
2014 Nov 05
2
[LLVMdev] Issue with std::call_once in PPC64 platform
It seems the crash of llvm/clang build on aarch64 Debian has been fixed by
r220941.
Thanks,
-Jiangning
2014-11-05 8:45 GMT+08:00 Jiangning Liu <liujiangning1 at gmail.com>:
> The versions I'm using right now are
>
> * gcc: (Debian/Linaro 4.9.1-14) 4.9.1
> * libstdc++: libstdc++.so.6.0.20
>
> Thanks,
> -Jiangning
>
> 2014-11-05 4:46 GMT+08:00 Chris Bieneman
2014 Sep 05
4
[LLVMdev] [cfe-dev] Address sanitizer regression test failures for PPC64 targets
Note that I've set the SA_NODEFER flag for the SEGV handler in the
ASan runtime only a couple of days ago.
Not sure that could've affected this test though; without that flag
the second SEGV would've simply crashed the program. But you can try
removing the flag from
compiler-rt/trunk/lib/sanitizer_common/sanitizer_posix_libcdep.cc and
see if that makes any difference.
HTH,
Alex
On
2014 Sep 26
2
[LLVMdev] [cfe-dev] Address sanitizer regression test failures for PPC64 targets
On Mon, 2014-09-08 at 22:00 -0400, Samuel F Antao wrote:
> Alexey, Alexander,
>
> Thanks for the suggestions. I tried removing the flag SA_NODEFER but
> it didn't do any good... I have been digging into the problem with the
> null_deref test today but I was unable to clearly identify the
> problem. I suspect that it was either a bug with the calling
> convention/unwinding
2014 Oct 01
2
[LLVMdev] [cfe-dev] Address sanitizer regression test failures for PPC64 targets
On Mon, Sep 8, 2014 at 7:00 PM, Samuel F Antao <sfantao at us.ibm.com> wrote:
> Alexey, Alexander,
>
> Thanks for the suggestions. I tried removing the flag SA_NODEFER but it
> didn't do any good... I have been digging into the problem with the
> null_deref test today but I was unable to clearly identify the problem. I
> suspect that it was either a bug with the
2014 Sep 24
2
[LLVMdev] noalias and alias.scope metadata producers
Hal, Johannes,
Thanks for the feedback. I have been digging into this a little bit more
and was able to have some of this metadata being generated. Nevertheless, I
am confused about the semantics of this metadata. Let me explain:
I was expecting the alias metadata to complement the information that alias
analysis passes compute. However, it seems that the alias information of
the pointers used
2014 Nov 04
4
[LLVMdev] Issue with std::call_once in PPC64 platform
Hi all,
I observe that r220932 (Removing the static initializer in
ManagedStatic.cpp by using llvm_call_once to initialize the ManagedStatic
mutex.) is causing tablegen to segfault in PPC platforms during static
initialization. The crash happens while calling std::call_once introduced
by this patch in the wrapper used in getManagedStaticMutex.
I understand this call is buggy for some platforms
2013 Jan 11
3
[LLVMdev] Documentation of fmuladd intrinsic
On Fri, Jan 11, 2013 at 1:08 PM, Andrew Booker <andrew.booker at arm.com>wrote:
> The fmuladd intrinsic is described as saying that a multiply and
> addition sequence can be fused into an fma instruction "if the code
> generator determines that the fused expression would be legal and
> efficient". (http://llvm.org/docs/LangRef.html#llvm-fma-intrinsic)
>
>
2016 Nov 18
2
what does -ffp-contract=fast allow?
----- Original Message -----
> From: "Sanjay Patel" <spatel at rotateright.com>
> To: "Hal J. Finkel" <hfinkel at anl.gov>
> Cc: "Mehdi Amini" <mehdi.amini at apple.com>, "llvm-dev"
> <llvm-dev at lists.llvm.org>, "cfe-dev" <cfe-dev at lists.llvm.org>,
> "andrew kaylor" <andrew.kaylor at
2016 Nov 18
2
what does -ffp-contract=fast allow?
Sent from my Verizon Wireless 4G LTE DROID
On Nov 17, 2016 5:53 PM, Mehdi Amini <mehdi.amini at apple.com<mailto:mehdi.amini at apple.com>> wrote:
>
>
>> On Nov 17, 2016, at 4:33 PM, Hal Finkel <hfinkel at anl.gov<mailto:hfinkel at anl.gov>> wrote:
>>
>>
>> ________________________________
>>>
>>> From: "Warren
2013 Jan 11
0
[LLVMdev] Documentation of fmuladd intrinsic
----- Original Message -----
> From: "Cameron McInally" <cameron.mcinally at nyu.edu>
> To: "Andrew Booker" <andrew.booker at arm.com>
> Cc: llvmdev at cs.uiuc.edu
> Sent: Friday, January 11, 2013 12:37:07 PM
> Subject: Re: [LLVMdev] Documentation of fmuladd intrinsic
>
>
> On Fri, Jan 11, 2013 at 1:08 PM, Andrew Booker <
>
2014 Nov 04
2
[LLVMdev] Issue with std::call_once in PPC64 platform
Ok, I'll put a patch together to fix this later today. I'll probably do
what Reid was suggesting and use what is already in there for Windows.
Thanks,
Samuel
Bill Schmidt <wschmidt at linux.vnet.ibm.com> wrote on 11/04/2014 12:11:08 PM:
> From: Bill Schmidt <wschmidt at linux.vnet.ibm.com>
> To: Samuel F Antao/Watson/IBM at IBMUS
> Cc: azanella at
2014 Nov 04
2
[LLVMdev] Issue with std::call_once in PPC64 platform
Adding Jiangning Liu to the thread.
Jiangning reported a similar issue on the llvm-commits list on Debian aarch64.
In general it sounds like std::call_once may not really be bug free.
Jiangning, can you please provide your gcc/libstdc++ version?
Thanks,
-Chris
> On Nov 4, 2014, at 9:38 AM, Bill Schmidt <wschmidt at linux.vnet.ibm.com> wrote:
>
> On Tue, 2014-11-04 at 12:17
2014 Nov 04
2
[LLVMdev] Issue with std::call_once in PPC64 platform
Hi Bill,
You can find the same issue in the buildbot:
http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux2/builds/16444/steps/compile.llvm.stage2/logs/stdio
It is failing for me both in BE (gcc 4.8.2) and LE(4.9.1). I am compiling
with clang 3.5, but those are the gcc toolchains I am using.
What do you think is the best way to fix this?
Thanks!
Samuel
Bill Schmidt <wschmidt at
2018 Aug 22
2
Condition code in DAGCombiner::visitFADDForFMACombine?
On 22.08.2018 17:52, Ryan Taylor wrote:
> This is probably going to effect on other backends and break llvm-lit
> for them?
Very likely, yes. Can you take a look at how big the fallout is? This
might give us a hint about what other frontends might expect, and who
needs to be involved in the discussion (if one is needed).
Cheers,
Nicolai
>
> On Wed, Aug 22, 2018 at 11:41 AM
2014 Sep 05
2
[LLVMdev] Address sanitizer regression test failures for PPC64 targets
Hi all,
I have been experiencing the failure of the address sanitizer regression
tests for a PPC64 target (Power7 machine). My understanding is that most of
the failures are related with the fact the stack is not being dumped.
I tried to understand what might be wrong and started by looking into the
null_deref.cc test as it hangs during the test run. I observe that after
the detection of the
2015 Jun 23
2
[LLVMdev] SafeStack pass and TLS support
Hi all,
Shouldn't SafeStack pass be executed only if the target has TLS support?
E.g. currently for NVPTX there is no way to implement
`__safestack_unsafe_stack_ptr`.
Any comments?
Thanks,
Samuel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150623/53f40bea/attachment.html>
2018 Aug 23
3
Condition code in DAGCombiner::visitFADDForFMACombine?
I don't think the global fast math flag should override the NoContraction
decoration as that's mostly the point of that decoration to begin with, to
have fine granular control while still having a broad sweeping
optimization. Did I miss your point? I feel like I did.
On Thu, Aug 23, 2018, 3:42 PM Michael Berg <michael_c_berg at apple.com> wrote:
> Ryan,
>
> Given that the
2013 Jan 11
1
[LLVMdev] Documentation of fmuladd intrinsic
Hal Finkel <hfinkel at anl.gov> writes:
> There are a few conditions that contribute to the decision of whether
> or not to make the fmuladd -> fma translation. The relevant code is in
> CodeGen/SelectionDAG/SelectionDAGBuilder.cpp:
>
> case Intrinsic::fmuladd: {
> EVT VT = TLI.getValueType(I.getType());
> if (TM.Options.AllowFPOpFusion !=