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/13741] [3.3/3.4/3.5 Regression] [tree-ssa] Variable-length arrays broke in gcc 3.x Date: Tue, 18 May 2004 03:54:00 -0000 [thread overview] Message-ID: <20040517153830.9875.qmail@sourceware.org> (raw) In-Reply-To: <20040119151417.13741.dmarkuson@arrayinc.com> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-05-17 15:38 ------- Back in 3.5.0 by the merge of the tree-ssa. -- What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|tree-ssa |3.5.0 What |Removed |Added ---------------------------------------------------------------------------- What |Removed |Added ---------------------------------------------------------------------------- Known to work|2.95.3 3.5.0 |2.95.3 Summary|[3.3/3.4 Regression] [tree- |[3.3/3.4/3.5 Regression] |ssa] Variable-length arrays |[tree-ssa] Variable-length |broke in gcc 3.x |arrays broke in gcc 3.x http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13741
next prev parent reply other threads:[~2004-05-17 15:38 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-19 15:14 [Bug c/13741] New: Variable-length arrays broke in gcc 3.x? dmarkuson at arrayinc dot com 2004-01-19 15:49 ` [Bug c/13741] [3.3/3.4/3.5 Regression] " pinskia at gcc dot gnu dot org 2004-01-23 20:46 ` reichelt at gcc dot gnu dot org 2004-01-23 20:55 ` [Bug c/13741] [3.3/3.4/3.5 Regression] Variable-length arrays broke in gcc 3.x pinskia at gcc dot gnu dot org 2004-01-24 15:31 ` pinskia at gcc dot gnu dot org 2004-03-01 0:10 ` mmitchel at gcc dot gnu dot org 2004-03-08 15:53 ` pinskia at gcc dot gnu dot org 2004-04-14 10:15 ` reichelt at gcc dot gnu dot org 2004-04-14 11:19 ` reichelt at gcc dot gnu dot org 2004-04-14 12:53 ` [Bug c/13741] [3.3/3.4 Regression] [tree-ssa] [merge?] " pinskia at gcc dot gnu dot org 2004-04-15 23:04 ` [Bug c/13741] [3.3/3.4 Regression] [tree-ssa] " pinskia at gcc dot gnu dot org 2004-04-22 21:24 ` pinskia at gcc dot gnu dot org 2004-04-23 1:26 ` pinskia at gcc dot gnu dot org 2004-05-05 21:01 ` giovannibajo at libero dot it 2004-05-06 20:48 ` pinskia at gcc dot gnu dot org 2004-05-18 3:54 ` pinskia at gcc dot gnu dot org [this message] 2004-06-23 14:55 ` [Bug tree-optimization/13741] " reichelt at gcc dot gnu dot org 2004-06-24 1:39 ` giovannibajo at libero dot it 2004-06-24 2:08 ` mark at codesourcery dot com 2004-07-29 14:57 ` pinskia at gcc dot gnu dot org 2004-08-19 20:34 ` mmitchel 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=20040517153830.9875.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).