public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/10196: [3.3/3.4 regression] Compile time regression with inlining Date: Mon, 07 Apr 2003 15:06:00 -0000 [thread overview] Message-ID: <20030407150600.31427.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/10196; it has been noted by GNATS. From: Steven Bosscher <s.bosscher@student.tudelft.nl> To: gcc-gnats@gcc.gnu.org, rguenth@tat.physik.uni-tuebingen.de, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org Cc: Subject: Re: optimization/10196: [3.3/3.4 regression] Compile time regression with inlining Date: Mon, 07 Apr 2003 17:00:43 +0200 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10196 I wanted to profile the testcase but with today's CVS it does not compile for me at all: In file included from /home/rguenth/ix86/gcc3.3/include/c++/3.3/bits/codecvt.h:334, from /home/rguenth/ix86/gcc3.3/include/c++/3.3/bits/locale_facets.h:528, from /home/rguenth/ix86/gcc3.3/include/c++/3.3/bits/basic_ios.h:44, from /home/rguenth/ix86/gcc3.3/include/c++/3.3/ios:51, from /home/rguenth/ix86/gcc3.3/include/c++/3.3/ostream:45, from /home/rguenth/ix86/gcc3.3/include/c++/3.3/iterator:70, from /net/bellatrix/home/rguenth/src/pooma-work/r2/src/Domain/DomainIterator.h:51, from /net/bellatrix/home/rguenth/src/pooma-work/r2/src/Domain/DomainBase.h:63, from /net/bellatrix/home/rguenth/src/pooma-work/r2/src/Domain/Domain.h:65, from /net/bellatrix/home/rguenth/src/pooma-work/r2/src/Domain/Interval.h:59, from /net/bellatrix/home/rguenth/src/pooma-work/r2/src/Layout/INode.h:52, from /net/bellatrix/home/rguenth/src/pooma-work/r2/src/Layout/LayoutBase.h:56, from /net/bellatrix/home/rguenth/src/pooma-work/r2/src/Layout/DynamicLayout.h:60, from /net/bellatrix/home/rguenth/src/pooma-work/r2/src/Layout/DynamicLayout.cmpl.cpp:35: /home/rguenth/ix86/gcc3.3/include/c++/3.3/i686-pc-linux-gnu/bits/codecvt_specializations.h: In member function `virtual std::codecvt_base::result std::codecvt<_InternT, _ExternT, std::__enc_traits>::do_out(std::__enc_traits&, const _InternT*, const _InternT*, const _InternT*&, _ExternT*, _ExternT*, _ExternT*&) const': /home/rguenth/ix86/gcc3.3/include/c++/3.3/i686-pc-linux-gnu/bits/codecvt_specializations.h:263: error: ` error' has not been declared /home/rguenth/ix86/gcc3.3/include/c++/3.3/i686-pc-linux-gnu/bits/codecvt_specializations.h:307: error: ` ok' has not been declared /home/rguenth/ix86/gcc3.3/include/c++/3.3/i686-pc-linux-gnu/bits/codecvt_specializations.h:315: error: ` partial' has not been declared /home/rguenth/ix86/gcc3.3/include/c++/3.3/i686-pc-linux-gnu/bits/codecvt_specializations.h:318: error: ` error' has not been declared Etc...
next reply other threads:[~2003-04-07 15:06 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-07 15:06 Steven Bosscher [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-23 15:46 mmitchel 2003-04-08 14:46 Richard Guenther 2003-04-08 11:06 Steven Bosscher 2003-04-08 11:06 Richard Guenther 2003-04-08 9:56 Steven Bosscher 2003-03-24 18:26 mmitchel 2003-03-24 13:46 Richard Guenther 2003-03-24 8:36 mmitchel
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=20030407150600.31427.qmail@sources.redhat.com \ --to=s.bosscher@student.tudelft.nl \ --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).