[PATCH] D13212: [ELF2] - Implemented -e flag

[Joerg Sonnenberger via llvm-commits]

On Mon, Sep 28, 2015 at 10:35:45AM -0700, Rui Ueyama wrote:
> On Mon, Sep 28, 2015 at 9:59 AM, Joerg Sonnenberger via llvm-commits <
> llvm-commits at lists.llvm.org> wrote:
> 
> > On Mon, Sep 28, 2015 at 01:33:16PM +0000, George Rimar via llvm-commits
> > wrote:
> > > "If there is no symbol named entry, the linker will try to parse entry
> > > as a number, and use that as the entry address (the number will be
> > > interpreted in base 10; you may use a leading 0x for base 16, or a
> > leading 0 for base 8)."
> > >
> > > But I doubt that it is a real usecase and not sure if it should be
> > implemented or not ?
> >
> > In combination with linker scripts, it can make perfect sense. Many ELF
> > kernel images are linked that way.
> >
> 
> Yes, we eventually need that. But that shouldn't be implemented in this
> patch and doesn't have to be supported now.

Well, in terms of architecture, the idea would be to keep it as string
as long as possible and only resolve it just before writing the
executable header. In that case, it is trivial to do either. It can't be
easily done in a different way either if you want to support literal
numbers.

Joerg