public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/58020] Code for handling IEEE exceptions
Date: Tue, 05 Nov 2013 13:56:00 -0000	[thread overview]
Message-ID: <bug-58020-4-0VzhVMY6GE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58020-4@http.gcc.gnu.org/bugzilla/>

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-433568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Nov 05 13:57:11 2013
Return-Path: <gcc-bugs-return-433568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7948 invoked by alias); 5 Nov 2013 13:57:11 -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 3252 invoked by uid 48); 5 Nov 2013 13:55:09 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/58479] [4.9 Regression] slow var-tracking on x86_64-linux at -O1 (and above) with -g, but checking disabled
Date: Tue, 05 Nov 2013 13:57: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: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-58479-4-bxGbXsLIS1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58479-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58479-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/msg00345.txt.bz2
Content-length: 290

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P1


  parent reply	other threads:[~2013-11-05 13:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29 17:05 [Bug libfortran/58020] New: " fkrogh#gcc at mathalacarte dot com
2013-07-29 19:29 ` [Bug libfortran/58020] " kargl at gcc dot gnu.org
2013-07-29 21:03 ` fkrogh#gcc at mathalacarte dot com
2013-07-29 22:01 ` sgk at troutmask dot apl.washington.edu
2013-07-30 12:48 ` dominiq at lps dot ens.fr
2013-07-30 14:14 ` burnus at gcc dot gnu.org
2013-07-30 14:36 ` richard.koolhans at gmail dot com
2013-07-30 17:31 ` dominiq at lps dot ens.fr
2013-07-30 17:37 ` sgk at troutmask dot apl.washington.edu
2013-07-30 17:55 ` fkrogh#gcc at mathalacarte dot com
2013-07-31 17:27 ` richard.koolhans at gmail dot com
2013-08-01 13:00 ` dominiq at lps dot ens.fr
2013-08-01 15:51 ` richard.koolhans at gmail dot com
2013-11-05 13:56 ` fxcoudert at gcc dot gnu.org [this message]
2013-11-05 14:05 ` fkrogh at mathalacarte dot com
2013-11-05 14:08 ` fkrogh at mathalacarte dot com
2013-11-05 15:52 ` burnus at gcc dot gnu.org
2013-11-05 16:12 ` fxcoudert at gcc dot gnu.org
2013-11-05 16:27 ` sgk at troutmask dot apl.washington.edu
2013-11-05 16:37 ` fxcoudert at gcc dot gnu.org
2013-11-05 17:05 ` richard.koolhans at gmail dot com
2013-11-05 17:43 ` sgk at troutmask dot apl.washington.edu
2013-11-06 12:28 ` fxcoudert at gcc dot gnu.org
2013-11-25  0:59 ` kargl at gcc dot gnu.org
2014-06-07 10:19 ` fxcoudert at gcc dot gnu.org

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=bug-58020-4-0VzhVMY6GE@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).