search for: svfs

...s2.c.orig 2008-11-18 16:37:41.000000000 +0100 --- source/smbd/trans2.c 2009-07-01 12:17:16.000000000 +0200 *************** *** 2583,2612 **** --- 2583,2642 ---- CIFS_UNIX_POSIX_PATH_OPERATIONS_CAP))); break; case SMB_QUERY_POSIX_FS_INFO: { int rc; vfs_statvfs_struct svfs; if (!lp_unix_extensions()) { return ERROR_NT(NT_STATUS_INVALID_LEVEL); } rc = SMB_VFS_STATVFS(conn, ".", &svfs); if (!rc) { + + { + SMB_BIG_UINT dfree,dsize,bsize,block_size,sectors_per_unit,bytes_per_sector; + + if (get_dfree_info(c...

...to >> a non-standard name, which allows the use of existing vector libraries. >> >> The `vector-variant` attribute needs to be attached on a per-call basis >> to avoid conflicts when merging modules with different vector variants. >> >> The query infrastructure: SVFS {#infrastructure} >> ------------------------------ >> >> The Search Vector Function System (SVFS) is constructed from an >> `llvm::Module` instance so it can create function definitions. The SVFS >> exposes an API with two methods. >> >> ### `SVFS::isFunct...

...icit mapping of the Vector Function ABI mangled name to a non-standard name, which allows the use of existing vector libraries. The `vector-variant` attribute needs to be attached on a per-call basis to avoid conflicts when merging modules with different vector variants. The query infrastructure: SVFS {#infrastructure} ------------------------------ The Search Vector Function System (SVFS) is constructed from an `llvm::Module` instance so it can create function definitions. The SVFS exposes an API with two methods. ### `SVFS::isFunctionVectorizable` This method queries the avilability of a ve...

...allows the use of existing vector libraries. >>>> >>>> The `vector-variant` attribute needs to be attached on a per-call basis >>>> to avoid conflicts when merging modules with different vector variants. >>>> >>>> The query infrastructure: SVFS {#infrastructure} >>>> ------------------------------ >>>> >>>> The Search Vector Function System (SVFS) is constructed from an >>>> `llvm::Module` instance so it can create function definitions. The SVFS >>>> exposes an API with two metho...

...ies. >>>>>> >>>>>> The `vector-variant` attribute needs to be attached on a per-call basis >>>>>> to avoid conflicts when merging modules with different vector variants. >>>>>> >>>>>> The query infrastructure: SVFS {#infrastructure} >>>>>> ------------------------------ >>>>>> >>>>>> The Search Vector Function System (SVFS) is constructed from an >>>>>> `llvm::Module` instance so it can create function definitions. The SVFS >>>&g...

...;>>>>>>> The `vector-variant` attribute needs to be attached on a per-call basis >>>>>>>> to avoid conflicts when merging modules with different vector variants. >>>>>>>> >>>>>>>> The query infrastructure: SVFS {#infrastructure} >>>>>>>> ------------------------------ >>>>>>>> >>>>>>>> The Search Vector Function System (SVFS) is constructed from an >>>>>>>> `llvm::Module` instance so it can create function def...

...;> The `vector-variant` attribute needs to be attached on a per-call basis >>>>>>>>>> to avoid conflicts when merging modules with different vector variants. >>>>>>>>>> >>>>>>>>>> The query infrastructure: SVFS {#infrastructure} >>>>>>>>>> ------------------------------ >>>>>>>>>> >>>>>>>>>> The Search Vector Function System (SVFS) is constructed from an >>>>>>>>>> `llvm::Module` instan...

Hi all, I am submitting the following RFC [1] to re-implement -fveclib via OpenMP constructs. The RFC was discussed during a round table at the last LLVM developer meeting, and presented during the BoF [2]. The proposal is published on Phabricator, for the purpose of keeping track of the comments, and it now ready for a review from a wider audience after being polished by Hal Finkel and Hideki

...t` attribute needs to be attached on a per-call basis >>>>>>>>>>>> to avoid conflicts when merging modules with different vector variants. >>>>>>>>>>>> >>>>>>>>>>>> The query infrastructure: SVFS {#infrastructure} >>>>>>>>>>>> ------------------------------ >>>>>>>>>>>> >>>>>>>>>>>> The Search Vector Function System (SVFS) is constructed from an >>>>>>>>>&g...

...attached on a per-call basis >>>>>>>>>>>>>> to avoid conflicts when merging modules with different vector variants. >>>>>>>>>>>>>> >>>>>>>>>>>>>> The query infrastructure: SVFS {#infrastructure} >>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>> >>>>>>>>>>>>>> The Search Vector Function System (SVFS) is constructed from an >>>&g...

...t;>>>>>> The `vector-variant` attribute needs to be attached on a per-call basis > >>>>>>> to avoid conflicts when merging modules with different vector variants. > >>>>>>> > >>>>>>> The query infrastructure: SVFS {#infrastructure} > >>>>>>> ------------------------------ > >>>>>>> > >>>>>>> The Search Vector Function System (SVFS) is constructed from an > >>>>>>> `llvm::Module` instance so it can create function...

...”, is the component that demangles the data > in the `vector-function-abi-variant` attribute and that provides the > instances of the class `VectorFunctionShape` that can be derived by > the mangled names listed in the attribute. > > ## Query interface: Search Vector Function System (SVFS) > > An interface that can be queried by the LLVM components to understand > whether or not a scalar function can be vectorized, and that retrieves > the vector function to be used if such vector shape is available. > > 1. This component is going to be unrelated to OpenMP. > 2....

...eciphering after the fact is feasible. > I will provide the cases for AArch64. > I think we can make further progress on trivial cases (where FE doesn’t “change” type) while we continue working out the details on non-trivial cases. > I think we can agree to proceed these way. The SVFS and the VectorShapeInfo are (I believe) designed with extendibility as a requirements. If we need more metadata to represent some specific cases, we will extend the SVFS internal to handle such metadata. I will update the RFC by moving the vector function signature generation in the FE. Thank yo...

...v <llvm-dev at lists.llvm.org> writes: > Hi all - I am working with a colleague to provide an initial implementation of this. > > We encountered a problem when dealing with generating the vector signatures of functions that use complex data. > > In this proposal, we expect the SVFS component in the backed to > demangle the name of the function in the attribute to be able to > reconstruct the signature of the vector function from the scalar > function signature. > > In case of Complex data, this doesn’t seem to be possible, because the > information of “being...

...RFC: Interface user provided vector functions with the vectorizer. Hi all - I am working with a colleague to provide an initial implementation of this. We encountered a problem when dealing with generating the vector signatures of functions that use complex data. In this proposal, we expect the SVFS component in the backed to demangle the name of the function in the attribute to be able to reconstruct the signature of the vector function from the scalar function signature. In case of Complex data, this doesn’t seem to be possible, because the information of “being a vector of 2 lanes” that is...

...RFC: Interface user provided vector functions with the vectorizer. Hi all - I am working with a colleague to provide an initial implementation of this. We encountered a problem when dealing with generating the vector signatures of functions that use complex data. In this proposal, we expect the SVFS component in the backed to demangle the name of the function in the attribute to be able to reconstruct the signature of the vector function from the scalar function signature. In case of Complex data, this doesn’t seem to be possible, because the information of “being a vector of 2 lanes” that is...

...ariant` attribute needs to be attached on a > > >>>>>>>>> per-call basis to avoid conflicts when merging modules with different vector variants. > > >>>>>>>>> > > >>>>>>>>> The query infrastructure: SVFS {#infrastructure} > > >>>>>>>>> ------------------------------ > > >>>>>>>>> > > >>>>>>>>> The Search Vector Function System (SVFS) is constructed from > > >>>>>>>>>...

...t; The `vector-variant` attribute needs to be attached on a per-call basis > >>>>>>>>> to avoid conflicts when merging modules with different vector variants. > >>>>>>>>> > >>>>>>>>> The query infrastructure: SVFS {#infrastructure} > >>>>>>>>> ------------------------------ > >>>>>>>>> > >>>>>>>>> The Search Vector Function System (SVFS) is constructed from an > >>>>>>>>> `llvm::Module` in...

...ctor-variant` attribute needs to be attached on a >>>>>>>>>>> per-call basis to avoid conflicts when merging modules with different vector variants. >>>>>>>>>>> >>>>>>>>>>> The query infrastructure: SVFS {#infrastructure} >>>>>>>>>>> ------------------------------ >>>>>>>>>>> >>>>>>>>>>> The Search Vector Function System (SVFS) is constructed from >>>>>>>>>>> an `llv...

...ttribute needs to be attached on a > >>>>>>>>>>> per-call basis to avoid conflicts when merging modules with different vector variants. > >>>>>>>>>>> > >>>>>>>>>>> The query infrastructure: SVFS {#infrastructure} > >>>>>>>>>>> ------------------------------ > >>>>>>>>>>> > >>>>>>>>>>> The Search Vector Function System (SVFS) is constructed > >>>>>>>>>&...