Displaying 20 results from an estimated 28 matches for "libmvec".
Did you mean:
libexec
2020 Sep 01
3
Vectorization of math function failed?
...e:
> On Tue, Sep 1, 2020 at 9:07 AM Venkataramanan Kumar
> <venkataramanan.kumar.llvm at gmail.com <mailto:venkataramanan.kumar.llvm at gmail.com>> wrote:
> > Hi Alexandre,
>
> Hi Venkataramanan,
>
> > I am not sure if we can generate vector calls to GlibC libmvec.
> Is the support for libmvec on the roadmap? If not how to add it?
>
> I also wanted to check with others here, if we can add support for vector routines in Glibc libmvec.
>
> Libmvec may not be available in machines which uses lower versions of glibc. We may have to take care o...
2020 Sep 01
2
Vectorization of math function failed?
On Tue, Sep 1, 2020 at 9:07 AM Venkataramanan Kumar
<venkataramanan.kumar.llvm at gmail.com> wrote:
> Hi Alexandre,
Hi Venkataramanan,
> I am not sure if we can generate vector calls to GlibC libmvec.
Is the support for libmvec on the roadmap? If not how to add it?
> ./clang --autocomplete=-fveclib=
This is amazing, thank you! I think it should be documented in clang
auto vectorization documentation.
Thank you very much,
--
Alexandre BIQUE
2020 Sep 15
2
Vectorization of math function failed?
Hi Venkat.,
Did you make progress with libmvec?
Is there a chance that it lands into clang 11?
Regards,
Alexandre Bique
On Tue, Sep 1, 2020 at 11:50 AM Venkataramanan Kumar
<venkataramanan.kumar.llvm at gmail.com> wrote:
>
> Hi Florian,
>
> On Tue, 1 Sep, 2020, 3:11 pm Florian Hahn, <florian_hahn at apple.com> wrote:
&...
2020 Nov 09
2
Targeting old glibc
No. A shared object is needed if it is linked in (1)--no-as-needed
mode or (2) after --gc-sections, a symbol referenced by a live input
section is defined by the shared object.
You'll need to check whether a symbol is defined by libmvec.so.1
On Mon, Nov 9, 2020 at 9:57 AM Alexandre Bique
<bique.alexandre at gmail.com> wrote:
>
> On Mon, Nov 9, 2020 at 6:52 PM Fāng-ruì Sòng <maskray at google.com> wrote:
> > Recent libm.a and libm.so are actually linker scripts
> >
> > % cat /usr/lib/x86_64-linu...
2020 Nov 09
2
Targeting old glibc
...ojects/Podolski/CMakeFiles/Podolski.dir/__/__/AudioModulesFrame/AM_PitchTrack.cpp.o:
> reference to exp
> /usr/lib/libm.so.6: shared definition of exp at GLIBC_2.2.5
> /usr/lib/libm.so.6: shared definition of exp
> /usr/lib/libm.so.6: shared definition of exp at GLIBC_2.29
> /usr/lib/libmvec.so.1: reference to exp at GLIBC_2.29
>
> So the dependency is being pulled by libmvec.
>
> Which is strange because the target is not using libmvec:
>
> [jenkins at archear build-clang.64]$ ldd VstPlugins/libPodolski.so
> linux-vdso.so.1 (0x00007ffccff47000)
> libexpat.so.1...
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 -Wl,--gc-sections -Wl,-O1
-Wl,--as-needed -Wl,--strip-all"
CLANG_LDFLAGS="$CLANG_LDFLAGS...
2020 Nov 10
0
Targeting old glibc
On Tue, Nov 10, 2020 at 12:27 AM Alexandre Bique
<bique.alexandre at gmail.com> wrote:
>
> 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 -Wl,--gc-sections -Wl,-O1
> -Wl,--as-needed -Wl,--strip-all"
&...
2020 Oct 28
2
Targeting old glibc
On Wed, Oct 28, 2020 at 6:07 PM Fangrui Song <maskray at google.com> wrote:
>
> On 2020-10-28, Alexandre Bique via llvm-dev wrote:
> >Hi,
> >
> >I wonder what is the right way to target 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
2020 Nov 09
0
Targeting old glibc
...gt; section is defined by the shared object.
A shared object is needed if it is linked in (1) --no-as-needed mode
or (2) after --gc-sections, a symbol referenced by a live input
section is defined by the shared object as non-STB_WEAK.
> You'll need to check whether a symbol is defined by libmvec.so.1
>
> On Mon, Nov 9, 2020 at 9:57 AM Alexandre Bique
> <bique.alexandre at gmail.com> wrote:
> >
> > On Mon, Nov 9, 2020 at 6:52 PM Fāng-ruì Sòng <maskray at google.com> wrote:
> > > Recent libm.a and libm.so are actually linker scripts
> > >
&g...
2020 Nov 09
0
Targeting old glibc
....c.o:
reference to exp
Projects/Podolski/CMakeFiles/Podolski.dir/__/__/AudioModulesFrame/AM_PitchTrack.cpp.o:
reference to exp
/usr/lib/libm.so.6: shared definition of exp at GLIBC_2.2.5
/usr/lib/libm.so.6: shared definition of exp
/usr/lib/libm.so.6: shared definition of exp at GLIBC_2.29
/usr/lib/libmvec.so.1: reference to exp at GLIBC_2.29
So the dependency is being pulled by libmvec.
Which is strange because the target is not using libmvec:
[jenkins at archear build-clang.64]$ ldd VstPlugins/libPodolski.so
linux-vdso.so.1 (0x00007ffccff47000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007...
2020 Nov 11
2
Targeting old glibc
On Tue, Nov 10, 2020 at 7:01 PM Fāng-ruì Sòng <maskray at google.com> wrote:
> > How to find what is pulling libmvec?
>
> If you build a -DCMAKE_BUILD_TYPE=Debug lld, you can set a breakpoint
> on lld/ELF/MarkLive.cpp:114 (ss->getFile().isNeeded) and check which
> symbol makes
> libmvec.so needed.
I'm afraid this is going to far for me :)
> > On the other hand, I don't understand...
2020 Sep 01
2
Vectorization of math function failed?
I've tried to do:
clang++ -O3 -march=native -mtune=native \
-Rpass=loop-vectorize,slp-vectorize
-Rpass-missed=loop-vectorize,slp-vectorize
-Rpass-analysis=loop-vectorize,slp-vectorize \
-ffast-math -ffp-model=fast -ffp-exception-behavior=ignore -ffp-contract=fast \
-c -o vec.o vec.cc
But I've got no feedback.
--
Alexandre Bique
2020 Nov 09
0
Targeting old glibc
...-ruì Sòng <maskray at google.com> wrote:
> Recent libm.a and libm.so are actually linker scripts
>
> % cat /usr/lib/x86_64-linux-gnu/libm.a
> /* GNU ld script
> */
> OUTPUT_FORMAT(elf64-x86-64)
> GROUP ( /usr/lib/x86_64-linux-gnu/libm-2.31.a
> /usr/lib/x86_64-linux-gnu/libmvec.a )
> % cat /usr/lib/x86_64-linux-gnu/libm.so
> /* GNU ld script
> */
> OUTPUT_FORMAT(elf64-x86-64)
> GROUP ( /lib/x86_64-linux-gnu/libm.so.6 AS_NEEDED (
> /lib/x86_64-linux-gnu/libmvec.so.1 ) )
In this script the libmvec is mentioned as "AS_NEEDED", and it is not
need...
2020 Nov 11
2
Targeting old glibc
...Podolski.64.so
>
> Alexandre Bique
>
> On Wed, Nov 11, 2020 at 2:19 PM Alexandre Bique
> <bique.alexandre at gmail.com> wrote:
> >
> > On Tue, Nov 10, 2020 at 7:01 PM Fāng-ruì Sòng <maskray at google.com> wrote:
> > > > How to find what is pulling libmvec?
> > >
> > > If you build a -DCMAKE_BUILD_TYPE=Debug lld, you can set a breakpoint
> > > on lld/ELF/MarkLive.cpp:114 (ss->getFile().isNeeded) and check which
> > > symbol makes
> > > libmvec.so needed.
> >
> > I'm afraid this is going...
2020 Nov 11
0
Targeting old glibc
...:
patchelf --clear-symbol-version log Podolski.64.so
Alexandre Bique
On Wed, Nov 11, 2020 at 2:19 PM Alexandre Bique
<bique.alexandre at gmail.com> wrote:
>
> On Tue, Nov 10, 2020 at 7:01 PM Fāng-ruì Sòng <maskray at google.com> wrote:
> > > How to find what is pulling libmvec?
> >
> > If you build a -DCMAKE_BUILD_TYPE=Debug lld, you can set a breakpoint
> > on lld/ELF/MarkLive.cpp:114 (ss->getFile().isNeeded) and check which
> > symbol makes
> > libmvec.so needed.
>
> I'm afraid this is going to far for me :)
>
> > >...
2020 Nov 11
0
Targeting old glibc
...; Alexandre Bique
>>
>> On Wed, Nov 11, 2020 at 2:19 PM Alexandre Bique
>> <bique.alexandre at gmail.com> wrote:
>> >
>> > On Tue, Nov 10, 2020 at 7:01 PM Fāng-ruì Sòng <maskray at google.com> wrote:
>> > > > How to find what is pulling libmvec?
>> > >
>> > > If you build a -DCMAKE_BUILD_TYPE=Debug lld, you can set a breakpoint
>> > > on lld/ELF/MarkLive.cpp:114 (ss->getFile().isNeeded) and check which
>> > > symbol makes
>> > > libmvec.so needed.
>> >
>> > I...
2018 Aug 07
2
id <username> - doesnt list all groups
Thank for your answer:
But i dont know understand why is following not working:
I want to restrict the ssh access for a special domain member:
In my "sshd_config" i added:
AllowGroups restrictaccess root
With user2 im able to login via ssh!
log: pam_krb5(sshd:auth): user user2 authenticated as user2 at ROOTRUDI.DE
With user1 im not!
log: User user1 from 192.168.0.100 not allowed
2007 Sep 15
0
(PR#9910) Incomplete library linking for grDevices.so on
...om: (NULL) (136.159.169.6)
>
>
> When compiling R 2.6.1 (alpha 2007-09-13), grDevices.so fails to link
> properly because of a missing symbol __vlog_.
That is not what the error message reproduced below says, which comes from
the runtime loader.
> This symbol is defined in
> libmvec.so, but no -lmvec is add by the configure script. Manually
> adding -lmvec to the linking command allows grDevices to compile. The
> error output of the make command (for a 64-bit version of R) is given
> below:
>
> cc -G -m64 -L/lib/64 -L/usr/lib/64 -L/usr/local/lib/64 -L/usr/u...
2020 Aug 31
2
Vectorization of math function failed?
...1 43 3c vmovss %xmm0,0x3c(%rbx)
1e2: 48 83 c4 10 add $0x10,%rsp
1e6: 5b pop %rbx
1e7: c3 retq
As you can see there is no call to a vectorized version of sin.
Did I do something wrong?
By the way I am on Linux with glibc 2.32 which has libmvec.
Regards,
--
Alexandre Bique
2016 Mar 02
4
Proposal for function vectorization and loop vectorization with function calls
...g
references [2].
References
==========
1. OpenMP SIMD language extensions: http://www.openmp.org/mp-documents/openmp-4.
5.pdf
2. VectorABI Documentation:
https://www.cilkplus.org/sites/default/files/open_specifications/Intel-ABI-Vecto
r-Function-2012-v0.9.5.pdf
https://sourceware.org/glibc/wiki/libmvec?action=AttachFile&do=view&target=Vecto
rABI.txt
[[Note: VectorABI was reviewed at X86-64 System V Application Binary Interface
mailing list. The discussion was recorded at
https://groups.google.com/forum/#!topic/x86-64-abi/LmppCfN1rZ4 ]]
3. The first paper on SIMD extensio...