similar to: [LLVMdev] Idea of a tool to help in library versioning

On Feb 29, 2008, at 6:10 AM, Daniel Ruoso wrote: > Then I got the idea of generating an API description file from the > public header files of the library Sounds neat. In the past I've done this with objdump for the public symbols in a library. In theory you don't care about types no findable by the api. A nice tool would allow one to stamp the interface as release time,

Sex, 2008-02-29 às 13:48 -0800, Mike Stump escreveu: > On Feb 29, 2008, at 6:10 AM, Daniel Ruoso wrote: > > Then I got the idea of generating an API description file from the > > public header files of the library > Sounds neat. In the past I've done this with objdump for the public > symbols in a library. In theory you don't care about types no > findable by

Hi samba community. I'm having a problem with the smb_auth authentication method. Everything looks like normal, but everytime I try to use smb_auth it returns ERR. I will show here some commands output to secure that all configuration is correct, and if anyone can help me to investigate what's happend I'll thanks. I'm using: Debian lenny, updated. ii samba 2:3.2.3-1

On Wed, Mar 15, 2017 at 2:22 PM, Martin Richtarsky <s at martinien.de> wrote: > Here is the relevant output: > > 0000000000013832 <func()>: > 13832: 55 push %rbp > 13833: 48 89 e5 mov %rsp,%rbp > 13836: 53 push %rbx > 13837: 48 83 ec 18 sub $0x18,%rsp

Hi Martin, It's hard to tell what is wrong only with the information. If that is an open-source program, can you give me a link to that so that I can try? If that's a proprietary software you cannot share with me, you might want to produce small reproducible test case. On Thu, Mar 23, 2017 at 1:10 AM, Martin Richtarsky <s at martinien.de> wrote: > Hi Rui, > > fyi I'm

Overview ======= We are planning to open source our internal implementation of Objective-C metadata reader library to LLVM. Unlike the C style objective-c metadata reader in llvm-objdump, it is designed to be a reusable C++ library to parse objective-c metadata from binaries with LLVM style error handling. The current implementation has an interface that resembles libObject in and it supports

Hi guys I have installed Xen 4 on Debian Lenny 5.0. I have a physical Windows 2003 Server and I wanna convert this server on a virtual server... I try to use XenConvert but without sucsess... Somebody can help??? Thanks Gilberto Nunes TI Selbetti Gestão de Documentos Telefone: +55 (47) 3441-6004 Celular: +55 (47) 8861-6672 _______________________________________________ Xen-users mailing

Hello, I am looking for tool to convert file from either (.s) bytecode or (.bc) bitcode to .asm file. Basically assembly instruction file for my x86 backend. I think so we can use llvm-objdump. However I am not able to figure out its exact options. Could you please tell me how to do that? -- Thanks, Teja -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi I am executing following steps to convert assembly to object code. llc -march=x86-64 -filetype=asm input.ll -o input.s g++ -g -c -o input.s --input.o inshort ll --> llc --> .s -->g++ -->obj original source was something like this { printf(" **** %s ****",str); } input.s turn out to be movq .str at GOTPCREL(%rip),%rdi movq .str.1 at GOTPCREL(%rip),%rsi xorl

A few days ago we were discussing object files and linking on IRC. I had been thinking about working on this for a while, and this discussion finally got me to do it. Attached are patches of a preliminary implementation of a generic object file library, and a few changes to llvm-nm to make use of it. The main goal in the design of the API is to allow a fast implementation by avoiding memory

Hi Mahesh, On 23 April 2018 at 10:51, Mahesh Attarde via llvm-dev <llvm-dev at lists.llvm.org> wrote: > movq .str at GOTPCREL(%rip),%rdi > movq .str.1 at GOTPCREL(%rip),%rsi That's quite strange. You wouldn't normally expect to access a constant string via the GOT. It looks like LLVM has decided to put the symbols in an odd section, so it'd be a good idea to make sure

I've made a change to llvm-objdump and feel uncomfortable checking it in without a test case. Where do the "make check" tests for tools like llvm-objdump go? Worse comes to worse, I'll stick it in test/MC/Mips since it is there I need the change for other Mips/MC tests. Thanks, Jack -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

Compilers don't know about functions that are not defined in the same compilation unit, so they leave call instruction operands as zero (because they can't compute any absolute nor relative address of the destinations), and let linkers fix the address by binary patching. So, what you are seeing is likely a bug of LLD that it fails to fix the address for some reason. Can you dump that

On Mon, Aug 27, 2012 at 11:07 AM, Carter, Jack <jcarter at mips.com> wrote: > I've made a change to llvm-objdump and feel uncomfortable checking > it in without a test case. Where do the "make check" tests for tools like > llvm-objdump go? > > Worse comes to worse, I'll stick it in test/MC/Mips since it is there I need > the change for other Mips/MC tests.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear developers, In the course of evaluating the feasibility of performing a post-release upgrade of our Fedora LLVM stack, it was pointed out that most of the shared libraries have filenames that do not contain version tags: http://article.gmane.org/gmane.linux.redhat.fedora.devel/171315 $ repoquery --provides llvm-libs.x86_64

On 7/16/14, 6:09 PM, sgundapa wrote: > I see a couple of issues here. > > If I include .S files for ARM, the –no-integrated-as path complains about > Assembler errors. > > The integrated-as path works fine though. > These are very likely just differences between the old ARM assembler syntax and the new 'Unified' syntax. Can you use an assembler that accepts UAL

Teja, I just checked my version of llc to make sure it worked on arm and x86_64 respectively. The website llvm.org hosts a manual page for this tool at http://llvm.org/docs/CommandGuide/llc.html. I think this tool from the ample LLVM armory will accomplish what you are looking to do. All the best in your endeavors, Shaun Shaun Hubbard On Mar 7, 2013, at 10:39 PM, teja tamboli

Teja, Your mention of .s being bytecode confuses me, but if you're asking how to lower a bitcode (.bc) or IR file (.ll) to assembly (.s) than llc is the tool you are looking for. llc -O2 path/to/bitcode/input.bc -o output.s -Chris On Mar 7, 2013, at 10:39 PM, teja tamboli wrote: > Hello, > > I am looking for tool to convert file from either (.s) bytecode or (.bc) bitcode to

Sounds good, I'll work on removing these in favor of defaulting to stdin then? > I think it would be much friendlier to just print "file or pipe expected" and then print the help. Do you have thoughts on this? I'm not sure there is a clean way to do this, the cleanest would be through getFileOrSTDIN(), but I'm not sure all of its users want this behavior. I don't