public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sander at mi dot fu-berlin dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/29483] New: Undefined reference when using negated static const double Date: Mon, 16 Oct 2006 15:49:00 -0000 [thread overview] Message-ID: <bug-29483-12759@http.gcc.gnu.org/bugzilla/> (raw) The following little testcase class Foo { public: void bar() const; static const double TOL = 1e-14; }; void Foo::bar() const { double tol = -TOL; } int main(){} produces the error message sander@haile:~/dune_projects/uggridtest$ g++ test.cc /tmp/cco39MFe.o: In function `Foo::bar() const': test.cc:(.text+0x8): undefined reference to `Foo::TOL' collect2: ld returned 1 exit status when compiled with sander@haile:~/dune_projects/uggridtest$ g++ --version g++ (GCC) 4.1.2 20060901 (prerelease) (Debian 4.1.1-13) It compiles with 2.95 and 3.3, it does not compile with 3.4. The error message goes away when the minus sign in front of TOL is removed. -- Summary: Undefined reference when using negated static const double Product: gcc Version: 4.1.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: sander at mi dot fu-berlin dot de http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29483
next reply other threads:[~2006-10-16 15:49 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-16 15:49 sander at mi dot fu-berlin dot de [this message] 2006-10-16 15:54 ` [Bug c++/29483] " pinskia at gcc dot gnu dot org 2006-10-30 12:29 ` rguenth at gcc dot gnu dot org 2006-10-30 12:29 ` rguenth 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-29483-12759@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).