similar to: [LLVMdev] REX prefix is not handled properly for X86_64?

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 $ echo

On Wed, Dec 24, 2014 at 2:43 PM, Craig Topper <craig.topper at gmail.com> wrote: > I believe this particular error is caused by this. That seems easy enough > to just drop the bit. Do you have other non-mmx examples? > > case TYPE_MM: \ > if (index > 7) \ > *valid = 0;

There is a problem on X86 disassembler for instructions beginning with x86 prefix : $ echo "0x66 0x0f 0x6f 0x8f 0x00 0x00 0x00 0x00" | llvm-mc --disassemble movdqa (%edi), %xmm1 $ echo "0x53 0x66 0x0f 0x6f 0x8f 0x00 0x00 0x00 0x00" | llvm-mc --disassemble pushl %ebx <stdin>:1:6: warning: invalid instruction encoding 0x53 0x66 0x0f 0x6f 0x8f 0x00 0x00

Thanks Rex for the updates to kde - especially the kdewebdev since that 'save' bug was especially annoying. Craig

Full_Name: Andrew Thornton Version: Webpage OS: Linux Submission from: (NULL) (81.154.9.63) The Writing R Extensions documentation at: http://cran.r-project.org/doc/manuals/R-exts.html lists two different filenames for making the example's Rout.save a test result. Section 1.1.3 says: "If tests has a subdirectory Examples containing a file pkg-Ex.Rout.save, this is compared to the

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

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

I added 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

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

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

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

Hi, I am having a really strange problem with my Samba shares on Debian Buster. None of the users can access any shares, which reside on ZFS-filesystem. Any other share works just fine. For example, if I create a normal folder to /home with same permissions and replace a ZFS-share with that, it works fine. When accessing any ZFS-shares the following error is recorded: Jan 08 22:39:56

I am attempting to create an instruction which takes a single 64-bit immediate. This doesn't seem like a thing that would exist already (because who needs an instruction which just takes an immediate?) How might I implement this easily? Perhaps I could use a format which encodes a register, which is then unused? Thanks for the help. Gus -------------- next part -------------- An HTML

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

I would like to draw a set of points that are equally spaced in a 2-D grid. Then I would like to draw lines that illustrate different directed paths through subsets of points. Imagine that the points correspond to booths in a conference center, and I want to show the various paths people took to visit the booths (using color to highlight different types of paths). An example path might be: [(1,1),

Create an object hierarchy to represent different bootloaders for Linux guests, moving the separate handling of grub1 and grub2 in different classes: this isolates the code for each type of bootloader together, instead of scattering it all around. This is mostly code refactoring, with no actual behaviour change. --- po/POTFILES-ml | 1 + v2v/Makefile.am | 2 + v2v/bootloaders.ml

Tracking down a problem with one of our benchmark codes, we've discovered that some of the patterns in X86InstrX86-64.td are wrong. Specifically: def MOV64toPQIrm : RPDI<0x6E, MRMSrcMem, (outs VR128:$dst), (ins i64mem:$src), "mov{d|q}\t{$src, $dst|$dst, $src}", [(set VR128:$dst, (v2i64 (scalar_to_vector

This series fixes and enhances parsing of the OVA manifest file. The changes are: - Added mandatory space to the regexp - Process all lines in the file, not just one - Warn on improperly formated lines - Support SHA256 hashes v1 -> v2: rebased on to master to make use of the Checksums module Tomáš Golembiovský (2): v2v: ova: fix checking of the manifest file v2v: ova: support SHA256

When I use barchart (with default formatting options), I get bars whose lengths/heights are not proportional to their value. For example: http://drop.io/wbagm6s/asset/capture-png Many of the values 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

Hello, I''m learning Rails right now, and as my first project I am trying to create a fun little useful website. However, I''m getting stuck on one of the steps, and was wondering what the easiest approach would be. What I''m specifically looking to do is to create "dynamic" forms, where the number of fields can be increased and decreased by the user.