public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl>
To: law@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: That annoying dnrm2.f failure on i386
Date: Thu, 02 Apr 1998 11:32:00 -0000	[thread overview]
Message-ID: <9803312132.AA24000@moene.indiv.nluug.nl> (raw)
In-Reply-To: <13329.891072696@hurl.cygnus.com>

[ ... Bernd Schmidt's patch elided ... ]

>  I've installed a slightly modified version of this patch.
>
>  In particular other passes can make use of this
>  information (haifa-sched.c & loop.c for example).  So
>  I've make sure the values are computed regardless of
>  STACK_REGS and updated the comments appropriately.

Great !  Now if you could install Richard Henderson's patch:

Thu Mar 12 09:53:14 1998  Richard Henderson  <rth@cygnus.com>

	* com.c (ffecom_expr_): Revert Oct 22 change.  Instead take  
a WIDENP
	argument so that we can respect the signedness of the  
original type.
	(ffecom_init_0): Do sizetype initialization first.  Init new
	ssizetype.

then all the current Fortran problems would be solved :-)

I have tried this patch on both an Alpha (solves the problem it was  
meant to solve and runs at least one other program correctly) and  
my m68k-next-nextstep3 system - just to check whether those changes  
wouldn't accidentally break a previously working combination.

(see http://egcs.cygnus.com/ml/egcs/1998-Mar/0456.html )

HTH,
Toon.

  reply	other threads:[~1998-04-02 11:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-18  4:16 Bernd Schmidt
1998-02-18 14:54 ` Toon Moene
1998-02-18 14:54 ` Dave Love
1998-03-29  5:14 ` Jeffrey A Law
1998-04-02 11:32   ` Toon Moene [this message]
1998-04-01 22:44     ` Jeffrey A Law
1998-04-01 23:41       ` Richard Henderson
1998-04-03 21:52         ` Jeffrey A Law
1998-04-03 21:52         ` Jim Wilson
1998-04-04 20:05           ` Richard Henderson

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=9803312132.AA24000@moene.indiv.nluug.nl \
    --to=toon@moene.indiv.nluug.nl \
    --cc=egcs@cygnus.com \
    --cc=law@cygnus.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).