From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5907 invoked by alias); 1 May 2014 22:27:57 -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 5874 invoked by uid 48); 1 May 2014 22:27:53 -0000 From: "dominiq at lps dot ens.fr" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/61002] Can't divide by 0 Date: Thu, 01 May 2014 22:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 4.8.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dominiq at lps dot ens.fr X-Bugzilla-Status: RESOLVED 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: bug_status resolution 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: 2014-05/txt/msg00050.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D61002 Dominique d'Humieres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |INVALID --- Comment #5 from Dominique d'Humieres --- > No objection here. I had just missed -fno-range-check, see comment 1. For the record the option is documented at http://gcc.gnu.org/onlinedocs/gfortran/Fortran-Dialect-Options.html#Fortran= -Dialect-Options -fno-range-check Disable range checking on results of simplification of constant expressions during compilation. For example, GNU Fortran will give an error at compile = time when simplifying a =3D 1. / 0. With this option, no error will be given and= a will be assigned the value +Infinity. If an expression evaluates to a value outside of the relevant range of [-HUGE():HUGE()], then the expression will= be replaced by -Inf or +Inf as appropriate. Similarly, DATA i/Z'FFFFFFFF'/ will result in an integer overflow on most systems, but with -fno-range-check the value will =E2=80=9Cwrap around=E2=80=9D and i will be initialized to -1 in= stead.=20 Closing as INVALID. >>From gcc-bugs-return-450359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 02 01:07:28 2014 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 2702 invoked by alias); 2 May 2014 01:07:26 -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 659 invoked by uid 48); 2 May 2014 01:07:20 -0000 From: "jvdelisle at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/60956] error reading (and writing) large text files in gfortran Date: Fri, 02 May 2014 01:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 4.7.3 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jvdelisle 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 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: 2014-05/txt/msg00051.txt.bz2 Content-length: 1035 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60956 Jerry DeLisle changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jvdelisle at gcc dot gnu.org --- Comment #2 from Jerry DeLisle --- (In reply to Dominique d'Humieres from comment #1) > The attached test executes without error when compiled with 4.3.1 (~232s), > but fails with all the revisions I have tried starting at 4.5 (no exhaustive > tests). From pr44292: "gfortran currently fails if the RECL= is larger than > 2 GB", so the failure seems expected. I recall pr44292. I never got a reply so I could not test the patch. I would highly suggest using unformatted IO for these large data sets. Saves space and runs faster, clearly. Its been a while so I don't know if I can find that old patch. Breaking ABI is also an issue, needing some discussion with the gfortran team.