public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kazu at cs dot umass dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/18746] New: segfault with cc1 compiled with checking disabled
Date: Wed, 01 Dec 2004 00:52:00 -0000	[thread overview]
Message-ID: <20041201005139.18746.kazu@cs.umass.edu> (raw)

Build cc1 with checking disabled.
Then compile the following with ./cc1 -quiet -O2.

extern void abort (void) __attribute__ ((noreturn));
extern char *strcpy (char *__restrict __dest, __const char *__restrict __src);

int
foo (int aaa, int bbb)
{
  static char buf[30];
  const char *p;

  switch (aaa)
    {
    case 10:
      p = "hello";
      break;

    case 20:
      p = "world";
      break;

    default:
      abort ();
    }

  if (bbb)
    {
      strcpy (buf, "banana");
      return 1;
    }
  strcpy (buf, p);

  return 0;
}

I get "internal compiler error: Segmentation fault".

The testcase was reduced from i386.c.

-- 
           Summary: segfault with cc1 compiled with checking disabled
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: kazu at cs dot umass dot edu
                CC: gcc-bugs at gcc dot gnu dot org
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18746


             reply	other threads:[~2004-12-01  0:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01  0:52 kazu at cs dot umass dot edu [this message]
2004-12-01  0:55 ` Diego Novillo
2004-12-01  0:55 ` [Bug tree-optimization/18746] " dnovillo at redhat dot com
2004-12-01  1:00 ` [Bug tree-optimization/18746] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-12-01  1:04 ` kazu at cs dot umass dot edu
2004-12-01  1:33 ` pinskia at gcc dot gnu dot org
2004-12-01  2:12 ` kazu at cs dot umass dot edu
2004-12-01  2:13 ` pinskia at gcc dot gnu dot org
2004-12-01  2:22 ` pinskia at gcc dot gnu dot org
2004-12-01  2:31 ` pinskia at gcc dot gnu dot org
2004-12-01  2:33 ` pinskia at gcc dot gnu dot org
2004-12-01  2:46 ` pinskia at gcc dot gnu dot org
2004-12-01  3:01 ` pinskia at gcc dot gnu dot org
2004-12-01 23:53 ` cvs-commit at gcc dot gnu dot org
2004-12-01 23:54 ` pinskia at gcc dot gnu dot 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=20041201005139.18746.kazu@cs.umass.edu \
    --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: 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).