public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wyldckat+gcc.bugzilla at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52790] New: Problems using x86_64-w64-mingw-w32-gfortran with mcmodel=large and medium
Date: Fri, 30 Mar 2012 15:10:00 -0000	[thread overview]
Message-ID: <bug-52790-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 52790
           Summary: Problems using x86_64-w64-mingw-w32-gfortran with
                    mcmodel=large and medium
    Classification: Unclassified
           Product: gcc
           Version: 4.6.3
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: wyldckat+gcc.bugzilla@gmail.com


Created attachment 27043
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27043
Example that works on Linux x86_64 but not with mingw-w64 on/for Windows

Attached is "test.f", an example file of Fortran code that will build just fine
on Linux x86_64, but it will not build with "x86_64-w64-mingw32-gfortran.exe"
on Windows or with a cross-compilation "build kit" on Linux.

Commands for building this test file:
- on several Linux x86_64 boxes with various gcc versions, all of these work:
 1.   gfortran -O3 test.f
 2.   gfortran -O3 -mcmodel=medium test.f
 3.   gfortran -O3 -mcmodel=large test.f
the last one is what I have to use with the real code, due to the number and
dimensions of the pre-allocated arrays.


- on Windows or cross-compiled from Linux, all of these don't work:
 1.   x86_64-w64-mingw32-gfortran.exe -O3 test.f
 2.   x86_64-w64-mingw32-gfortran.exe -O3 -mcmodel=medium test.f
 3.   x86_64-w64-mingw32-gfortran.exe -O3 -mcmodel=large test.f

The errors vary depending on option. In order, the summary "complaints" are:
 1.   In function `pre_c_init' [...] crtexe.c [...] relocation truncated to
fit: R_X86_64_PC32 against symbol ...

 2.   as.exe: BFD (GNU Binutils) 2.22.51.20111217 assertion fail [...]
coff-x86_64.c [...] cannot represent relocation type BFD_RELOC_386_GOTPC

 3.   as.exe [...] cannot represent relocation type BFD_RELOC_X86_64_GOTPC64


Tested build systems:
- custom build: binutils 2.21 + gcc 4.5.3 (gmp 4.3.2 + mpfr 2.4.2 + mpc 0.8.2)
+ mingw-w64 CRT v1.x
- custom build: binutils 2.22 + gcc 4.6.3 (gmp 5.0.2 + mpfr 3.0.1 + mpc 0.9) +
mingw-w64 CRT v2.x
- automatic build from the mingw-w64 project (Gcc 4.7.0 and binutils
2.22.51.20111217), namely with the package:
mingw-w64-bin_i686-mingw_20111220.zip



This was initially reported on the mingw-w64 project bug tracker:
http://sourceforge.net/tracker/?func=detail&atid=983354&aid=3505342&group_id=202880
The answer was and I quote:
  «This bug report is invalid on this list. You can open a feature-request on
gcc's bugtracker for it, but x64 windows target is using small-memory model
only. larget memory-model isn't supported at all, and medium is at least
absolutely untested.
  Therefore I close this bug as invalid, as it has nothing to do with mingw-w64
itself.»


             reply	other threads:[~2012-03-30 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30 15:10 wyldckat+gcc.bugzilla at gmail dot com [this message]
2012-04-19  9:00 ` [Bug target/52790] " jb at gcc dot gnu.org
2013-04-03  8:07 ` ktietz at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-52790-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).