public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/18746] [4.0 Regression] segfault with cc1 compiled with checking disabled Date: Wed, 01 Dec 2004 02:13:00 -0000 [thread overview] Message-ID: <20041201021336.31404.qmail@sourceware.org> (raw) In-Reply-To: <20041201005139.18746.kazu@cs.umass.edu> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-12-01 02:13 ------- This does not make sense. This looks like a latent bug. With checking enabled we have the following for the statement: # bufD.1116_5 = V_MAY_DEF <bufD.1116_4>; __builtin_memcpy (&bufD.1116, pD.1117_1, 6); but with checking disabled we get: # bufD.1116_4 = V_MAY_DEF <bufD.1116_3>; # TMT.0D.1125 = V_MAY_DEF <TMT.0D.1125>; __builtin_memcpy (&bufD.1116, pD.1117_1, 6); Note the extra TMT.0D.1125. -- What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |4.0.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18746
next prev parent reply other threads:[~2004-12-01 2:13 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-01 0:52 [Bug tree-optimization/18746] New: " kazu at cs dot umass dot edu 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 [this message] 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=20041201021336.31404.qmail@sourceware.org \ --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).