This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [x86]: Allow @GOTOFF in non-memory context?
- From: Uros Bizjak <ubizjak at gmail dot com>
- To: GCC Development <gcc at gcc dot gnu dot org>
- Cc: Jakub Jelinek <jakub at redhat dot com>, "H.J. Lu" <hjl dot tools at gmail dot com>, Rainer Orth <ro at cebitec dot uni-bielefeld dot de>, IainS <developer at sandoe-acoustics dot co dot uk>
- Date: Thu, 03 Jun 2010 21:40:52 +0200
- Subject: Re: [x86]: Allow @GOTOFF in non-memory context?
- References: <AANLkTinjwofdJ1RIH1YsvpAUsTYbY7mOnxmqrooxDGCO@mail.gmail.com>
On Thu, 2010-06-03 at 14:24 +0200, Uros Bizjak wrote:
> I'm looking into i386.md, where we have a bunch of instances of
> following comment:
>
> ; Current assemblers are broken and do not allow @GOTOFF in
> ; ought but a memory context.
>
> Code, following this comment disables or special-cases "pic_symbolic_operands".
>
> I'm investigating, which "current assemblers" are broken, since my
> assembler from binutils-2.20 happily assembles:
>
> addl x@GOTOFF(%ebx), %eax
>
> in 32bit mode, as well as
>
> addq x@GOTPCREL(%rip), %rax
>
> in 64bit mode.
>
> Looking into gcc install documentation, the lowest mentioned version
> is 2.13.1. I have no idea, if this version supports above asm, so I
> would like to ask someone with access to this ancient version if he
> can test this instruction.
FYI, binutils-2.13.1 (that doesn't even build out-of-the-box nowadays
without a couple of trivial fixes) assembles above instructions without
problems, so IMO - as far as ELF is concerned - we can remove this
limitation.
Uros.