Home > Error Cannot > Error Cannot Represent Relocation Type Bfd_reloc_rva

Error Cannot Represent Relocation Type Bfd_reloc_rva

Lu 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? OTOH fpc 1.9+ creates .ppu files for both, so you need to split up. PR rtl-optimization/49504 * gcc.target/i386/pr49504.c: New. Lu PR target/49860 * gcc.target/i386/pr47446-3.c: Renamed to ... * gcc.target/i386/pr49860-1.c: This. his comment is here

No, since Pmode is still in > > DImode and DImode addresses are *valid* addresses. I can not compile my own win32 units because of the following compilation errror: (~/FreePascal/src/fpc)-$ make clean (~/FreePascal/src/fpc)-$ make OS_TARGET=win32 all ... .... ..... Assembler is done on purpose to catch problems like this. I'm not quite understand what you're saying unfortunately :) I'm not that guru in this. http://mingw-users.1079350.n2.nabble.com/Error-using-dlltool-td2913097.html

make[4]: Entering directory `/home/leva/FreePascal/src/fpc/rtl/win32' as -o wprt0.o wprt0.as wprt0.as: Assembler messages: wprt0.as:29: Error: cannot represent relocation type BFD_RELOC_RVA wprt0.as:31: Error: cannot represent relocation type BFD_RELOC_RVA wprt0.as:32: Error: cannot represent relocation type 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 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); ... } I guess the code above This is artificial limitation.

The assembler is generating an object file which contains the BFD_RELOC_64 relocation. Previous message: [lazarus] cant find unit interfacebase Next message: [lazarus] cant find unit interfacebase Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information For this testcase, x32 should generate very similar code to ia32, except for additional 8 registers. Most annoying abuses are: 1) Top posting 2) Thread hijacking 3) HTML/MIME encoded mail 4) Improper quoting 5) Improper trimming _______________________________________________ You may change your MinGW Account Options or unsubscribe at:

I'm doing this because I must > build my projects to win32 too. Am I right? > > > You need a cross compiled as and ld with target that supports win32. It is the > same issue as [1]. > > [1] http://gcc.gnu.org/ml/gcc-patches/2011-07/msg01825.html X32 is 32bit environment. navigate here 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

But how can I compile them? -- LeVA Previous message: [lazarus] cant find unit interfacebase Next message: [lazarus] cant find unit interfacebase Messages sorted by: [ date ] [ thread ] Assembler should put correctly zero-extended symbol at the relocation site. http://p.sf.net/sfu/businessobjects_______________________________________________ MinGW-users mailing list [hidden email] This list observes the Etiquette found at http://www.mingw.org/Mailing_Lists. I have these binaries: i686-pc-mingw32-addr2line i686-pc-mingw32-dlltool i686-pc-mingw32-objcopy i686-pc-mingw32-size i686-pc-mingw32-ar i686-pc-mingw32-dllwrap i686-pc-mingw32-objdump i686-pc-mingw32-strings i686-pc-mingw32-as i686-pc-mingw32-ld i686-pc-mingw32-ranlib i686-pc-mingw32-strip i686-pc-mingw32-c++filt i686-pc-mingw32-nm i686-pc-mingw32-readelf i686-pc-mingw32-windres and all of them are symlinked to my $PATH.

  • Comment 3 Uroš Bizjak 2011-07-27 12:49:52 UTC (In reply to comment #2) > > Assembler should accept R_X86_64_64 and zero-extend it to 8 bytes.
  • It can compile my projects.
  • Cheers Nick References: Fwd: Error: cannot represent relocation type BFD_RELOC_64 From: kanishk rastogi Re: Error: cannot represent relocation type BFD_RELOC_64 From: Ramana Radhakrishnan Re: Error: cannot represent relocation type BFD_RELOC_64 From:
  • Modified: branches/x32/gcc/ChangeLog.x32 branches/x32/gcc/config/i386/i386.md branches/x32/gcc/config/i386/predicates.md Comment 13 hjl@gcc.gnu.org 2011-08-06 14:05:43 UTC Author: hjl Date: Sat Aug 6 14:05:39 2011 New Revision: 177509 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=177509 Log: Add testcases for PRs 48084/49504/49860. 2011-08-06 H.J.
  • Added: trunk/gcc/testsuite/gcc.dg/pr49860.c trunk/gcc/testsuite/gcc.target/i386/pr48084-1.c trunk/gcc/testsuite/gcc.target/i386/pr48084-2.c trunk/gcc/testsuite/gcc.target/i386/pr48084-3.c trunk/gcc/testsuite/gcc.target/i386/pr48084-4.c trunk/gcc/testsuite/gcc.target/i386/pr48084-5.c trunk/gcc/testsuite/gcc.target/i386/pr49504.c Modified: trunk/gcc/testsuite/ChangeLog Format For Printing -XML -Clone This Bug -Top of page Home | New | Browse | Search | [?] | Reports
  • Lu Modified: 2011-08-06 14:05 UTC (History) CC List: 2 users (show) rth ubizjak See Also: Host: Target: x32 Build: Known to work: Known to fail: Last reconfirmed: Attachments Add an attachment
  • In > > another word, if a memory operand is OK for ia32, it must be OK > > for x32. > > Can you prevent x32 to generate DImode symbols?
  • No, since Pmode is still in > > > DImode and DImode addresses are *valid* addresses.
  • Thank you.

For the testcase from PR, > expand generates SImode symbol that is later extended to DImode and handled > through movabs. his comment is here PS: I can execute the same commad in native Windows without errors.Thank you. ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option No, since Pmode is still in > DImode and DImode addresses are *valid* addresses. Lu 2011-07-27 16:16:54 UTC Let's punt it for now.

We ask that you be polite and do the same. http://haywirerobotics.com/error-cannot/error-cannot-open-an-http-server-socket-error-reported-errno-eacces.html And if I can use the 1.9.1, do I have to compile my own win32 units, or I can use these: ftp://gd.tuwien.ac.at/languages/pascal/fpc/snapshot/v11/win32-i386/ Are these for fpc1.9.1? Assembler should put correctly > zero-extended symbol at the relocation site. Maybe 64-bit mode is being selected inside the assembler source file.

It must handle all immediate_operands. Free forum by Nabble Edit this page Fedora Mailing-Lists Sign In Sign Up Sign In Sign Up Manage this list 2016 November October September August July June May April March February Attachments: iphlpapi.def (application/octet-stream — 43 bytes) attachment.html (text/html — 1.2 KB) +0/-0 Like / Dislike Reply Show replies by date 2733 days inactive 2733 days old [email protected] Manage subscription 2 comments 2 participants weblink Added: branches/x32/gcc/testsuite/gcc.target/i386/pr49860-1.c - copied unchanged from r176926, branches/x32/gcc/testsuite/gcc.target/i386/pr47446-3.c Removed: branches/x32/gcc/testsuite/gcc.target/i386/pr47446-3.c Modified: branches/x32/gcc/testsuite/ChangeLog.x32 Comment 11 Uroš Bizjak 2011-08-02 06:36:28 UTC Fixed in binutils [1], not a gcc bug. [1] http://sourceware.org/ml/binutils/2011-08/msg00010.html Comment 12

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); Index Nav: [DateIndex] [SubjectIndex] [AuthorIndex] [ThreadIndex] Message Nav: [DatePrev][DateNext] [ThreadPrev][ThreadNext] Other format: [Raw text] Re: Error: cannot represent relocation type BFD_RELOC_64 From: Nick Clifton To: kanishk The assembler and linker are external > applications from GNU binutils.

In another word, if a memory operand is OK for ia32, it must be OK for x32.

So the assembler must think that it is creating a 64-bit binary. Mattias > and when trying to compile to win32, it > says that: > TOutputFilter: > "/home/leva/FreePascal/lib/fpc/1.9.1/units/win32/rtl/wprt0.o: file not > recognized: File format not recognized" > > Is this beacause of You > are now trying to use win32(=pecoff) .o files with the linux linker that > only supports ELF .o files. > > Note: The compile itself can read .ppu files PR target/49860 * gcc.dg/pr49860.c: New.

No, since Pmode is still in DImode and DImode addresses are *valid* addresses. Expected output: @00000000 00 00 00 00 00 00 00 00 0F C6 00 00 00 00 00 00 0D CE 00 00 00 00 00 00 0D 8E 00 00 Most annoying abuses are: 1) Top posting 2) Thread hijacking 3) HTML/MIME encoded mail 4) Improper quoting 5) Improper trimming _______________________________________________ You may change your MinGW Account Options or unsubscribe at: http://haywirerobotics.com/error-cannot/error-cannot-represent-relocation-type-bfd-reloc-sh-imm8.html Comment 8 H.J.

Your patch just papers over this fact. By the way, what happened to the cross tool triplet prefix? ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables Hopefully in a few days. We ask that you be polite and do the same.

http://p.sf.net/sfu/businessobjects_______________________________________________ MinGW-users mailing list [hidden email] This list observes the Etiquette found at http://www.mingw.org/Mailing_Lists. This will be described in the wikis. It is the > > > same issue as [1]. > > > > > > [1] http://gcc.gnu.org/ml/gcc-patches/2011-07/msg01825.html > > > > X32 is 32bit environment. So if I compile lazarus with make clean > all, and run it, it works fine.

For your programs it means you need also some macros for the unit output dir. Lu 2011-07-27 16:14:39 UTC (In reply to comment #7) > (In reply to comment #6) > > > > > This testcase is about valid address for x86_64_immediate_operand > > > MinGW-users Search everywhere only in this topic Advanced Search Error using dlltool Classic List Threaded ♦ ♦ Locked 3 messages Fabrício Godoy Reply | Threaded Open this post in threaded view For this testcase, x32 should generate > very similar code to ia32, except for additional 8 registers.

GBiz is too! Latest News Stories: Docker 1.0Heartbleed Redux: Another Gaping Wound in Web Encryption UncoveredThe Next Circle of Hell: Unpatchable SystemsGit 2.0.0 ReleasedThe Linux Foundation Announces Core Infrastructure You are calling your native Linux "as". Take a look at the gas command line being issued by gcc when you are compiling application.c. Lu 2011-07-27 12:39:39 UTC (In reply to comment #1) > Assembler should accept R_X86_64_64 and zero-extend it to 8 bytes.

Is this the ususal > method of compiling the win32 units (make OS_TARGET=win32 all)? For the testcase from PR, expand generates SImode symbol that is later extended to DImode and handled through movabs. Most annoying abuses are: 1) Top posting 2) Thread hijacking 3) HTML/MIME encoded mail 4) Improper quoting 5) Improper trimming _______________________________________________ You may change your MinGW Account Options or unsubscribe at: