public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/35198] [4.1/4.2/4.3 Regression] missed evaluation of VM array type when used as a cast Date: Sun, 17 Feb 2008 23:12:00 -0000 [thread overview] Message-ID: <20080217231207.8336.qmail@sourceware.org> (raw) In-Reply-To: <bug-35198-1447@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from joseph at codesourcery dot com 2008-02-17 23:12 ------- Subject: Re: [4.1/4.2/4.3 Regression] missed evaluation of VM array type when used as a cast My view remains as I said in <http://gcc.gnu.org/ml/gcc-patches/2006-09/msg00039.html>: front ends should make the internal variable for VLA sizes explicit. This is not however suitable for implementing in development stage 3, let alone in regression-only mode or on release branches. There may of course be a simpler fix for this particular bug. I don't think side effects in VLA size expressions (let alone in VLA size expressions in casts) are that likely to be used in real code outside of conformance testsuites, so I wouldn't consider this regression (worked with 2.95.3, failed with 3.0.4) of great importance. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35198
next prev parent reply other threads:[~2008-02-17 23:12 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-14 18:58 [Bug c/35198] New: missed evaluation of VM array type mrs at apple dot com 2008-02-14 21:43 ` [Bug c/35198] [4.1/4.2/4.3 Regression] missed evaluation of VM array type when used as a cast rguenth at gcc dot gnu dot org 2008-02-17 16:20 ` rguenth at gcc dot gnu dot org 2008-02-17 16:34 ` ebotcazou at gcc dot gnu dot org 2008-02-17 23:12 ` joseph at codesourcery dot com [this message] 2008-02-17 23:22 ` rguenth at gcc dot gnu dot org 2008-05-19 20:33 ` [Bug c/35198] [4.1/4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org 2008-07-04 23:00 ` [Bug c/35198] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org 2008-10-24 0:10 ` jsm28 at gcc dot gnu dot org 2008-10-24 19:38 ` jsm28 at gcc dot gnu dot org 2008-11-12 23:16 ` jsm28 at gcc dot gnu dot org 2009-03-29 18:14 ` [Bug c/35198] [4.2/4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org 2009-03-29 18:23 ` jsm28 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=20080217231207.8336.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).