public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Reichelt <reichelt@igpm.rwth-aachen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/7520: internal compiler error in verify_local_live_at_start Date: Thu, 08 Aug 2002 07:16:00 -0000 [thread overview] Message-ID: <20020808133603.8170.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/7520; it has been noted by GNATS. From: Reichelt <reichelt@igpm.rwth-aachen.de> To: gcc-gnats@gcc.gnu.org, chr.breitkopf@magrathea.de, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: optimization/7520: internal compiler error in verify_local_live_at_start Date: Thu, 8 Aug 2002 16:08:47 +0200 Hi, the bug can be reproduced with the following code snippet: -------------------------------snip here------------------------- int foo() { int i; long long int j; while (1) { if (j & 1) ++i; j >>= 1; if (j) return i; } } int bar() { if (foo()) return; } -------------------------------snip here------------------------- Just compile with "gcc -O3" on an i686-pc-linux-gnu box to get the following error: bug.c: In function `bar': bug.c:17: Internal compiler error in verify_local_live_at_start, at flow.c:583 Please submit a full bug report, [etc.] The code is at least questionable as "bar" should return a value. (The same situation occurs in the original example: "getexposure" should return an int, but the last return statement does not return a value.) Greetings, Volker Reichelt http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7520
next reply other threads:[~2002-08-08 13:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-08 7:16 Reichelt [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-09-26 17:30 rth 2002-08-22 8:06 Christoph Breitkopf 2002-08-07 5:46 Christoph Breitkopf 2002-08-07 3:26 chr-breitkopf
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=20020808133603.8170.qmail@sources.redhat.com \ --to=reichelt@igpm.rwth-aachen.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).