search for: expansions

...ses over the line, >>> parsing, processing metacharacters, and expanding variables. And >>> I don't know where to find a concise description of that any more. >> >> man bash, about 900 lines down under "EXPANSION". > > But it is not 'just' expansions. You need to know the full order of > operations with all the steps - word splitting, quote removal, i/o > redirection, groupings, etc., some of which is repeated over the line > after some of the other steps happen. I think I saw this in an > understandable form for the bourne shel...

Hi Eli, Thank you for the patch! Yet something to improve: [auto build test ERROR on next-20200715] url: https://github.com/0day-ci/linux/commits/Eli-Cohen/VDPA-support-for-Mellanox-ConnectX-devices/20200716-155039 base: ca0e494af5edb59002665bf12871e94b4163a257 config: mips-allyesconfig (attached as .config) compiler: mips-linux-gcc (GCC) 9.3.0 reproduce (this is a W=1 build):

tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/mst/vhost.git linux-next head: 39c226b6b576b23d6d558331e6895f02b0892555 commit: 990055c63121520ad29deca72b1167b392563ddd [16/17] virtio-balloon: Add support for providing unused page reports to host config: riscv-allmodconfig (attached as .config) compiler: riscv64-linux-gcc (GCC) 7.4.0 reproduce: wget

Hi Eli, Thank you for the patch! Yet something to improve: [auto build test ERROR on next-20200715] url: https://github.com/0day-ci/linux/commits/Eli-Cohen/VDPA-support-for-Mellanox-ConnectX-devices/20200716-155039 base: ca0e494af5edb59002665bf12871e94b4163a257 config: i386-allyesconfig (attached as .config) compiler: gcc-9 (Debian 9.3.0-14) 9.3.0 reproduce (this is a W=1 build):

On Tue, Aug 04, 2020 at 07:20:36PM +0300, Eli Cohen wrote: > Hi Michael, > please note that this series depends on mlx5 core device driver patches > in mlx5-next branch in > git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git. > > git pull git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git mlx5-next > > They also depend Jason Wang's

On Wed, Aug 05, 2020 at 03:40:54PM +0300, Eli Cohen wrote: > On Wed, Aug 05, 2020 at 08:00:55AM -0400, Michael S. Tsirkin wrote: > > On Tue, Aug 04, 2020 at 07:20:36PM +0300, Eli Cohen wrote: > > > Hi Michael, > > > please note that this series depends on mlx5 core device driver patches > > > in mlx5-next branch in > > >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 14/02/15 16:53, Les Mikesell wrote: <snip> > To understand it completely you need to know the order of > operations as the shell makes multiple passes over the line, > parsing, processing metacharacters, and expanding variables. And > I don't know where to find a concise description of that any more. man bash, about 900

On Sat, Feb 14, 2015 at 1:13 PM, Robert Nichols <rnicholsNOSPAM at comcast.net> wrote: > >> But it is not 'just' expansions. You need to know the full order of >> operations with all the steps - word splitting, quote removal, i/o >> redirection, groupings, etc., some of which is repeated over the line >> after some of the other steps happen. I think I saw this in an >> understandable form for...

...um(x) # N* number of total combinations How to write f(x) in a general framework? Quid of this framework when e1 and e2 are completed with their lags if q > 1? Your help or advice would be greatly appreciated Bilel -- View this message in context: http://r.789695.n4.nabble.com/RE-taylor-expansions-with-real-vectors-tp4636886.html Sent from the R help mailing list archive at Nabble.com.

tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/mst/vhost.git linux-next head: f2c4b499aecc0c5a1ec67f3a2a7310cb7168a8ab commit: 4c145987a955269da79312a79ec26638712644bb [8/9] vhost: block speculation of translated descriptors config: mips-malta_kvm_defconfig (attached as .config) compiler: mipsel-linux-gcc (GCC) 7.4.0 reproduce: wget

Hi Eli, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on next-20200715] url: https://github.com/0day-ci/linux/commits/Eli-Cohen/VDPA-support-for-Mellanox-ConnectX-devices/20200716-155039 base: ca0e494af5edb59002665bf12871e94b4163a257 config: i386-allyesconfig (attached as .config) compiler: gcc-9 (Debian 9.3.0-14) 9.3.0 reproduce (this is a W=1 build):

...their own expansion. Another option to consider is adding a new optimization pass for this expansion that isn’t target specific if other targets would benefit from a more general infrastructure. Please provide feedback if this approach should be continued to implement the PowerPC specific memcmp expansions or whether the community is interested in devising a more general approach. Thanks, Zaara Syeda -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161229/1990fc64/attachment.html>

...I'm trying to solve a problem that we have in implementation of the assembler for Mips platform in llvm. Mips has some pseudo instructions that, depending on the arguments can be emitted as one or more real instructions by the assembler. For example load immediate instruction can have multiple expansions depending on a size of immediate operand: This expansion is for 0 ≤ j ≤ 65535. li d,j => ori d,$zero,j This one is for −32768 ≤ j < 0. li d,j => addiu d,$zero,j This one is for any other value of j that is representable as a 32-bit integer. li d,j => lui d,hi16(j) ori d,d,lo16(j) I hav...

Hi Maciej, [auto build test ERROR on net-next/master] [also build test ERROR on v4.12-rc1 next-20170512] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Maciek-Fijalkowski/Fix-ERROR-trailing-statements-should-be-on-next-line/20170515-021304 config: x86_64-acpi-redef (attached as .config) compiler:

...her option to consider is adding a new optimization pass for this > expansion that isn’t target specific if other targets would benefit > from a more general infrastructure. > > Please provide feedback if this approach should be continued to > implement the PowerPC specific memcmp expansions or whether the > community is interested in devising a more general approach. > > Thanks, > > Zaara Syeda > > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listi...

Hi Eli, Thank you for the patch! Yet something to improve: [auto build test ERROR on next-20200715] url: https://github.com/0day-ci/linux/commits/Eli-Cohen/VDPA-support-for-Mellanox-ConnectX-devices/20200716-155039 base: ca0e494af5edb59002665bf12871e94b4163a257 config: ia64-allmodconfig (attached as .config) compiler: ia64-linux-gcc (GCC) 9.3.0 reproduce (this is a W=1 build):

Hello All, Does anyone know of an expansion module (keypad extension for attendant) that works with the gxp-2000? - Jason -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060508/f49a24e3/attachment.htm

...;m trying to solve a problem that we have in implementation of the assembler for Mips platform in llvm. Mips has some pseudo instructions that, depending on the arguments can be emitted as one or more real instructions by the assembler. > For example load immediate instruction can have multiple expansions depending on a size of immediate operand: > This expansion is for 0 ≤ j ≤ 65535. > li d,j => > ori d,$zero,j > This one is for −32768 ≤ j < 0. > li d,j => > addiu d,$zero,j > This one is for any other value of j that is representable as a 32-bit integer. > li d,j =&...

I don't have any guests with PAGE_SIZE > 64k but the code seems to be clearly broken in that case as PAGE_SIZE / MERGEABLE_BUFFER_ALIGN will need more than 8 bit and so the code in mergeable_ctx_to_buf_address does not give us the actual true size. Cc: John Fastabend <john.fastabend at gmail.com> Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Lightly tested on x86

I don't have any guests with PAGE_SIZE > 64k but the code seems to be clearly broken in that case as PAGE_SIZE / MERGEABLE_BUFFER_ALIGN will need more than 8 bit and so the code in mergeable_ctx_to_buf_address does not give us the actual true size. Cc: John Fastabend <john.fastabend at gmail.com> Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Lightly tested on x86