This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/49860] [x32] Error: cannot represent relocation type BFD_RELOC_64 in x32 mode
- From: "ubizjak at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 27 Jul 2011 16:04:49 +0000
- Subject: [Bug target/49860] [x32] Error: cannot represent relocation type BFD_RELOC_64 in x32 mode
- Auto-submitted: auto-generated
- References: <bug-49860-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49860
--- Comment #7 from Uros Bizjak <ubizjak at gmail dot com> 2011-07-27 16:04:47 UTC ---
(In reply to comment #6)
> > > This testcase is about valid address for x86_64_immediate_operand
> > > and x86_64_zext_immediate_operand. If it is valid for TARGET_32BIT,
> > > it should be valid for TARGET_X32.
> >
> > (define_predicate "x86_64_immediate_operand"
> > (match_code "const_int,symbol_ref,label_ref,const")
> > {
> > if (!TARGET_64BIT)
> > return immediate_operand (op, mode);
> > ...
>
> X32 != LP64.
i686 = TARGET_32BIT
x32 = TARGET_64BIT
x86_64 = TARGET_64BIT
> > This is artificial limitation.
>
> Those generated codes aren't very efficient for x32. There is
> a problem somewhere.
It is *movdi_internal_rex64. But you can't change it. It must handle all
immediate_operands.