public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tim at klingt dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/38670] New: [4.4 regression] g++ rejects valid c++ code Date: Tue, 30 Dec 2008 10:43:00 -0000 [thread overview] Message-ID: <bug-38670-12873@http.gcc.gnu.org/bugzilla/> (raw) (sorry for not reducing the test case) gcc-4.4 fails to compile some of my code, which compiled fine with (at least) 4.2 and 4.3. the preprocessed source is attached. gcc version: Using built-in specs. Target: x86_64-linux-gnu Configured with: ../gcc-4.4-20081226/configure -v --with-bugurl=file:///usr/share/doc/gcc-snapshot/README.Bugs --enable-languages=c,c++ --prefix=/usr/local/lib/gcc-snapshot --enable-shared --with-system-zlib --disable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-gtk-cairo --disable-plugin --enable-objc-gc --enable-mpfr --disable-werror --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.4.0 20081226 (experimental) (GCC) -- Summary: [4.4 regression] g++ rejects valid c++ code Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: tim at klingt dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38670
next reply other threads:[~2008-12-30 10:43 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-30 10:43 tim at klingt dot org [this message] 2008-12-30 10:43 ` [Bug c++/38670] " tim at klingt dot org 2008-12-30 10:57 ` tim at klingt dot org 2008-12-30 10:59 ` tim at klingt dot org 2008-12-30 11:14 ` jakub at gcc dot gnu dot org
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=bug-38670-12873@http.gcc.gnu.org/bugzilla/ \ --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).