public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ruschein@infomine.ucr.edu To: gcc-gnats@gcc.gnu.org Subject: c++/7373: g++ 3.0 and 3.1 miscompile certain uses of the ternary operator Date: Mon, 22 Jul 2002 09:06:00 -0000 [thread overview] Message-ID: <20020722160235.30989.qmail@sources.redhat.com> (raw) >Number: 7373 >Category: c++ >Synopsis: g++ 3.0 and 3.1 miscompile certain uses of the ternary operator >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Jul 22 09:06:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Dr. Johannes Ruscheinski >Release: gcc versions 3.0.4 and 3.1.1-0pre3 >Organization: >Environment: Debian sid on 80x86, Linux 2.4.19-pre8 >Description: Comiling the supplied tiny test program (g++-3.0 test.cc) results in the following linker errors (binutils version 2.12.90.0.14-1): /tmp/ccKTBRxn.o: In function `main': /tmp/ccKTBRxn.o(.text+0x17): undefined reference to `Fred::BIT1' /tmp/ccKTBRxn.o(.text+0x21): undefined reference to `Fred::BIT2' collect2: ld returned 1 exit status >How-To-Repeat: Compile the test program with *no* command line flags and version 3.0.4 (Debian 3.0.4-12 or 3.1.1-0pre3) and observe the linker error messages. >Fix: Unknown. Sorry I'm an application programmer and don't know anything about the compiler internals. I'd love to learn about it though :-) >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/x-c++src; name="test.cc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="test.cc" c3RydWN0IEZyZWQgewoJc3RhdGljIGNvbnN0IHVuc2lnbmVkIEJJVDEgPSAxOwoJc3RhdGljIGNv bnN0IHVuc2lnbmVkIEJJVDIgPSAyOwp9OwoKCmludCBtYWluKGludCBhcmdjLCBjaGFyICphcmd2 W10pCnsKCXVuc2lnbmVkIG1hc2soYXJnYyA/IEZyZWQ6OkJJVDEgOiBGcmVkOjpCSVQyKTsKfQo=
next reply other threads:[~2002-07-22 16:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-22 9:06 ruschein [this message] 2002-07-22 14:12 nathan 2002-07-22 14:36 Johannes Ruscheinski
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=20020722160235.30989.qmail@sources.redhat.com \ --to=ruschein@infomine.ucr.edu \ --cc=gcc-gnats@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).