public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mark at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/14545] [3.4/3.5 Regression] Cannot compile pooma-gcc (regression) Date: Thu, 18 Mar 2004 15:48:00 -0000 [thread overview] Message-ID: <20040318154849.17986.qmail@sources.redhat.com> (raw) In-Reply-To: <20040312062911.14545.schmid@snake.iap.physik.tu-darmstadt.de> ------- Additional Comments From mark at codesourcery dot com 2004-03-18 15:48 ------- Subject: Re: [3.4/3.5 Regression] Cannot compile pooma-gcc (regression) giovannibajo at libero dot it wrote: >------- Additional Comments From giovannibajo at libero dot it 2004-03-18 15:31 ------- >Subject: Re: [3.4/3.5 Regression] Cannot compile pooma-gcc (regression) > >bangerth at dealii dot org wrote: > > > >>This whole business with non-dependent initializers has run somehow >>out of control given how late we are in the release cycle. We must >>have had at least a dozen different reports about this problem. Has anyone >>considered reverting the patch that introduced this instability? We >>seem to be stomping out fires that keep popping up everywhere... >> >> > >The patch just helps finding latent problems, really. It's not that the patch >was not complete or instable, it just somehow helps uncovering problems with >our detection of constant expressions. Plus, we're making big progress, because >now it's always possible to use const locals as template arguments while before >it was failing very often. > > Right. The follow-on patches that we've been making have definitely been fixing bugs; we'd want them independently of the initializer patch. >Anyway, this is the updated patch, and I'm running the regression test right >now. OK for mainline and 3.4 if it passes? > Yes, this patch looks good. Thanks! -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14545
next prev parent reply other threads:[~2004-03-18 15:48 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-03-12 6:29 [Bug c++/14545] New: " schmid at snake dot iap dot physik dot tu-darmstadt dot de 2004-03-12 6:32 ` [Bug c++/14545] " schmid at snake dot iap dot physik dot tu-darmstadt dot de 2004-03-12 6:42 ` [Bug c++/14545] [3.4/3.5 Regression] " pinskia at gcc dot gnu dot org 2004-03-13 23:41 ` schmid at snake dot iap dot physik dot tu-darmstadt dot de 2004-03-14 3:45 ` pinskia at gcc dot gnu dot org 2004-03-15 13:41 ` giovannibajo at libero dot it 2004-03-15 16:58 ` giovannibajo at libero dot it 2004-03-16 15:20 ` pinskia at gcc dot gnu dot org 2004-03-17 1:19 ` giovannibajo at libero dot it 2004-03-17 1:34 ` mark at codesourcery dot com 2004-03-18 1:12 ` giovannibajo at libero dot it 2004-03-18 14:04 ` bangerth at dealii dot org 2004-03-18 14:42 ` giovannibajo at libero dot it 2004-03-18 15:09 ` bangerth at dealii dot org 2004-03-18 15:19 ` mark at codesourcery dot com 2004-03-18 15:30 ` bangerth at dealii dot org 2004-03-18 15:32 ` giovannibajo at libero dot it 2004-03-18 15:48 ` mark at codesourcery dot com [this message] 2004-03-18 15:53 ` bangerth at dealii dot org 2004-03-19 9:59 ` cvs-commit at gcc dot gnu dot org 2004-03-19 11:42 ` cvs-commit at gcc dot gnu dot org 2004-03-19 11:42 ` giovannibajo at libero dot it
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=20040318154849.17986.qmail@sources.redhat.com \ --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).