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:19:00 -0000 [thread overview]
Message-ID: <20040318151912.29089.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:19 -------
Subject: Re: [3.4/3.5 Regression] Cannot compile pooma-gcc
(regression)
bangerth at dealii dot org wrote:
>------- Additional Comments From bangerth at dealii dot org 2004-03-18 15:08 -------
>Oh, hell. I was just posting this as an amusement for everyone, because
>it is so _really_ short. How can we _not_ get this right?
>
>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...
>
>
Yes, I've been considering reverting that patch.
However, some of the problems we've found would have arisen in other
contexts as well; that's just where they happened so show up. Falsely
assuming that something is an integral constant-expression (which has
been the source of several of the bugs) could result in many other
problems as well.
I hope to look at this some more today.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14545
next prev parent reply other threads:[~2004-03-18 15:19 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 [this message]
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
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=20040318151912.29089.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: link
Be 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).