public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Tim Prince <tprince818.tp@gmail.com>
Cc: Steve Kargl <sgk@troutmask.apl.washington.edu>,
		"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	FX <fxcoudert@gmail.com>,
	ktietz70@googlemail.com
Subject: Re: Fwd: Windows support dropped from gcc trunk
Date: Sun, 18 Oct 2015 07:30:00 -0000	[thread overview]
Message-ID: <CAGkQGiKpALMVfaisf-oLF_9uNC4yYhywQVTpS_Hk-J1W7RmryQ@mail.gmail.com> (raw)
In-Reply-To: <562164AB.5080306@gmail.com>

Dear Tim,

Thanks from all of us for taking this on. It is clear from clf that a
lot of people out there are using gfortran under windows and that the
poor support is not doing much for the reputation of gfortran.

Cheers

Paul

On 16 October 2015 at 22:57, Tim Prince <tprince818.tp@gmail.com> wrote:
>
>
> On 10/14/2015 1:08 PM, Steve Kargl wrote:
>> On Wed, Oct 14, 2015 at 11:48:27AM -0400, Tim Prince wrote:
>>>> I added gcc@gcc.gnu.org as this technically isn't a Fortran issue.
>>> test suite reports hundred of new ICE instances, all referring to this
>>> seh_unwind_emit function:
>>>
>>> /cygdrive/c/users/tim/tim/tim/src/gnu/gcc1/gcc/testsuite/gcc.c-torture/compile/20000127-1.c:
>>> In function 'foo':^M
>>> /cygdrive/c/users/tim/tim/tim/src/gnu/gcc1/gcc/testsuite/gcc.c-torture/compile/20000127-1.c:7:1:
>>> internal compiler error: in i386_pe_seh_unwind_emit, at
>>> config/i386/winnt.c:1137^M
>> I think you'll need to file a bug report.  It probably
>> should be labeled as target specific and give a major
>> status.
>>
> The fixes checked in by Uros appear to have taken care of the C
> problem.  I am just finishing up a build of libgfortran using the new
> compiler, after editing the .h files to permit building in spite of the
> lack of support for either real(10) or real(16).  It still looks
> intentional that someone changed libgfortran so that it won't build
> automatically for this case.  configure still finds correct results on
> which math functions are supported in each data type.  There is a
> sqrtl() but not much more (and that will be the same as sqrt as Windows
> X64 sets 53-bit precision mode).
> Assuming I get a satisfactory gfortran testsuite, I'll post it.  gcc and
> g++ testsuites appeared to be back in the ballpark.
> Testsuite always produced failure of all rounding tests because of the
> lack of support for real(10) and real(16).



-- 
Outside of a dog, a book is a man's best friend. Inside of a dog it's
too dark to read.

Groucho Marx

  reply	other threads:[~2015-10-18  7:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 14:33 Tim Prince
2015-10-14 15:33 ` Fwd: " Tim Prince
2015-10-14 15:36   ` Steve Kargl
2015-10-14 15:48     ` Tim Prince
2015-10-14 17:08       ` Steve Kargl
2015-10-14 17:29         ` Tim Prince
2015-10-14 18:06           ` Steve Kargl
2015-10-16 20:57         ` Tim Prince
2015-10-18  7:30           ` Paul Richard Thomas [this message]
2015-10-18  7:58             ` FX
2015-10-18  9:51               ` Tim Prince
2015-10-18 10:32                 ` FX

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=CAGkQGiKpALMVfaisf-oLF_9uNC4yYhywQVTpS_Hk-J1W7RmryQ@mail.gmail.com \
    --to=paul.richard.thomas@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=fxcoudert@gmail.com \
    --cc=ktietz70@googlemail.com \
    --cc=sgk@troutmask.apl.washington.edu \
    --cc=tprince818.tp@gmail.com \
    /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).