search for: rex

Hi, I get * excluding invalid files from 'R.oo' Subdirectory 'R' contains invalid file names: attachLocally.Object.Rex Exception.Rex extend.default.Rex InternalErrorException.reportBug.Rex Package.Rex Person.Rex Rdoc.Rex setMethodS3.Rex StaticFields.Rex when running R CMD build in R v2.3.0 devel. I do understand what is going on. In my *.R files I keep so called Rdoc comments which in their simplest form are...

...it works fine. When accessing any ZFS-shares the following error is recorded: Jan 08 22:39:56 punishedkorppu smbd[27893]: [2018/01/08 22:39:56.075343, 0] ../source3/smbd/service.c:774(make_connection_snum) Jan 08 22:39:56 punishedkorppu smbd[27893]: canonicalize_connect_path failed for service rex, path /tank/rex The system in use is Debian Buster with Samba 2:4.7.3+dfsg-1 and ZoL 0.7.4-1 from Debian repo. Selinux is disabled and apparmor too. Any ideas what might be wrong with this setup? --- information --- The mountpoint really is /tank/rex according to zfs list. It can also be acces...

...\ > if (index > 7) \ > *valid = 0; \ > return prefix##_MM0 + index; > yes, exactly this place. but the question is: how do we know when to drop the REX.B? i dont know any non-MMX examples. it seems only MMX related instructions have this issue. thanks, Jun > > On Tue, Dec 23, 2014 at 10:17 PM, Jun Koi <junkoi2004 at gmail.com> wrote: >> >> hi, >> >> i think the current X86 disassembler is quite broken and...

Hi, Intel's Xed can interpret "43 40 04 75" as "add al, 0x75", but LLVM's X86 disassembler considers this invalid code. I guess the reason is that LLVM fails to recognize the REX prefix in this case. Is this correct? Thanks. Jun -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141211/dc1a23fe/attachment.html>

...one testshare /home/testijako and connected to it with the same credentials as I would connect to ZFS-shares. Then I did the strace to that particular PID and tried connecting to one ZFS-share. There was indeed an error which might have something to do with this issue: Line 2001: lstat("/tank/rex", 0x7fff1f6fb2c0) = -1 ENOENT (No such file or directory) Im sure that folder exists (files have been omitted): aurinko at punishedkorppu:~$ cd /tank/rex aurinko at punishedkorppu:/tank/rex$ ls -hal total 32M drwxrwxrwx 12 rex rex 20 Dec 24 19:09 . Full stracefile can be fo...

Hello, I tried lunch something but the anwer was "can't find apps" (I used absolute path too) [serge@rex wineserver-rex]$ wine /windows/ProgramFiles/Office/winword.exe Invoking /opt/wine/bin/wine.bin /windows/ProgramFiles/Office/winword.exe ... Wine failed with return code 2 /usr/bin/wine: line 516: 1046 Compl?t? tail -f $log_name Deleting /tmp/wine.log.Vv4t6C [serge@rex wineserver-re...

hi, i think the current X86 disassembler is quite broken and fails badly on handling REX for x86_64 code. below are some examples: $ echo "0x0f,0xeb,0xc3"|./Release+Asserts/bin/llvm-mc -disassemble -triple=x86_64 .text por %mm3, %mm0 $ echo "0x40,0x0f,0xeb,0xc3"|./Release+Asserts/bin/llvm-mc -disassemble -triple=x86_64 .text por %mm3, %mm0...

Greetings, The following question has come up in an off-list discussion. Is it possible to construct a regular expression 'rex' out of two given regular expressions 'rex1' and 'rex2', such that a character string X matches 'rex' if and only if X matches 'rex1' AND X does not match 'rex2'? The desired end result can be achieved by logically combining the results of a grep using &...

v1 was here: https://www.redhat.com/archives/libguestfs/2017-September/msg00135.html This is a more complete evolution of the earlier patch. It replaces most important uses of Str with PCRE throughout the code. It also extends the bindings with some useful features like case-insensitive regexps. The main places I *didn't* touch are the generator (GObject uses Str extensively); and

v1: https://www.redhat.com/archives/libguestfs/2017-September/msg00135.html v2: https://www.redhat.com/archives/libguestfs/2017-September/msg00158.html v3 is almost identical to v2, but I have added 4 extra commits to almost finish the job of replacing Str everywhere possible (note it's not possible to replace Str in common/mlstdutils or the generator because those are pure OCaml). As

...: unit -> unit + method virtual remove_console : unit -> unit + method update () = () +end + +(* Helper type used in detect_bootloader. *) +type bootloader_type = + | Grub1 + | Grub2 + +(* Helper function for SUSE: remove (hdX,X) prefix from a path. *) +let remove_hd_prefix path = + let rex = Str.regexp "^(hd.*)\\(.*\\)" in + Str.replace_first rex "\\1" path + +(* Grub1 (AKA grub-legacy) representation. *) +class bootloader_grub1 (g : G.guestfs) inspect grub_config = + (* Grub prefix? Usually "/boot". *) + let grub_prefix = + let mounts = g#inspect...

...: unit -> unit + method virtual remove_console : unit -> unit + method update () = () +end + +(* Helper type used in detect_bootloader. *) +type bootloader_type = + | Grub1 + | Grub2 + +(* Helper function for SUSE: remove (hdX,X) prefix from a path. *) +let remove_hd_prefix path = + let rex = Str.regexp "^(hd.*)\\(.*\\)" in + Str.replace_first rex "\\1" path + +(* Grub1 (AKA grub-legacy) representation. *) +class bootloader_grub1 g inspect grub_config = + let prefix = + let mounts = g#inspect_get_mountpoints inspect.i_root in + try + List.find ( +...

...e is nothing omitted from the current implementation. Rich. > +(* Helper type used in detect_bootloader. *) > +type bootloader_type = > + | Grub1 > + | Grub2 > + > +(* Helper function for SUSE: remove (hdX,X) prefix from a path. *) > +let remove_hd_prefix path = > + let rex = Str.regexp "^(hd.*)\\(.*\\)" in > + Str.replace_first rex "\\1" path > + > +(* Grub1 (AKA grub-legacy) representation. *) > +class bootloader_grub1 (g : G.guestfs) inspect grub_config = > + (* Grub prefix? Usually "/boot". *) > + let grub_prefix...

...vision 49716) > +++ lib/Target/X86/X86CodeEmitter.cpp (working copy) > @@ -92,8 +92,6 @@ > intptr_t PCAdj = 0); > > unsigned getX86RegNum(unsigned RegNo) const; > - bool isX86_64ExtendedReg(const MachineOperand &MO); > - unsigned determineREX(const MachineInstr &MI); > > bool gvNeedsLazyPtr(const GlobalValue *GV); > }; > @@ -405,139 +403,6 @@ > } > } > > -static unsigned sizeOfImm(const TargetInstrDesc *Desc) { > - switch (Desc->TSFlags & X86II::ImmMask) { > - case X86II::Imm8: return...

...@@ -276,88 +240,7 @@ let rec convert ~keep_serial_console (g : G.guestfs) inspect source rcaps = * list is the default booting kernel. *) let grub_kernels : kernel_info list = - (* Helper function for SUSE: remove (hdX,X) prefix from a path. *) - let remove_hd_prefix = - let rex = Str.regexp "^(hd.*)\\(.*\\)" in - Str.replace_first rex "\\1" - in - - let vmlinuzes = - match grub with - | `Grub1 -> - let paths = - let expr = sprintf "/files%s/title/kernel" grub_config in - let paths = g#aug_match...

OK, here's a new patch that adds the infrastructure and the implementation for X86, ARM and PPC of GetInstSize and GetFunctionSize. Both functions are virtual functions defined in TargetInstrInfo.h. For X86, I moved some commodity functions from X86CodeEmitter to X86InstrInfo. What do you think? Nicolas Evan Cheng wrote: > > I think both of these belong to TargetInstrInfo. And

...[(store (i64 (vector_extract (v2i64 VR128:$src), (iPTR 0))), addr:$dst)]>; These say that for an AT&T-style assembler, output movd and for an Intel assembler, output movq. The problem is that such movs to and from memory must either use movq or put a rex prefix before the movd. No such rex prefix appears in these patterns, meaning the instructions will move 32 bits rather than 64 bits. Bad things happen. A little sleuthing uncovered this: $ svn log -r32609 ~/svn/test/official.llvm/llvm/lib/Target/X86/X86InstrX86-64.td ------------------------...

...> (iPTR 0))), addr:$dst)]>; > > These say that for an AT&T-style assembler, output movd and for an > Intel > assembler, output movq. Right. > > The problem is that such movs to and from memory must either use movq > or put a rex prefix before the movd. No such rex prefix appears in > these > patterns, meaning the instructions will move 32 bits rather than 64 > bits. You mean there should be a "rex" in the assembly string? That is, rex movd %rax, %xmm0 The Mac OS X assembly does not take rex prefi...

...hlight different types of paths). An example path might be: [(1,1), (1,3), (3, 3)]. Note: I would like to also make the size of the points in the grid variable (they correspond to the sizes of the booth). Can anyone suggest a way to do this in R? (Or to suggest another software package.) Thanks, Rex

...lues in this chart are 1; however, because the blue bars extend to the left of the "0" tick mark, those bars appear to represent higher numeric values. Is there a way to make the length of the bar proportional to the data value, so that people looking at my chart are not misled? Thanks, Rex [[alternative HTML version deleted]]