From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5662 invoked by alias); 5 Nov 2013 13:56:25 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 1305 invoked by uid 48); 5 Nov 2013 13:54:23 -0000 From: "fxcoudert at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libfortran X-Bugzilla-Version: 4.8.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fxcoudert 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: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc blocked Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-11/txt/msg00343.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D58020 Francois-Xavier Coudert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fxcoudert at gcc dot gnu.o= rg Blocks| |29383 --- Comment #13 from Francois-Xavier Coudert = --- I may have a bit of time in November and December to look at this. I actual= ly 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=E2=80=A6 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: 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: List-Archive: List-Post: List-Help: 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" 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: In-Reply-To: References: 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?id=58479 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P1