[Bug libfortran/58020] Code for handling IEEE exceptions

["fkrogh at mathalacarte dot com" <gcc-bugzilla@gcc.gnu.org>]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58020

--- Comment #15 from fkrogh at mathalacarte dot com ---
Hi Francois-Xavier --
      I'm sorry, but Richard did all the work on this, and I'm just a
sorry middle man.  We are both people specializing in computational
mathematics, and thus not likely to be helpful with respect to your
question number 2.  With this email I'm asking Richard to give you a
more detailed response.
Many thanks for looking into this,
      Fred



On 11/05/2013 05:54 AM, fxcoudert at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58020
>
> Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |fxcoudert at gcc dot gnu.org
>               Blocks|                            |29383
>
> --- Comment #13 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
> I may have a bit of time in November and December to look at this. I actually
> had started implementing the IEEE modules in gfortran back in 2008-2009, but
> never got too far (I was unclear, back then, on the exact requirements for
> things like constant folding… some interps have made clear that our job is
> actually easier than I thought back then).
>
> So, a few questions to Fred and Richard:
>
>   0. Thanks for contributing your work to our open-source effort!
>   1. What is the current status of your code w.r.t. the IEEE modules? Do you
> have full coverage? Full test coverage? Does it depend on 32 vs 64-bit?
>   2. Although you don't plan to support other architectures than i386/x86_64, we
> have to think about it. The current approach does not seem to lend itself to
> writing new ports easily. How do you think we could better insulate the
> processor-specific code from the higher-level IEEE modules themselves?
>
> I have started reading the code, but your answers would be very much
> appreciated!
>
>From gcc-bugs-return-433573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Nov 05 14:19:43 2013
Return-Path: <gcc-bugs-return-433573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7808 invoked by alias); 5 Nov 2013 14:19:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5528 invoked by uid 55); 5 Nov 2013 14:17:39 -0000
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/58981] movmem/setmem use mode wider than Pmode for size
Date: Tue, 05 Nov 2013 14:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-58981-4-va3vuD4zZ8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58981-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58981-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-11/txt/msg00350.txt.bz2
Content-length: 815

http://gcc.gnu.org/bugzilla/show_bug.cgi?idX981

--- Comment #8 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> ---
Author: hjl
Date: Tue Nov  5 14:17:33 2013
New Revision: 204394

URL: http://gcc.gnu.org/viewcvs?rev 4394&root=gcc&view=rev
Log:
Don't use mode wider than Pmode for size in movmem/setmem

gcc/

    PR middle-end/58981
    * doc/md.texi (@code{movmem@var{m}}): Specify Pmode as mode of
    pattern, instead of word_mode.

    * expr.c (emit_block_move_via_movmem): Don't use mode wider than
    Pmode for size.
    (set_storage_via_setmem): Likewise.

gcc/testsuite/

    PR middle-end/58981
    * gcc.dg/pr58981.c: New test.

Added:
    trunk/gcc/testsuite/gcc.dg/pr58981.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/doc/md.texi
    trunk/gcc/expr.c
    trunk/gcc/testsuite/ChangeLog