public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bgreen@nas.nasa.gov
To: gcc-gnats@gcc.gnu.org
Subject: c++/5534: simple case that fails to link when using -frepo
Date: Tue, 29 Jan 2002 14:06:00 -0000	[thread overview]
Message-ID: <20020129215853.20222.qmail@sources.redhat.com> (raw)


>Number:         5534
>Category:       c++
>Synopsis:       simple case that fails to link when using -frepo
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jan 29 14:06:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Bryan Green
>Release:        3.0.3
>Organization:
>Environment:
Configured with: /home/bgreen/gcc/gcc-3.0.3/configure --prefix=/usr/local/gcc-3.0.3 --enable-threads=posix
Thread model: posix
gcc version 3.0.3
Linux 2.4.2-2smp-081701 #2 SMP i686 unknown
>Description:
The code submitted, when compiled with -frepo option,
causes numerous iterations of:
 collect: recompiling frepo.C
 collect: relinking
before failing with an undefined symbol.
The source to the problem is in the use of the unnamed
namespace for the structure definition.
The example code uses an stl list, but changing it to
a vector or deque shows equivalent results.
>How-To-Repeat:
#include <list>

namespace {
    struct data {
        int v;
    };
}

int main(int,char **)
{
    std::list<data> llist;
    return 0;
}
>Fix:

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


             reply	other threads:[~2002-01-29 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-29 14:06 bgreen [this message]
2002-07-06  7:42 lerdsuwa

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=20020129215853.20222.qmail@sources.redhat.com \
    --to=bgreen@nas.nasa.gov \
    --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).