public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andreas Rottmann <a.rottmann@gmx.at> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7929: ICE on struct initialization Date: Fri, 11 Oct 2002 01:36:00 -0000 [thread overview] Message-ID: <20021011083601.9789.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7929; it has been noted by GNATS. From: Andreas Rottmann <a.rottmann@gmx.at> To: Joe Buck <jbuck@synopsys.com> Cc: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: c++/7929: ICE on struct initialization Date: 11 Oct 2002 10:27:41 +0200 Joe Buck <jbuck@synopsys.com> writes: > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7929 > > I'm not seeing this error either with the FSF 3.2 release or with the > CVS 3.2 > branch as of today. The test case I'm using is > > ----------- > #include <string> > > struct Bar > { > std::string str; > }; > > int main() > { > Bar bar = { "hello" }; > } > ---------- > There is no crash or diagnostic. Perhaps a bug was introduced and > then fixed on > the branch sometime between Aug 30 and now, or perhaps a local Debian > patch is > responsible. Any objection to closing the bug? > > I just upgraded my Debian packages (to the latest version from unstable) and the bug has vanished! Regards, Andy -- Andreas Rottmann | Dru@ICQ | 118634484@ICQ | a.rottmann@gmx.at http://www.8ung.at/rotty | GnuPG Key: http://www.8ung.at/rotty/gpg.asc Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
next reply other threads:[~2002-10-11 8:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-11 1:36 Andreas Rottmann [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-11 11:01 jbuck 2002-10-10 17:26 Joe Buck 2002-09-30 4:56 Andreas Rottmann 2002-09-30 2:46 Reichelt 2002-09-16 6:46 a.rottmann
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=20021011083601.9789.qmail@sources.redhat.com \ --to=a.rottmann@gmx.at \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).