public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/24389] [4.0/4.1 Regression] tr1::unordered_map duplicate symbols (not extern?)
Date: Sat, 15 Oct 2005 20:32:00 -0000 [thread overview]
Message-ID: <20051015203213.1356.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24389-11529@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from pinskia at gcc dot gnu dot org 2005-10-15 20:32 -------
(In reply to comment #3)
> Note that I cannot reproduce with 4.0.0 and 4.0.1. I'm wondering whether is
> even
> more fallout from that static patch :( ... CC-ing Mark
It looks like it.
file1.c:
template<int dummy>
struct X
{
static const int n_primes = 256;
static const unsigned long primes[n_primes + 1];
};
template<int dummy>
const int X<dummy>::n_primes;
template<int dummy>
const unsigned long X<dummy>::primes[n_primes + 1] =
{ 0 };
const unsigned long *f(void){return &X<0>::primes[0];}
------------------------------
file2.c:
template<int dummy>
struct X
{
static const int n_primes = 256;
static const unsigned long primes[n_primes + 1];
};
template<int dummy>
const int X<dummy>::n_primes;
template<int dummy>
const unsigned long X<dummy>::primes[n_primes + 1] =
{ 0 };
const unsigned long *f1(void){return &X<0>::primes[0];}
int main(){}
-------
Compile and link, this fails.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pinskia at gcc dot gnu dot
| |org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Keywords| |wrong-code
Last reconfirmed|0000-00-00 00:00:00 |2005-10-15 20:32:13
date| |
Summary|tr1::unordered_map duplicate|[4.0/4.1 Regression]
|symbols (not extern?) |tr1::unordered_map duplicate
| |symbols (not extern?)
Target Milestone|--- |4.0.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24389
next prev parent reply other threads:[~2005-10-15 20:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 20:08 [Bug c++/24389] New: " maarten dot keijzer at gmail dot com
2005-10-15 20:15 ` [Bug c++/24389] " pinskia at gcc dot gnu dot org
2005-10-15 20:21 ` pinskia at gcc dot gnu dot org
2005-10-15 20:28 ` pcarlini at suse dot de
2005-10-15 20:32 ` pinskia at gcc dot gnu dot org [this message]
2005-10-15 20:42 ` [Bug c++/24389] [4.0/4.1 Regression] template variable not getting marked as weak pinskia at gcc dot gnu dot org
2005-10-15 20:45 ` pinskia at gcc dot gnu dot org
2005-10-16 20:19 ` mmitchel at gcc dot gnu dot org
2005-10-16 23:16 ` cvs-commit at gcc dot gnu dot org
2005-10-16 23:18 ` cvs-commit at gcc dot gnu dot org
2005-10-16 23:19 ` mmitchel at gcc dot gnu dot org
2005-10-16 23:19 ` cvs-commit 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=20051015203213.1356.qmail@sourceware.org \
--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: 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).