[LLVMdev] ELFObjectFile changes, llvm-objdump showing 'wrong' values?

[Bendersky, Eli]

Hi Will,

I've committed the recent change to ELFObjectFile (r148653). It was supposed to add new functionality, not break existing one. I'll take a look at this and will keep you updated.

Eli

> -----Original Message-----
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
> On Behalf Of Will Dietz
> Sent: Monday, January 23, 2012 07:32
> To: llvmdev at cs.uiuc.edu
> Subject: [LLVMdev] ELFObjectFile changes, llvm-objdump showing 'wrong'
> values?
> 
> Hi all,
> 
> I'm using the MC framework for a project, and while updating to latest trunk
> (r148672) encountered the following issue:
> 
> It seems that SymbolRef::getAddress and SymbolRef::getFileOffset have
> been changed to add the symbol's offset to the offset of the containing
> section?
> 
> This has the following implications:
> 
> To get the /actual/ fileoffset, I now need to do:
> Symbol.getFileOffset() - ContainingSection.getFileOffset() And to get the
> address relative to the section, I do:
> Symbol.getFileOffset() - 2*ContainingSection.getFileOffset()
> 
> I suspect this isn't the desired functionality (what use is the original value?)?
> 
> You can also see the impact of this on the tool llvm-objdump (as well as llvm-
> nm), as shown below:
> 
> Normal objdump: http://pastebin.com/Fsv3Vvye vs llvm-objdump:
> http://pastebin.com/MRryQe4D
> 
> I believe r148653 caused this, but haven't verified directly.  This didn't happen
> as of r148100.
> 
> Am I missing something (my code borrows a good deal from llvm-objdump
> and llvm-nm, so if they are doing something wrong with respect to these
> new changes, so am I), or is this something that should be fixed?
> 
> Thanks for your time!
> 
> ~Will
> 
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.