public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: matt@3am-software.com
To: gcc-gnats@gcc.gnu.org
Subject: middle-end/7044: gcc-current
Date: Sun, 16 Jun 2002 02:46:00 -0000	[thread overview]
Message-ID: <20020616004318.21909.qmail@sources.redhat.com> (raw)


>Number:         7044
>Category:       middle-end
>Synopsis:       gcc-current
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jun 15 17:46:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     matt@3am-software.com
>Release:        GNU C version 3.2 20020615 (experimental) (vax-netbsdelf)
>Organization:
>Environment:
cross-compiler on NetBSD-1.6A i386
>Description:
After updating GCC via anoncvs, the included file fails to compile at any optimization level.  Though GNU C version 3.2 20020610 (experimental) (vax-netbsdelf) from 5 days ago compiled it fine. 
>How-To-Repeat:
Compile this:
void
xx(int a)
{
        switch (a) {
        case  1: z(); break;
        case  5: x(); break;
        case  7: v(); break;
        case 11: s(); break;
        case 13: q(); break;
        }
}

results in:

./cc1 -version -O0 -quiet /tmp/x.i 
GNU C version 3.2 20020615 (experimental) (vax-netbsdelf)
        compiled by GNU C version 2.95.3 20010315 (release) (NetBSD nb2).
/tmp/x.i: In function `xx':
/tmp/x.i:18: error: missing barrier after block 0
/tmp/x.i:18: internal compiler error: verify_flow_info failed
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-06-16  0:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020616004318.21909.qmail@sources.redhat.com \
    --to=matt@3am-software.com \
    --cc=gcc-gnats@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: link
Be 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).