This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/49860] [x32] Error: cannot represent relocation type BFD_RELOC_64 in x32 mode


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49860

--- Comment #6 from H.J. Lu <hjl.tools at gmail dot com> 2011-07-27 15:42:37 UTC ---
(In reply to comment #5)
> (In reply to comment #4)
> 
> > > Can you prevent x32 to generate DImode symbols? No, since Pmode is still in
> > > DImode and DImode addresses are *valid* addresses. For the testcase from PR,
> > > expand generates SImode symbol that is later extended to DImode and handled
> > > through movabs.
> > 
> > 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.

> 
> I guess the code above speaks for itself.
> 
> > Assembler is done on purpose to catch problems like this.
> 
> This is artificial limitation.

Those generated codes aren't very efficient for x32. There is
a problem somewhere.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]