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 fortran/67531] FAIL: gfortran.dg/ieee/large_2.f90 -O0 execution test Date: Thu, 10 Sep 2015 21:45:00 -0000 [thread overview] Message-ID: <bug-67531-4-bLMRddvfPi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67531-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67531 --- Comment #3 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> --- (In reply to Pat Haugen from comment #2) > pthaugen@genoa:~$ ~/install/gcc/trunk/bin/gcc z.c -lm && ./a.out > 0.3333333333333333333333333333333353876586 > 0.3333333333333333333333333333333292246827 How about with this? I'm trying to come as close as possible to the exact sequence of fe.etround() calls as the Fortran front-end and runtime library would end up performing… #include <fenv.h> #include <stdio.h> int main (void) { int r; long double x1, x2, x; x1 = 1; x = 3; r = fegetround (); fesetround (FE_UPWARD); x1 = x1 / x; fesetround (r); x2 = 1; x = 3; r = fegetround (); fesetround (FE_DOWNWARD); x2 = x2 / x; fesetround (r); printf ("%.40Lg\n", x1); printf ("%.40Lg\n", x2); } >From gcc-bugs-return-496923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Sep 10 21:52:57 2015 Return-Path: <gcc-bugs-return-496923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 70526 invoked by alias); 10 Sep 2015 21:52:57 -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 70460 invoked by uid 48); 10 Sep 2015 21:52:54 -0000 From: "pangbw at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/59124] [4.9/5/6 Regression] Wrong warnings "array subscript is above array bounds" Date: Thu, 10 Sep 2015 21:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 4.8.3 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: pangbw at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.4 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-59124-4-jJrtz7gH2X@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59124-4@http.gcc.gnu.org/bugzilla/> References: <bug-59124-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: 2015-09/txt/msg00901.txt.bz2 Content-length: 1339 https://gcc.gnu.org/bugzilla/show_bug.cgi?idY124 --- Comment #19 from baoshan <pangbw at gmail dot com> --- I did a little investigation to the code: The warning occurs because tree_int_cst_lt (up_bound, up_sub) is true here: else if (TREE_CODE (up_sub) == INTEGER_CST && (ignore_off_by_one ? (tree_int_cst_lt (up_bound, up_sub) && !tree_int_cst_equal (up_bound_p1, up_sub)) : (tree_int_cst_lt (up_bound, up_sub) || tree_int_cst_equal (up_bound_p1, up_sub)))) { if (dump_file && (dump_flags & TDF_DETAILS)) { fprintf (dump_file, "Array bound warning for "); dump_generic_expr (MSG_NOTE, TDF_SLIM, ref); fprintf (dump_file, "\n"); } warning_at (location, OPT_Warray_bounds, => "array subscript is above array bounds"); TREE_NO_WARNING (ref) = 1; } I dumped the tree up_bound and up_sub: (gdb) p debug_tree(up_bound) <integer_cst 0x7ffff6acd3a8 type <integer_type 0x7ffff6c3d0a8 sizetype> constant 5> p debug_tree(up_sub) <integer_cst 0x7ffff6ae92d0 type <integer_type 0x7ffff6c3d738 unsigned int> constant 4294967291> We can see the value of up_sub is represented as unsigned int value 4294967291 which is really weird to me, it suppose to be a int value -5 here.
next prev parent reply other threads:[~2015-09-10 21:45 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-09 22:09 [Bug fortran/67531] New: " pthaugen at gcc dot gnu.org 2015-09-10 21:31 ` [Bug fortran/67531] " pthaugen at gcc dot gnu.org 2015-09-10 21:45 ` fxcoudert at gcc dot gnu.org [this message] 2015-09-10 22:00 ` schwab@linux-m68k.org 2015-09-11 13:50 ` [Bug fortran/67531] No IEEE rounding support for powerpc long double type pthaugen at gcc dot gnu.org 2021-05-04 12:31 ` rguenth 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-67531-4-bLMRddvfPi@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: linkBe 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).