Displaying 14 results from an estimated 14 matches for "exp2f".
Did you mean:
exp2
2020 Oct 28
4
Targeting old glibc
...an old glibc?
I have a machine which is up to date (glibc 2.32 and clang+lld 10.0.1).
So far I've been able to target older glibc by having a C file containing:
__asm__(".symver powf,powf at GLIBC_2.2.5");
__asm__(".symver expf,expf at GLIBC_2.2.5");
__asm__(".symver exp2f,exp2f at GLIBC_2.2.5");
__asm__(".symver log2f,log2f at GLIBC_2.2.5");
__asm__(".symver logf,logf at GLIBC_2.2.5");
__asm__(".symver log,log at GLIBC_2.2.5");
__asm__(".symver log2,log2 at GLIBC_2.2.5");
__asm__(".symver exp,exp at GLIBC_2.2.5"...
2020 Nov 11
2
Targeting old glibc
...will be renamed to 'exp at GLIBC_2.2.5'
> and get bound to the old version at link time. It will thus work with
> old glibc.
I have one .cpp file with:
__asm__(".symver powf,powf at GLIBC_2.2.5");
__asm__(".symver expf,expf at GLIBC_2.2.5");
__asm__(".symver exp2f,exp2f at GLIBC_2.2.5");
__asm__(".symver log2f,log2f at GLIBC_2.2.5");
__asm__(".symver logf,logf at GLIBC_2.2.5");
__asm__(".symver log,log at GLIBC_2.2.5");
__asm__(".symver log2,log2 at GLIBC_2.2.5");
__asm__(".symver exp,exp at GLIBC_2.2.5"...
2020 Oct 28
2
Targeting old glibc
...libc 2.32 and clang+lld 10.0.1).
> >
> >So far I've been able to target older glibc by having a C file containing:
> >
> >__asm__(".symver powf,powf at GLIBC_2.2.5");
> >__asm__(".symver expf,expf at GLIBC_2.2.5");
> >__asm__(".symver exp2f,exp2f at GLIBC_2.2.5");
> >__asm__(".symver log2f,log2f at GLIBC_2.2.5");
> >__asm__(".symver logf,logf at GLIBC_2.2.5");
> >
> >__asm__(".symver log,log at GLIBC_2.2.5");
> >__asm__(".symver log2,log2 at GLIBC_2.2.5");
>...
2020 Nov 11
2
Targeting old glibc
...o the old version at link time. It will thus work with
> > > old glibc.
> >
> > I have one .cpp file with:
> >
> > __asm__(".symver powf,powf at GLIBC_2.2.5");
> > __asm__(".symver expf,expf at GLIBC_2.2.5");
> > __asm__(".symver exp2f,exp2f at GLIBC_2.2.5");
> > __asm__(".symver log2f,log2f at GLIBC_2.2.5");
> > __asm__(".symver logf,logf at GLIBC_2.2.5");
> >
> > __asm__(".symver log,log at GLIBC_2.2.5");
> > __asm__(".symver log2,log2 at GLIBC_2.2.5");...
2015 Mar 25
0
[PATCH] nv50/ir: take postFactor into account when doing peephole optimizations
...hole.cpp
@@ -451,7 +451,9 @@ ConstantFolding::expr(Instruction *i,
b->data.f32 = 0.0f;
}
switch (i->dType) {
- case TYPE_F32: res.data.f32 = a->data.f32 * b->data.f32; break;
+ case TYPE_F32:
+ res.data.f32 = a->data.f32 * b->data.f32 * exp2f(i->postFactor);
+ break;
case TYPE_F64: res.data.f64 = a->data.f64 * b->data.f64; break;
case TYPE_S32:
if (i->subOp == NV50_IR_SUBOP_MUL_HIGH) {
@@ -579,6 +581,7 @@ ConstantFolding::expr(Instruction *i,
i->src(0).mod = Modifier(0);
i->src...
2020 Nov 11
0
Targeting old glibc
....2.5'
> > and get bound to the old version at link time. It will thus work with
> > old glibc.
>
> I have one .cpp file with:
>
> __asm__(".symver powf,powf at GLIBC_2.2.5");
> __asm__(".symver expf,expf at GLIBC_2.2.5");
> __asm__(".symver exp2f,exp2f at GLIBC_2.2.5");
> __asm__(".symver log2f,log2f at GLIBC_2.2.5");
> __asm__(".symver logf,logf at GLIBC_2.2.5");
>
> __asm__(".symver log,log at GLIBC_2.2.5");
> __asm__(".symver log2,log2 at GLIBC_2.2.5");
> __asm__(".symve...
2020 Nov 09
0
Targeting old glibc
...).
> > >
> > >So far I've been able to target older glibc by having a C file containing:
> > >
> > >__asm__(".symver powf,powf at GLIBC_2.2.5");
> > >__asm__(".symver expf,expf at GLIBC_2.2.5");
> > >__asm__(".symver exp2f,exp2f at GLIBC_2.2.5");
> > >__asm__(".symver log2f,log2f at GLIBC_2.2.5");
> > >__asm__(".symver logf,logf at GLIBC_2.2.5");
> > >
> > >__asm__(".symver log,log at GLIBC_2.2.5");
> > >__asm__(".symver log2,log2 at...
2020 Nov 11
0
Targeting old glibc
...me. It will thus work with
>> > > old glibc.
>> >
>> > I have one .cpp file with:
>> >
>> > __asm__(".symver powf,powf at GLIBC_2.2.5");
>> > __asm__(".symver expf,expf at GLIBC_2.2.5");
>> > __asm__(".symver exp2f,exp2f at GLIBC_2.2.5");
>> > __asm__(".symver log2f,log2f at GLIBC_2.2.5");
>> > __asm__(".symver logf,logf at GLIBC_2.2.5");
>> >
>> > __asm__(".symver log,log at GLIBC_2.2.5");
>> > __asm__(".symver log2,log2 at...
2013 Sep 18
2
[LLVMdev] JIT compiled intrinsics calls is call to null pointer
Hi everyone,
I am trying to call an LLVM intrinsic (llvm.pow.f32), inserted with the
following call:
std::vector<llvm::Type *>
arg_types;arg_types.push_back(llvm::Type::getFloatTy(context));auto
function=llvm::Intrinsic::getDeclaration(module, llvm::Intrinsic::pow,
arg_types);auto result=ir_builder->CreateCall(function, args);
When I try to execute the code generated by the JIT
2020 Nov 09
2
Targeting old glibc
...t; > >So far I've been able to target older glibc by having a C file containing:
> > > >
> > > >__asm__(".symver powf,powf at GLIBC_2.2.5");
> > > >__asm__(".symver expf,expf at GLIBC_2.2.5");
> > > >__asm__(".symver exp2f,exp2f at GLIBC_2.2.5");
> > > >__asm__(".symver log2f,log2f at GLIBC_2.2.5");
> > > >__asm__(".symver logf,logf at GLIBC_2.2.5");
> > > >
> > > >__asm__(".symver log,log at GLIBC_2.2.5");
> > > >__asm__(&...
2020 Nov 10
2
Targeting old glibc
Thank you very much for your help Fāng-ruì Sòng.
I've tried various things like linking directly to libm-2.32 but it
didn't work, it seems that libm-2.32 still pulls libmvec.
I have the following linker flags:
CLANG_LDFLAGS="-fuse-ld=lld -static-libstdc++ -static-libgcc
-fvisibility=hidden -fdata-sections -ffunction-sections"
CLANG_LDFLAGS="$CLANG_LDFLAGS
2012 Aug 02
2
[LLVMdev] Proposal to merge SimplifyLibCalls into InstCombiner
...len, strpbrk, strtol, strtod, strtof, strtoul,
strtoll, strtold, strtoull, strtold, strtoull, strspn, strcspn, strstr,
memcmp, memcpy, memmove, memset, __strcpy_chk, cosf, cos, cosl, powf,
pow, powl, llvm.pow.f32, llvm.pow.f64, llvm.pow.f80, llvm.pow.f128,
llvm.pow.ppcf128, exp21, exp2, exp2f, llvm.exp2.ppcf128, llvm.exp2.f128,
llvm.exp2.f80, llvm.exp2.f64, llvm.exp2.f32, floor, cell, round, rint,
nearbyint, ffs, ffsl, ffsll, abs, labs, llabs, isdigit, isascii,
toascii, sprintf, print, fwrite, fputs, fprintf, puts.
Test cases that exercise the library call folders for each of...
2015 Jan 20
3
[LLVMdev] strlen in fast-isel
It seems that fast-isel for intel does not handle strlen. It's a general
problem in fast-isel .
~/llvmw/build/Deb~/llvmw/build/Debug+Asserts/bin/clang -O0 -mllvm
-fast-isel-verbose -mllvm -fast-isel strlen1.c
strlen1.c:12:3: warning: implicitly declaring library function 'printf' with
type 'int (const char *, ...)'
printf("%i\n", len);
^
2020 Feb 02
0
Wine release 5.1
...ddraw/tests: Don't use log2f to avoid mingwex dependency.
jscript: Introduce jsstr_to_bstr helper.
jscript: Store source position in instr_t.
jscript/tests: Add more error reporting tests.
jscript/tests: Add more script enter notification tests.
msvcrt: Provide exp2f in importlib.
winegcc: Use Wine crt when linking to msvcrt.
vbscript: Overflow hex literals in 16-bit range.
vbscript: Fix VT_UNKNOWN handling in set statements.
vbscript: Fix VT_UNKNOWN handling in is expressions.
scrrun: Add MoveFile implementation.
mshtml/test...