public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: FX Coudert <fxcoudert@gmail.com>
To: n8tm@aol.com
Cc: pinskia@gmail.com,  tprince@computer.org,
	 Tobias Burnus <burnus@net-b.de>,
	 Paul Thomas <paulthomas2@wanadoo.fr>,
	 Jerry DeLisle <jvdelisle@verizon.net>,
	 "fortran@gcc.gnu.org List" <fortran@gcc.gnu.org>
Subject: Re:
Date: Thu, 12 Apr 2007 21:00:00 -0000	[thread overview]
Message-ID: <5757969E-FE19-4D76-9E9E-A61209CDDF07@gmail.com> (raw)
In-Reply-To: <8C94B5ACA298987-8B4-8502@WEBMAIL-DB13.sysops.aol.com>

> Your patch text was mangled various ways by various mail readers  
> (all off line this afternoon).

And I almost missed your mail because it landed in my spam folder :)

> After I performed the mandatory quarterly Windows repair, and  
> applied the changes in vim, it works for cygwin.
> I'm attempting to attach my reconstruction of your patch, along  
> with the testsuite run prior to patch

I think you meant "after the patch", because otherwise it doesn't  
make sense, as c_by_val_1.f is not flagged as a failure.

I commited the patch to trunk (as rev. 123768), thanks for testing. I  
also saw that gfortran.dg/intrinsic_intkinds_1.f90 is failing, could  
you post the related testsuite log excerpt ($builddir/gcc/testsuite/ 
gfortran/gfortran.log, grep for FAIL)?

Thanks again,
FX

       reply	other threads:[~2007-04-12 21:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8C94B5ACA298987-8B4-8502@WEBMAIL-DB13.sysops.aol.com>
2007-04-12 21:00 ` FX Coudert [this message]
2023-08-22 13:06 Mamadou Diop
2023-08-23  8:19 ` Arjen Markus
  -- strict thread matches above, loose matches on Subject: below --
2021-03-10 18:34 mscfd
2021-03-11  7:48 ` Richard Biener
2020-07-26  4:49 Damian Rouson
2020-07-26  8:55 ` Arjen Markus
2013-03-13  5:51 Re: DavidLNewton
2013-03-12  9:22 Re: DavidLNewton
2007-07-06  6:27 Re: Tobias Burnus
2007-07-06  8:17 ` Re: Lee Millward
2007-03-27 13:13 Re: Paul Richard Thomas
     [not found] <4195D82C2DB1D211B9910008C7C9B06F01F373E0@lr0nt3.lr.tudelft.nl>
2003-12-07 14:17 ` Re: Paul Brook

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=5757969E-FE19-4D76-9E9E-A61209CDDF07@gmail.com \
    --to=fxcoudert@gmail.com \
    --cc=burnus@net-b.de \
    --cc=fortran@gcc.gnu.org \
    --cc=jvdelisle@verizon.net \
    --cc=n8tm@aol.com \
    --cc=paulthomas2@wanadoo.fr \
    --cc=pinskia@gmail.com \
    --cc=tprince@computer.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).