public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/67429] [5/6 Regression] Missing part of error messages. Date: Wed, 02 Sep 2015 08:56:00 -0000 [thread overview] Message-ID: <bug-67429-4-pwwIrL8SmC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67429-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429 --- Comment #11 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- (In reply to Manuel López-Ibáñez from comment #10) > > Error: Expecting END BLOCK statement at (1) > > (null):0: confused by earlier errors, bailing out > > > Even if *I* cannot reproduce this, such an error should be easy to debug: > Just put a break in diagnostic_report_diagnostic on the line that gives > this message and go up to find out what triggered this code to run. > My guess is that you are somehow triggering an ICE while reporting an ICE. > It would be interesting to understand where that strange location comes > from (I guess it is UNKNOWN_LOCATION?). And also to harden that code to not > try to print a null s.file pointer! Sorry for the confusion I sometime get this kind of error instead of the usual ICE when using compilers configured with '--enable-checking=release'. >From gcc-bugs-return-496152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Sep 02 09:04:31 2015 Return-Path: <gcc-bugs-return-496152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 35518 invoked by alias); 2 Sep 2015 09:04:31 -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 35471 invoked by uid 48); 2 Sep 2015 09:04:27 -0000 From: "xuejuncao at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/67433] ?: expression returns unexpected value when condition is a bool variable which memory is not true/false Date: Wed, 02 Sep 2015 09:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: xuejuncao at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: Message-ID: <bug-67433-4-VbD8ilbHXY@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-67433-4@http.gcc.gnu.org/bugzilla/> References: <bug-67433-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/msg00130.txt.bz2 Content-length: 693 https://gcc.gnu.org/bugzilla/show_bug.cgi?idg433 --- Comment #8 from xuejuncao <xuejuncao at gmail dot com> --- thanks, i get the below result with -fsanitize=undefined boolmagic.c:12:16: runtime error: load of value 255, which is not a valid value for type '_Bool' boolmagic.c:13:15: runtime error: load of value 255, which is not a valid value for type '_Bool' boolmagic.c:14:15: runtime error: load of value 255, which is not a valid value for type '_Bool' b = 1, i = 1, j = 1 but, can i say the "-fsanitize=undefined" will _corrects_ the undefined behaviour? or replace the code by if/else, which works fine (lucky?) int i; // = (u.b ? 1 : 0); if (u.b) i = 1; else i = 0;
next prev parent reply other threads:[~2015-09-02 8:56 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-01 19:55 [Bug fortran/67429] New: " dominiq at lps dot ens.fr 2015-09-01 20:00 ` [Bug fortran/67429] " kargl at gcc dot gnu.org 2015-09-01 20:05 ` dominiq at lps dot ens.fr 2015-09-01 20:13 ` sgk at troutmask dot apl.washington.edu 2015-09-01 20:24 ` dominiq at lps dot ens.fr 2015-09-01 20:46 ` sgk at troutmask dot apl.washington.edu 2015-09-01 21:04 ` pault at gcc dot gnu.org 2015-09-01 21:10 ` pault at gcc dot gnu.org 2015-09-01 22:17 ` dominiq at lps dot ens.fr 2015-09-02 0:30 ` manu at gcc dot gnu.org 2015-09-02 8:56 ` dominiq at lps dot ens.fr [this message] 2015-09-02 9:05 ` dominiq at lps dot ens.fr 2015-09-02 9:16 ` rguenth at gcc dot gnu.org 2015-09-02 10:42 ` dominiq at lps dot ens.fr 2015-09-02 18:23 ` pault at gcc dot gnu.org 2015-09-02 18:48 ` manu at gcc dot gnu.org 2015-09-04 18:38 ` pault 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-67429-4-pwwIrL8SmC@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).