public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/34472] [4.3 Regression] gcc.dg/struct/wo_prof_malloc_size_var.c doesn't work Date: Wed, 16 Jan 2008 11:15:00 -0000 [thread overview] Message-ID: <20080116103339.24656.qmail@sourceware.org> (raw) In-Reply-To: <bug-34472-682@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from rguenth at gcc dot gnu dot org 2008-01-16 10:33 ------- Confirmed on x86_64-unknown-linux-gnu. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 GCC target triplet| |x86_64-*-* Keywords| |ice-on-valid-code Priority|P3 |P2 Last reconfirmed|0000-00-00 00:00:00 |2008-01-16 10:33:38 date| | Summary|gcc.dg/struct/wo_prof_malloc|[4.3 Regression] |_size_var.c doesn't work |gcc.dg/struct/wo_prof_malloc | |_size_var.c doesn't work Target Milestone|--- |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34472
next prev parent reply other threads:[~2008-01-16 10:34 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-12-14 22:52 [Bug tree-optimization/34472] New: " hjl at lucon dot org 2007-12-17 14:08 ` [Bug tree-optimization/34472] " olga at gcc dot gnu dot org 2007-12-17 19:04 ` hjl at lucon dot org 2007-12-17 19:09 ` hjl at lucon dot org 2007-12-19 18:57 ` olga at gcc dot gnu dot org 2007-12-20 0:15 ` hjl at lucon dot org 2008-01-16 11:15 ` rguenth at gcc dot gnu dot org [this message] 2008-01-20 2:14 ` [Bug tree-optimization/34472] [4.3 Regression] " pinskia at gcc dot gnu dot org 2008-01-20 15:34 ` ubizjak at gmail dot com 2008-01-20 15:36 ` zadeck at naturalbridge dot com 2008-01-20 16:43 ` olga at gcc dot gnu dot org 2008-01-20 16:59 ` zadeck at naturalbridge dot com 2008-01-24 18:50 ` rsandifo at gcc dot gnu dot org 2008-01-24 23:40 ` hjl dot tools at gmail dot com
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=20080116103339.24656.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).