Displaying 3 results from an estimated 3 matches for "machoformat".
2013 Jul 05
0
[LLVMdev] Hi, people, I propose to move Debug and Object File related headers out of Support
...tioned this - I think the point of having
ELF.h and friends in Support is that they’re intended to (more or less
exactly) match the headers provided by the system. Most of what’s there is
duplicated in a friendlier form (for ObjectFile-related stuff), or just to
match the LLVM style (notably Object/MachOFormat.h) in Object.
-- Ahmed Bougacha
> Chip
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
-------------- next part -------...
2013 Jul 05
2
[LLVMdev] Hi, people, I propose to move Debug and Object File related headers out of Support
On Jul 4, 2013, at 10:22 PM, 罗勇刚(Yonggang Luo) wrote:
>
> 在 2013-7-4 下午8:53，"Charles Davis" <cdavis5x at gmail.com>写道：
> >
> >
> > On Jul 4, 2013, at 1:43 AM, 罗勇刚(Yonggang Luo) wrote:
> >
> > > LLVM is a modularized software system, so I hope it's was modularized,
> > > And ELF.h is definitely belongs to Object by
2012 Jan 04
0
[LLVMdev] exposing container-specific features in the Object library
Hello,
The ObjectFile class (in Object/ObjectFile.h) presents a format-independent interface for object files. In addition, for COFF and MachO, some internal format details are exposed in special headers. For example, Object/COFF.h exposes coff_file_header and coff_symbol. Object/MachOFormat.h exposes headers, "segment load commands" and so on.
ELF, however, is not exposed and completely hidden behind the ObjectFile.h interface.
My questions is - what is the reasoning behind this design, which apparently takes 2 different approaches. Is the intention to eventually have everyt...