similar to: [LLVMdev] X86 disassembler 0x66 prefix

Hello, I have seen this bug for quite a while, and even in the latest code it is still there: that is X86 disassembler does not handle 0x66 prefix properly, if it is put behind 0xF3 prefix. The below commands should return the same output, but not. $ echo "0xf3 0x66 0xa5"|./build/bin/llvm-mc --disassemble -triple=x86_64 -output-asm-variant=1 .text rep movsw word ptr es:[rdi], word ptr

I have a question about a movie I 've encoded with libtheora. It's a video 2000x2000 with Theora codec and no audio. The video is fine with some players, but it isn't read in youtube. http://www.ibiiztera.be/others/test3.ogv -------------- next part -------------- An HTML attachment was scrubbed... URL:

Dear all, I cannot find the answer of this question. We all know LLVM IR is portable, but it uses ILP32 and record the target layout within the IR. target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64 :64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64" target triple = "x86_64-linux-gnu" It seems it already assigned

Hello everyone, I have noticed thar our dahdi-channels.conf has some repeating directives, for instance for channel 2 (FXO) we have these settings: ;;; line="2 WCTDM/0/1 FXSKS" signalling=fxs_ks callerid=asreceived group=0 context=from-pstn channel => 2 callerid= group= context=default As you can see, a few directives are repeated (callerid, group, context). This was generated by

Hi, Any recent experience to share when using OpenStage phones in SIP mode and Asterisk ? What about provisionning (and localization) ? BLF ? Audio quality ? User acceptance ? Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20101222/79c2b6bc/attachment.htm>

Hi, In file X86DisassemblerDecoder.c, we have function readPrefixes() with below code: ..... } else if (insn->mode == MODE_32BIT) { insn->registerSize = (hasOpSize ? 2 : 4); insn->addressSize = (hasAdSize ? 2 : 4); insn->displacementSize = (hasAdSize ? 2 : 4); insn->immediateSize = (hasOpSize ? 2 : 4); } .... This is confused to me: so we

I became suspicious that I should have received a certain message, and reading pm.log I discovered that it had indeed arrived and had been allocated to /var/mail/anne, despite procmailrc telling it that MAILDIR=/home/anne/Maildir/ Any idea what might have caused this? It seems to have been working like this only in the last 24 hours or so. Anne -- KDE Community Working Group New to KDE

Hi All, Just a little over thought. Sorry if someone already asked about this before. Is it possible to put all 16 Ports of E1 in One Asterisk Server ? And if it's not possible is there any suggestion or alternative for me to use more than 320 lines of outgoing calls on One Asterisk Server ? Thanks ZH -------------- next part -------------- An HTML attachment was

I looked at this briefly, I think it causes some mistakes that get reversed later in fixupReg. The disassembler design is a bit of a mess with regards to prefixes and operand size. On Tue, Apr 1, 2014 at 4:43 PM, Jun Koi <junkoi2004 at gmail.com> wrote: > > > > On Mon, Mar 31, 2014 at 11:48 PM, Jun Koi <junkoi2004 at gmail.com> wrote: > >> Hi, >> >>

Ok I can't get my CDR values to set from the h extension in either 1.6.2 or 1.8 What is wrong? Here is what I found in the cdr.conf ; Normally, CDR's are not closed out until after all extensions are finished ; executing. By enabling this option, the CDR will be ended before executing ; the "h" extension so that CDR values such as "end" and "billsec" may

there is an if-else code in X86DisassemblerDecoder.c that does exactly the same thing on both paths. so this patch removes the redundant path. thanks, Jun diff --git a/lib/Target/X86/Disassembler/X86DisassemblerDecoder.c b/lib/Target/X86/Disassembler/X86DisassemblerDecoder.c index 20e61da..3932ea1 100644 --- a/lib/Target/X86/Disassembler/X86DisassemblerDecoder.c +++

Hello, I'm looking for a disassembler to examine a malicious Win32 binary on FreeBSD. Does anybody have any favourites? I see pedisassem in ports, but it looks to be broken and unmaintained (it crashes with a floating point error, currently). MC

According to http://www.winehq.com/site/docs/winedev-guide/wine-debugger "It seems that Windows Disassembler 32 currently has problems working correctly under Wine, so use IDA or GoVest." I tried it anyway, and it looked ok while it was disassembling my program. But then, when it finished disassembling, the window was made really tiny, and when I made the window regular-sized, the font

Hi, I have been trying to use LLVM as a disassembler, thus providing a small part of my decompiler that I am working on. It currently decompiles from X86_64 binary.o -> LLVM IR. It works with a small set of test programs so far, so cannot currently handle large binary programs yet. The problem is with the LLVM "getInstruction()" method. It used to have a PC (program counter)

Hi All, I would like to have more details about this LLVM wished feature (taken from http://llvm.org/OpenProjects.html#misc_new): "Write a disassembler for machine code that would use TableGen to output MachineInstrs for transformations, optimizations, etc." The phrase refers to _native_ machine code? Any extra detail about this feature will be really appreciated, since I'm

Hi there. I've looking libcpu project and some history of the mailing list and got a question: what is the status of the disassembler? I mean, is there someone working on it, what targets does it support and so on. I mean, it would be interesting to be able to "undo" the operations LLVM does, like machine code->LLVM IR. If there's no one working with this right now, I'd

Other than the x86 disassembler effort, is there an ARM disassembler effort going on? It seems that there have been commits for weeks with messages like "add so-and-so instruction to ARM.td for disassembly purposes only"... -- Thanks, Shih-wei -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello I think I found a bug in the x86 instruction definition file, while trying out the disassembler. It looks like the "ADD32rr_alt" instruction should have GR32 operands, not GR16. Attached you can find a patch, which should fix the problem. But even with the change I can not decode e.g. "0x03 0xC1" (should be "addl %ecx, %eax") only if I remove the

I'm wondering if anyone is working on a machine code -> LLVM bitcode disassembler? Obviously, there won't be a one-to-one correspondence but it seems like you should be able to get close. There's always inline asm for the remaining fragments. So is there such a thing? Thank you, Bob

Hi there! In the x86 disassembler I noticed an if-statement with a duplicated branch. Are these intended to be identical? Best regards, Nicolas Kaiser -- diff -ur llvm-2.8.orig/lib/Target/X86/Disassembler/X86DisassemblerDecoder.c llvm-2.8/lib/Target/X86/Disassembler/X86DisassemblerDecoder.c --- llvm-2.8.orig/lib/Target/X86/Disassembler/X86DisassemblerDecoder.c 2010-05-06 22:59:00.000000000 +0200