On Sat, Jan 4, 2014 at 9:13 PM, Steve Kargl
wrote:
> On Wed, Jan 01, 2014 at 07:49:16PM -0800, Mike Stump wrote:
>> On Nov 23, 2013, at 12:16 PM, Steve Kargl
>> wrote:
>>> On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
Richi has asked the we break the wide-int patch so that the
On Wed, Jan 01, 2014 at 07:49:16PM -0800, Mike Stump wrote:
> On Nov 23, 2013, at 12:16 PM, Steve Kargl
> wrote:
>> On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
>>> Richi has asked the we break the wide-int patch so that the
>>> individual port and front end maintainers can review
On Nov 23, 2013, at 12:16 PM, Steve Kargl
wrote:
> On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
>> Richi has asked the we break the wide-int patch so that the individual port
>> and front end maintainers can review their parts without have to go through
>> the entire patch.Th
On 11/24/2013 08:38 AM, N.M. Maclaren wrote:
On Nov 24 2013, Kenneth Zadeck wrote:
Thank you for your posting. That certainly clears up my understanding.
If there is a clear description of the subset
of C++ that the front-end is allowed to use, a pointer to it for the
benefit of Fortran/C/Ad
On Sun, Nov 24, 2013 at 2:38 PM, N.M. Maclaren wrote:
> The main problem is that integer constant expressions in C are limited to
> the built-in operators, of which the only tricky ones are division and
> remainder (and, occasionally, multiplication) - see C11 6.6#3. Fortran
> is not so limited, a
Am 24.11.2013 13:56, schrieb Kenneth Zadeck:
On 11/24/2013 05:50 AM, Tobias Burnus wrote:
- if (hi || low < 0
...
+ if (((!as || as->type != AS_ASSUMED_RANK)
+ && wi::geu_p (bound, GFC_TYPE_ARRAY_RANK (TREE_TYPE (desc
+ || wi::gtu_p (bound, GFC_MAX_DIMENSIONS))
gfc_error ("'dim' argument of
Hi,
On 2013-11-24 22:38, N.M. Maclaren wrote:
The main problem is that integer constant expressions in C are limited to
the built-in operators, of which the only tricky ones are division and
remainder (and, occasionally, multiplication) - see C11 6.6#3. Fortran
is not so limited, and there are
On Nov 24 2013, Kenneth Zadeck wrote:
Thank you for your posting. That certainly clears up my understanding.
If there is a clear description of the subset
of C++ that the front-end is allowed to use, a pointer to it for the
benefit of Fortran/C/Ada/whatever people would be useful. But that's
On 11/24/2013 05:50 AM, Tobias Burnus wrote:
Mike Stump wrote:
Richi has asked the we break the wide-int patch so that the
individual port and front end maintainers can review their parts
without have to go through the entire patch.This patch covers the
fortran front end.
Nice clean up.
On 11/24/2013 05:16 AM, N.M. Maclaren wrote:
On Nov 23 2013, Andrew Pinski wrote:
On Sat, Nov 23, 2013 at 12:16 PM, Steve Kargl
wrote:
On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
Richi has asked the we break the wide-int patch so that the
individual port and front end maint
Mike Stump wrote:
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the fortran front end.
Nice clean up. The new class looks much cleaner as it avoids
On Nov 23 2013, Andrew Pinski wrote:
On Sat, Nov 23, 2013 at 12:16 PM, Steve Kargl
wrote:
On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
Richi has asked the we break the wide-int patch so that the individual
port and front end maintainers can review their parts without have to
Steve Kargl writes:
> On Sat, Nov 23, 2013 at 01:31:04PM -0800, Andrew Pinski wrote:
>> On Sat, Nov 23, 2013 at 12:16 PM, Steve Kargl
>> wrote:
>> > On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
>> >> Richi has asked the we break the wide-int patch so that the individual
>> >> por
On Sat, Nov 23, 2013 at 4:26 PM, Steve Kargl
wrote:
> On Sat, Nov 23, 2013 at 01:31:04PM -0800, Andrew Pinski wrote:
>> On Sat, Nov 23, 2013 at 12:16 PM, Steve Kargl
>> wrote:
>> > On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
>> >> Richi has asked the we break the wide-int patch so
On Sat, Nov 23, 2013 at 01:31:04PM -0800, Andrew Pinski wrote:
> On Sat, Nov 23, 2013 at 12:16 PM, Steve Kargl
> wrote:
> > On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
> >> Richi has asked the we break the wide-int patch so that the individual
> >> port and front end maintainers c
On Sat, Nov 23, 2013 at 1:31 PM, Andrew Pinski wrote:
> On Sat, Nov 23, 2013 at 12:16 PM, Steve Kargl
> wrote:
>> On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
>>> Richi has asked the we break the wide-int patch so that the individual port
>>> and front end maintainers can review t
On Sat, Nov 23, 2013 at 12:16 PM, Steve Kargl
wrote:
> On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
>> Richi has asked the we break the wide-int patch so that the individual port
>> and front end maintainers can review their parts without have to go through
>> the entire patch.
On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
> Richi has asked the we break the wide-int patch so that the individual port
> and front end maintainers can review their parts without have to go through
> the entire patch.This patch covers the fortran front end.
>
> Ok?
>
> +
18 matches
Mail list logo
