search for: moving

libswfdec/swfdec_codec_video.c | 2 libswfdec/swfdec_movie.c | 3 test/trace/Makefile.am | 193 ++++++++++++ test/trace/place-object-5.swf |binary test/trace/place-object-5.swf.trace | 4 test/trace/place-object-6.swf

Folks, I'm running into something which looks like a bug in linearscan allocator. Of course I can't be 100% sure it's not some unobvious mistake on my part, so I'd like to hear your opinion. First, I attach two files -- LLVM asm and the asm for my target. The problem with assembler is: on line 171 it uses register gr2, which is copied from gr6 above, on line 161. The only

Hi, I have the following code and am using R 2.7.2: JIBqq <- (Jqrt.IB[2:length(Jqrt.IB)]/Jqrt.IB[1:(length(Jqrt.IB)-1)])-1 JIBqq <- cbind(zoo(JIBqq, Jqrt.time[2:length(Jqrt.time)])) y.JIBqq <- merge(JIBqq,lag(JIBqq,-1)) > y.JIBqq JIBqq lag(JIBqq, -1) 2004-06-30 0.003318909 NA 2004-09-30 -0.028536136 0.003318909

+ Erik, who implemented DR1579 Originally, I had the warning similar to GCC's warning, but took it out due to not having DR1579 implemented in clang (warning changed in r243594) Erik in r274291 implemented DR1579, although PR27785 didn't mention anything about std::move It looks like what's happening is that Clang and GCC handles the return differently. Clang needs the std::move

Hi, folks. I've started getting these errors from rsync, and any help would be appreciated: >ERROR: out of memory in string_area_new buffer >rsync error: error allocating core memory buffers (code 22) at util.c(115) >ERROR: out of memory in string_area_new buffer >rsync error: error allocating core memory buffers (code 22) at util.c(115) >ERROR: out of memory in

tag 334917 = patch thanks Hi, I?ve fixed the m68k syscall of klibc and made it able to use six-argument syscalls like mmap2. However, I could not yet fully test it (only mostly; opendir() specifically fails) due to: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47533 @m68k porters: Please have a look at the gcc bug as well. @klibc: Please apply the patch, it?s better than what we have, and

Here a patch to make move plugin take care of CompWindowActionMoveMask. http://hibbert.univ-lille3.fr/~cbellegarde/Compiz/respectWindowActions.patch There is also a bug in gtk-window-decorator. If you use this plugin: http://forum.go-compiz.org/viewtopic.php?t=643 Set your terminal to be non movable, terminal window doesn't have _NET_WM_ACTION_MOVE, but you can move it with decoration.

LLVMers, The LLVM.org <http://llvm.org/> server which hosts SVN, GIT mirror, documentation, and the main LLVM.org <http://llvm.org/> website is moving to a new server on June 24th. As a result of the move commit access will be locked out beginning 09:00PDT on the 24th. We hope to have the move complete and commit access restored to everyone in a timely manner, however, a move of this magnitude will take several hours to complete. In addition,...

The new move plugin interface that makes the applications sync to Xserver position at each move notify, also if it could be considered important, caused - as negative point - a poor wobbly quality while moving windows... That's why some kinds of "forks" were made to disable this new feature (see the "bouge" plugin), so I decided, instead of use "another" plugin simply to patch the git move plugins to add an option that will allow users to decide which move type should be...

The maildirsize file is double counting messages when moving them from folder to folder when "maildir_copy_with_hardlinks = no": 1024000000000S 99337571 19370 14010590 2 <--- moved from subfolder to subfolder -7005295 -1 14010590 2 <--- moved from subfolder to INBOX -7005295 -1 14010590 2 <--- moved from INBOX to subfold...

I wanted to move messages from a mbox mailbox on server A to mdbox on server B. I thought I could do this by connecting to the remote server with "doveadm move -S x.x.x.x:x -u testuser Archive/2017 mailbox INBOX/test" but I guess this will only allow and move messages internally on server B? Should I use dsync, or is there another way to move the messages?

...nother namespace? Do we need > > > to move the slaves too? > > > > No. Why would we move the slaves? The whole point is to make most customer ignore the net-failover slaves and remain them ?hidden? in their dedicated netns. > > We won?t prevent customer from explicitly moving the net-failover slaves out of this netns, but we will not move them out of there automatically. > > > The 2-device netvsc already handles case where master changes namespace. Is it by moving slave with it? -- MST

...nother namespace? Do we need > > > to move the slaves too? > > > > No. Why would we move the slaves? The whole point is to make most customer ignore the net-failover slaves and remain them ?hidden? in their dedicated netns. > > We won?t prevent customer from explicitly moving the net-failover slaves out of this netns, but we will not move them out of there automatically. > > > The 2-device netvsc already handles case where master changes namespace. Is it by moving slave with it? -- MST

Yes, we should produce this warning in C++11 mode too. (I could be misrecalling, but I think the rationale for the current behaviour is based on historical GCC behaviour.) On Sun, 16 Sep 2018, 10:04 David Blaikie via cfe-dev, < cfe-dev at lists.llvm.org> wrote: > Fair point made on that thread - that this is a DR, so technically the > std::move is pessimizing even in C++11 mode.

Debian: (Closes: #334917) Signed-off-by: Thorsten Glaser <tg at mirbsd.de> --- usr/klibc/arch/m68k/syscall.S | 42 +++++++++++++++++++++++++++++++++------- usr/klibc/arch/m68k/vfork.S | 13 +++-------- 2 files changed, 38 insertions(+), 17 deletions(-) diff --git a/usr/klibc/arch/m68k/syscall.S b/usr/klibc/arch/m68k/syscall.S index 966c92d..f468678 100644 ---

i everybody! first at all, sorry about my poor english... i''m working in a little experiment about boucing objects using Effect.Move implementation and a couple Effect.Transitions'' but... i was stuck in the way how Effect.Move works. I need to move a object in two dimensions: X and Y, but in different times.... Effect.Parallel not work for me, because meanwhile the object

Colin Walters (1): autogen.sh: Implement GNOME Build API Dylan Aïssi (1): Fix typo: Initalizing --> Initializing Emil Velikov (2): autogen.sh: use quoted string variables xf86-video-r128: remove the GlxSetVisualConfigs stub and friends Helmut Grohne (1): Fix for cross build failure Kevin Brace (31): Move the location where R128PreInitGamma is called

...olly later. LLVM provides some predefined ExtensionPointTy: EP_EarlyAsPossible, EP_ModuleOptimizerEarly, EP_LoopOptimizerEnd, EP_ScalarOptimizerLate, ... Currently Polly uses "EP_EarlyAsPossible" to run as early as possible. As what you suggested: >Instead of removing canonicalization passes, I believe we may want to >move Polly to a later place in the pass manager. Possibly at the >beginning of the loop optimizer right before PM.add(createLoopRotatePass()); I want to move it to the point immediate after someone Loop optimization pass, e.g. MPM.add(creat...

...ges=43 [@~]# doveadm mailbox status -u testuser -t messages INBOX/test2 messages=16 Also tried with doveadm -v copy -S 192.168.10.43:542 -u testuser INBOX/test2 user testuser mailbox test >doveadm [-Dv] move [-S socket_path] -u user destination [user source_user] search_query > >Moving all mails from mailbox INBOX/test on serverA to mailbox >Archive/2017 on local serverB. > + destination Archive/2017 must exist > + Limitation: source_user and testuser must share the same UID and GID > >doveadm move -S x.x.x.x:x -u testuserAtServerB > Archive/2017 user sou...

...I have a dataframe with the following attributes: rownum(1:405), colnum(1:287), year(2000:2009), daily(rownum x colnum x year) and foragePotential (0:1, by 0.01). The data is actually stored in a netcdf file and I'm trying to provide a conceptual version of the data. Ok. I need to calculate a moving mean and a moving variance for each cell on the following temporal windows - 7 day, 14 day, and 28 day. So far I have code for the moving average. ma <- function(x , n) { filter(x, rep(1/n, n), sides = 1) } # note that when the function is used, n is defined for the temporal p...