From: Kai Tietz <Kai.Tietz@onevision.com>
To: FX <fxcoudert@gmail.com>
Cc: "J. Finch" <finchlady888@hotmail.com>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
"GCC Development" <gcc@gcc.gnu.org>,
mingw-w64-public@lists.sourceforge.net
Subject: Re: internal compiler error: Segmentation fault
Date: Wed, 09 Jan 2008 15:37:00 -0000 [thread overview]
Message-ID: <OFE6417A0A.F2B77E75-ONC12573CB.00550DDA-C12573CB.0055BA58@onevision.de> (raw)
In-Reply-To: <19c433eb0801090709j4e1e09a6v4534562c22b38cb8@mail.gmail.com>
> [for mingw-w64-public@... and gcc@... readers, seeshort thread
> starting at http://gcc.gnu.org/ml/fortran/2008-01/msg00103.html]
>
> > Gcc gets the similar problem. It only works without optimization.
> It seems not a problem with gfortran.
>
> OK, then it'd be more appropriate to ask the mingw mailing-list or the
> generic gcc@gcc.gnu.org list.
>
> > GMP version is 4.2.2, and has been modified for x86_64. The
> original 4.2.2 does not support x86_64-pc-mingw32.
>
> Does GMP pass tests? Have you built it with extra checking enabled? I
> don't suspect what you're seeing is a GMP problem, but you can never
> be too sure.
To have a better chance to find the issue could you anwser these question?
a) Does this happens on a cross compiler, too? You can get on via the
mingw-w64 pages on sourceforge.
b) Which runtime version of mingw-w64 you are using?
c) How did you compile gmp? As reference may take a look at
http://terpstra.ca/lurker/message/20071208.235835.12a77213.en.html
This is a patch for gmp seems to work with mingw-w64 runtime as author
tells.
> > I do not have gdb for windows for the time being.
>
> That's why I gave you a download link for MS debuggers (I don't think
> gdb is supported on x86_64-mingw32). I'm not sure much can be done
> without a debugger.
I am currently on gdb support for x86_64 mingw target. But I expect, it
will still take some time until I publish.
Cheers,
i.A. Kai Tietz
| (\_/) This is Bunny. Copy and paste Bunny
| (='.'=) into your signature to help him gain
| (")_(") world domination.
------------------------------------------------------------------------------------------
OneVision Software Entwicklungs GmbH & Co. KG
Dr.-Leo-Ritter-Straße 9 - 93049 Regensburg
Tel: +49.(0)941.78004.0 - Fax: +49.(0)941.78004.489 - www.OneVision.com
Commerzbank Regensburg - BLZ 750 400 62 - Konto 6011050
Handelsregister: HRA 6744, Amtsgericht Regensburg
Komplementärin: OneVision Software Entwicklungs Verwaltungs GmbH
Dr.-Leo-Ritter-Straße 9 – 93049 Regensburg
Handelsregister: HRB 8932, Amtsgericht Regensburg - Geschäftsführer:
Ulrike Döhler, Manuela Kluger
next prev parent reply other threads:[~2008-01-09 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19c433eb0801090519l676a7645u162dc18760e99cc9@mail.gmail.com>
[not found] ` <BAY127-W419B706D2D2ACAC13608CE8D490@phx.gbl>
2008-01-09 15:09 ` FX
2008-01-09 15:37 ` Kai Tietz [this message]
2008-01-09 15:43 ` FX
[not found] <BAY127-W3905CADAD6C9E6370134AD8D4A0@phx.gbl>
2008-01-10 14:36 ` Kai Tietz
2008-01-10 15:18 ` J. Finch
2008-01-10 15:32 ` J. Finch
2008-01-10 16:06 ` Kai Tietz
2008-01-10 18:38 ` J. Finch
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=OFE6417A0A.F2B77E75-ONC12573CB.00550DDA-C12573CB.0055BA58@onevision.de \
--to=kai.tietz@onevision.com \
--cc=finchlady888@hotmail.com \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=mingw-w64-public@lists.sourceforge.net \
/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).