This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [fortran, patch] Handle POW/CPOW builtins for all floating-point types

From: Tobias Burnus <burnus at net-b dot de>
To: FX <fxcoudert at gmail dot com>
Cc: Fortran List <fortran at gcc dot gnu dot org>, gcc-patches at gcc dot gnu dot org
Date: Wed, 01 Sep 2010 12:32:51 +0200
Subject: Re: [fortran, patch] Handle POW/CPOW builtins for all floating-point types
References: <550FFCCF-E4EB-4731-8683-B03BF3E71539@gmail.com> <4C7E05D7.9060004@net-b.de> <75D25071-F1F3-498B-A1AE-F1A23C028A37@gmail.com> <4C7E1483.8000503@net-b.de> <702C8ECB-7D2C-4AD8-83FB-E860C902FF95@gmail.com>

On 09/01/2010 10:59 AM, FX wrote:

So everything in libgfortran that checks for (dtype == GFC_DTYPE_REAL) will need to check for (dtype == GFC_DTYPE_REAL || dtype == GFC_DTYPE_FLOAT128).

Yes.

Before I go and change everything, now that the "end of stage 1" date has been announced (Oct 27th), will there be a push for the array descriptor rework to make it in 4.6, or will it wait for 4.7?

That's unclear. It still requires some work to get the basic implementation regression free, then one needs to agree on the used elements - and implement them. I think end of October is possible, but I wouldn't be surprised if it takes longer.

Tobias

References:
- Re: [fortran, patch] Handle POW/CPOW builtins for all floating-point types
  - From: Tobias Burnus
- Re: [fortran, patch] Handle POW/CPOW builtins for all floating-point types
  - From: FX
- Re: [fortran, patch] Handle POW/CPOW builtins for all floating-point types
  - From: Tobias Burnus
- Re: [fortran, patch] Handle POW/CPOW builtins for all floating-point types
  - From: FX

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]