public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "numerical.simulation@web.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/11080] New: g++ fails to compile Daixtrose Date: Tue, 03 Jun 2003 13:15:00 -0000 [thread overview] Message-ID: <20030603131536.11080.numerical.simulation@web.de> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11080 Summary: g++ fails to compile Daixtrose Product: gcc Version: 3.4 Status: UNCONFIRMED Severity: blocker Priority: P2 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: numerical.simulation@web.de CC: gcc-bugs@gcc.gnu.org,numerical.simulation@web.de Hi! Sorry for disregarding the bug-report-etiquette. I failed to reduce all this to small examples and the problems are much too numerous. After several months of trying different versions of g++ and after fiddling around with ICEs and probable workarounds I decide that the problems are to be reported in sum. The whole static const builtin and enum section is somewhat broken with g++, so I feel like it is time to report this here. - Daixtrose compiles fine with Intel C++ 7.1 using option -ansi, so it is unlikely You find too many errors in it. - Daixtrose stresses compiler's template support to maximum, so it is well designed as testsuite for any C++ compiler - Daixtrose is shipped with GNU-autotool-support so it is easy to set up to see g++ malperform - download cvs at cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/daixtrose login cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/daixtrose \ co daixtrose - visit http://daixtrose.sourceforge.net/ best regards, Markus ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2003-06-03 13:15 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-06-03 13:15 numerical.simulation@web.de [this message] 2003-06-03 13:59 ` [Bug c++/11080] " numerical.simulation@web.de
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=20030603131536.11080.numerical.simulation@web.de \ --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).