public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dej@inode.org
To: gcc-gnats@gcc.gnu.org
Subject: c++/10483: Spurious reference created to integer constant in ternary op
Date: Thu, 24 Apr 2003 16:16:00 -0000	[thread overview]
Message-ID: <20030424160942.15308.qmail@sources.redhat.com> (raw)


>Number:         10483
>Category:       c++
>Synopsis:       Spurious reference created to integer constant in ternary op
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Apr 24 16:16:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     dej@inode.org
>Release:        gcc version 2.95.3 20010315 (release) [FreeBSD]
>Organization:
>Environment:
FreeBSD slam.inode.org 4.6-RELEASE FreeBSD 4.6-RELEASE #2: Sun Oct  6 18:46:44 EDT 2002     dej@slam.inode.org:/usr/src/sys/compile/SLAM  i386
>Description:
Given the following source:

using namespace std;

struct Foo {
    static const int BAR = 1;
    static const int BAZ = 2;
};


int main(int argc, char *argv[])
{
    int c = argc ? Foo::BAR : Foo::BAZ;
    return 0;
}

and invoked like:

/usr/local/gcc322/bin/gcc test.cpp -o test -lstdc++

I obtain:
/var/tmp//ccu6NK1Z.o: In function `main':
/var/tmp//ccu6NK1Z.o(.text+0x17): undefined reference to `Foo::BAR'
/var/tmp//ccu6NK1Z.o(.text+0x21): undefined reference to `Foo::BAZ'

Since BAR and BAZ are static integer constants, they should not be generating linker references.  This happens only with the ternary operator; the equivalent if/else code does not produce the problem.
>How-To-Repeat:
See description.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-04-24 16:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24 16:16 dej [this message]
2003-04-24 16:23 nathan

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=20030424160942.15308.qmail@sources.redhat.com \
    --to=dej@inode.org \
    --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: link
Be 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).