public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marcus at jet dot franken dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/30375] New: tree-ssa-dse incorrectly removes struct initialization Date: Thu, 04 Jan 2007 22:04:00 -0000 [thread overview] Message-ID: <bug-30375-3760@http.gcc.gnu.org/bugzilla/> (raw) A wine testcase started failing with the trunk compiler some days ago. The difference is pretty obivous in the tree dump: diff -u encode.c.056t.dce3 encode.c.057t.dse1 --- encode.c.056t.dce3 2007-01-04 23:03:14.000000000 +0100 +++ encode.c.057t.dse1 2007-01-04 23:03:14.000000000 +0100 @@ -52,7 +52,6 @@ int iftmp.507; <bb 2>: - info = {}; point = {}; entry = {}; buf = 0B; However, if you look at it, info is clearly used right below. I will attach .i, and the two dump files. -- Summary: tree-ssa-dse incorrectly removes struct initialization Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: marcus at jet dot franken dot de GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30375
next reply other threads:[~2007-01-04 22:04 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-04 22:04 marcus at jet dot franken dot de [this message] 2007-01-04 22:08 ` [Bug c/30375] " marcus at jet dot franken dot de 2007-01-04 22:08 ` marcus at jet dot franken dot de 2007-01-04 22:09 ` marcus at jet dot franken dot de 2007-01-04 22:10 ` marcus at jet dot franken dot de 2007-01-04 22:22 ` [Bug tree-optimization/30375] [4.3 Regression] " pinskia at gcc dot gnu dot org 2007-01-05 5:29 ` pinskia at gcc dot gnu dot org 2007-02-03 15:28 ` steven at gcc dot gnu dot org 2007-02-03 15:28 ` steven at gcc dot gnu dot org 2007-02-03 15:49 ` dnovillo at gcc dot gnu dot org 2007-03-09 20:05 ` aldyh at gcc dot gnu dot org 2007-03-09 23:30 ` pinskia at gcc dot gnu dot org 2007-07-24 20:30 ` marcus at jet dot franken dot de 2007-07-24 20:31 ` marcus at jet dot franken dot de 2007-07-24 20:31 ` marcus at jet dot franken dot de 2007-07-24 20:32 ` marcus at jet dot franken dot de 2007-07-24 20:32 ` marcus at jet dot franken dot de 2007-07-25 5:11 ` marcus at jet dot franken dot de 2007-08-06 5:53 ` pinskia at gcc dot gnu dot org 2007-08-10 0:24 ` mmitchel at gcc dot gnu dot org 2007-08-22 20:24 ` rguenth at gcc dot gnu dot org 2007-08-22 20:25 ` rguenth at gcc dot gnu dot org 2007-08-31 10:51 ` rguenth at gcc dot gnu dot org 2007-08-31 10:59 ` rguenth at gcc dot gnu dot org 2007-08-31 13:56 ` rguenth at gcc dot gnu dot org 2007-08-31 14:13 ` rguenth at gcc dot gnu dot org 2007-08-31 14:27 ` rguenth at gcc dot gnu dot org 2007-08-31 14:34 ` rguenth at gcc dot gnu dot org 2007-09-02 18:35 ` marcus at jet dot franken dot de 2007-09-25 13:59 ` rguenth at gcc dot gnu dot org 2007-09-25 14:49 ` rguenth at gcc dot gnu dot org 2007-09-26 9:31 ` belyshev at depni dot sinp dot msu dot ru 2007-09-26 9:46 ` belyshev at depni dot sinp dot msu dot ru 2007-09-26 11:55 ` rguenth at gcc dot gnu dot org 2007-09-26 11:57 ` rguenth 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=bug-30375-3760@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).