From: FX <fxcoudert@gmail.com>
To: "Kai Tietz" <Kai.Tietz@onevision.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:43:00 -0000 [thread overview]
Message-ID: <19c433eb0801090743j109ccc93l41f47056134eab99@mail.gmail.com> (raw)
In-Reply-To: <OFE6417A0A.F2B77E75-ONC12573CB.00550DDA-C12573CB.0055BA58@onevision.de>
> To have a better chance to find the issue could you anwser these question?
I'll let J. answer these himself, since I have no direct experience of
the bug myself (no Win64 machine), but...
> a) Does this happens on a cross compiler, too?
I doubt it, since he sees the bug even on trivial programs at -O1 and,
last time I tried, cross-compilers worked fairly well.
> b) Which runtime version of mingw-w64 you are using?
I've asked, but got no answer.
> I am currently on gdb support for x86_64 mingw target. But I expect, it
> will still take some time until I publish.
That's great news nonetheless!
--
FX Coudert
http://www.homepages.ucl.ac.uk/~uccafco/
next prev parent reply other threads:[~2008-01-09 15:43 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
2008-01-09 15:43 ` FX [this message]
[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=19c433eb0801090743j109ccc93l41f47056134eab99@mail.gmail.com \
--to=fxcoudert@gmail.com \
--cc=Kai.Tietz@onevision.com \
--cc=finchlady888@hotmail.com \
--cc=fortran@gcc.gnu.org \
--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).