search for: enderby

Oops sorry. lib/MC/MCAnalysis/MCObjectDisassembler.CPP Thanks. -eric On Jul 31, 2014 1:21 PM, "Kevin Enderby" <enderby at apple.com> wrote: > Eric, what file are your referring to? The path > lib/MC/MCObjectDisassembler does not end in a .cpp or .h and is not a > directory . > > Just a bit more info and I can get back to you if I’m using what your > asking about. > > K...

...alues in hex. AFAIK, hex is not just the default, but the only choice. On the other hand, llvm-objdump prints operand values in decimal and ignores the --print-imm-hex option for ELF. How about a patch to print operands in hex for ELF? Good place to start? On Mon, Dec 1, 2014 at 5:49 PM, Kevin Enderby <enderby at apple.com> wrote: > There currently is a -macho option to llvm-objdump to "Use MachO specific object file parser” which I’m hiding the disassembly stuff specific for Mach-O behind. Currently it is only used with the -disassemble option. But one could see it to be used fo...

...2: eb fd jmp 1 <bar> 4: eb fb jmp 1 <bar> 6: eb 01 jmp 9 <baz> 8: 90 nop 00000009 <baz>: 9: 90 nop What does otool produce? On Tue, Aug 26, 2014 at 11:16 AM, Kevin Enderby <enderby at apple.com> wrote: > For branch targets my preference is to print the target’s address (not the displacement of the branch), and preferably in hex. I like this too. > I don’t think having multiple addresses for a target is a real problem with the exception of the address 0...

...ctionality in place. Then when we’re ready to, optionally as packagers decide to opt-in, use llvm-objdump to replace the system version, we can figure out the right way to make that transition nice and clean. >> >> -jim >> >> >>> On Dec 1, 2014, at 4:40 PM, Kevin Enderby <enderby at apple.com> wrote: >>> >>> Hi Steve, >>> >>> I’ve been trying to get the functionality of llvm-objdump to match that of darwin’s otool(1). In adding the support for symbolic disassembly and to allow testing of it on very large files that would...

Hi Kent, My guess is you are getting some new bit of info in your object files and your ranlib(1) is older and doesn't know about it. If you can send me the .o file or the output of otool(1) with the -hlv options on your object file I can take a look. Kev P.S. you can find out the version of ranlib(1) you have by running strings(1) on it and grep(1)'ing for the string

On Tue, May 24, 2016 at 1:35 PM, Kevin Enderby <enderby at apple.com> wrote: > Hi Jack, > > Just a guess here, this may be the bug Chris helped me out with in the use of the include file xar/xar.h which is not C++ safe. I needed to wrap my include via: > > #ifdef HAVE_LIBXAR > extern "C" { > #include <xa...

Ran into this today -- rebuilt the SVN Trunk for this morning of LLVM+CLANG. Now every time my builds try and make a library from .o files, ranlib complains about 'malformed object' files. This is with OS X 10.7.4, and the binary tools from XCode 4.4.1 ld -v @(#)PROGRAM:ld PROJECT:ld64-127.2 llvm version 3.0svn, from Apple Clang 3.0 (build 211.12) ranlib doesn't tell you what

...fsym 2 iundefsym 17 nundefsym 0 tocoff 0 ntoc 0 modtaboff 0 nmodtab 0 extrefsymoff 0 nextrefsyms 0 indirectsymoff 0 nindirectsyms 0 extreloff 0 nextrel 0 locreloff 0 nlocrel 0 On Wed, Sep 26, 2012 at 4:31 PM, Kevin Enderby <enderby at apple.com> wrote: > Hi Kent, > > My guess is you are getting some new bit of info in your object files and your ranlib(1) is older and doesn't know about it. If you can send me the .o file or the output of otool(1) with the -hlv options on your object file I can take...

...the simpler thing, while we get the real functionality in place. Then when we’re ready to, optionally as packagers decide to opt-in, use llvm-objdump to replace the system version, we can figure out the right way to make that transition nice and clean. -jim > On Dec 1, 2014, at 4:40 PM, Kevin Enderby <enderby at apple.com> wrote: > > Hi Steve, > > I’ve been trying to get the functionality of llvm-objdump to match that of darwin’s otool(1). In adding the support for symbolic disassembly and to allow testing of it on very large files that would allow the disassembly to diff c...

Jack, What version of CMake are you using? -Chris > On May 24, 2016, at 11:00 AM, Jack Howarth <howarth.mailing.lists at gmail.com> wrote: > > On Tue, May 24, 2016 at 1:35 PM, Kevin Enderby <enderby at apple.com> wrote: >> Hi Jack, >> >> Just a guess here, this may be the bug Chris helped me out with in the use of the include file xar/xar.h which is not C++ safe. I needed to wrap my include via: >> >> #ifdef HAVE_LIBXAR >> extern "C&qu...

...linkage on libxar is required in the tools/llvm-objdump/CMakeLists.txt when HAVE_LIBXAR and LLVM_LINK_LLVM_DYLIB are set. Jack > >> On May 24, 2016, at 11:00 AM, Jack Howarth <howarth.mailing.lists at gmail.com> wrote: >> >> On Tue, May 24, 2016 at 1:35 PM, Kevin Enderby <enderby at apple.com> wrote: >>> Hi Jack, >>> >>> Just a guess here, this may be the bug Chris helped me out with in the use of the include file xar/xar.h which is not C++ safe. I needed to wrap my include via: >>> >>> #ifdef HAVE_LIBXAR >>...

...with an X100P in the UK ? I'm seeing some oddness - when I plug the wall socket into the card, I lose dialtone. If I unplug it, it comes back. Does this sound familiar to anyone ? Cheers Nigel Nigel Taylor Technology Director ITAzure Limited Dunn House Warren Park Way Enderby Leicestershire LE19 4SA 0116 286 3016 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050304/a6fffac0/attachment.htm

...Jack Howarth > <howarth.mailing.lists at gmail.com> wrote: >> On Tue, May 24, 2016 at 1:22 PM, Jack Howarth >> <howarth.mailing.lists at gmail.com> wrote: >>> On Tue, May 24, 2016 at 12:08 PM, Reid Kleckner <rnk at google.com> wrote: >>>> Kevin Enderby added those symbol uses in r270491. It has a cmake >>>> feature test, and all the uses of those symbols appear bracketed in >>>> HAVE_LIBXAR, so I don't know what went wrong for you. >>> >>> The trigger for this build failure is the usage of >>&g...

Hello Tim, Rafael, Renato and llvmdev, I’m working to get llvm-objdump handle both arm and thumb disassembly from the same object file similarly to how darwin’s otool(1) works. And I’m looking for implementing direction. I spoke to Jim Grosbach about some ideas and he suggested I send out and email about some of the possibilities. Since none of the ones I could think of are pretty he thought

...24, 2016 at 1:24 PM, Jack Howarth <howarth.mailing.lists at gmail.com> wrote: > On Tue, May 24, 2016 at 1:22 PM, Jack Howarth > <howarth.mailing.lists at gmail.com> wrote: >> On Tue, May 24, 2016 at 12:08 PM, Reid Kleckner <rnk at google.com> wrote: >>> Kevin Enderby added those symbol uses in r270491. It has a cmake >>> feature test, and all the uses of those symbols appear bracketed in >>> HAVE_LIBXAR, so I don't know what went wrong for you. >> >> The trigger for this build failure is the usage of >> -DLLVM_BUILD_EXTER...

Hello Vladimir, While this is great for platforms that use the current gas style assembler macros your patch also changes the existing support for darwin that does not use these style of assembler macros. Could you please update your patch that leaves the assembler macros unchanged for darwin. Then we can review the updated patch. Thanks, Kev On Feb 5, 2012, at 1:43 PM, Vladimir Sorokin

...ith two arguments 'a+b','c' with patch => macro test2 with three arguments 'a','+','b,c' For compability this problems requiring some compiler switch flag. Can you give me description/example how it's can be done? Thanks for response. 2012/2/9 Kevin Enderby <enderby at apple.com> > Hello Vladimir, > > While this is great for platforms that use the current gas style assembler > macros your patch also changes the existing support for darwin that does > not use these style of assembler macros. Could you please update your > patc...

Hello llvm users! I make patch of asm parser for make it to be closer to gas: 1) treat space as comma of parameters 2) support "req" & "vararg" atttributes 3) macro calls with with explicit named arguments Path attached. Can anybody review it? -------------- next part -------------- An HTML attachment was scrubbed... URL:

...attempts to resolve the symbols from libxar using an indirect linkage on libxar in libLLVM.dylib. Jack >> >>> On May 24, 2016, at 11:00 AM, Jack Howarth <howarth.mailing.lists at gmail.com> wrote: >>> >>> On Tue, May 24, 2016 at 1:35 PM, Kevin Enderby <enderby at apple.com> wrote: >>>> Hi Jack, >>>> >>>> Just a guess here, this may be the bug Chris helped me out with in the use of the include file xar/xar.h which is not C++ safe. I needed to wrap my include via: >>>> >>>> #ifdef...

With the correct list this time. On Wed, Sep 9, 2015 at 6:59 PM, Davide Italiano <davide at freebsd.org> wrote: > Hi, > in the last month I spent some time implementing the missing MachO > specific features in llvm-readobj, and converting all the remaining > tests that used macho-dump to the new format. > llvm-readobj should have all the functionality that macho-dump had. If