public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org
To: Sylvain.Pion@sophia.inria.fr, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, ljrittle@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: libstdc++/6641: -D__USE_MALLOC doesn't link
Date: Mon, 13 May 2002 13:20:00 -0000	[thread overview]
Message-ID: <20020513202030.17964.qmail@sources.redhat.com> (raw)

Synopsis: -D__USE_MALLOC doesn't link

Responsible-Changed-From-To: unassigned->ljrittle
Responsible-Changed-By: ljrittle
Responsible-Changed-When: Mon May 13 13:20:30 2002
Responsible-Changed-Why:
    My pet issue.
State-Changed-From-To: open->closed
State-Changed-By: ljrittle
State-Changed-When: Mon May 13 13:20:30 2002
State-Changed-Why:
    You are correct in that this is a change from 2.95 and
    perhaps 3.0 (the only correct use of __USE_MALLOC was
    surely documented by the 3.0 release but it is possible
    that it still "worked").
    
    The libstdc++-v3 documentation now explicitly says that
    you must rebuild the entire library to define library
    implementation macros such as __USE_MALLOC.
    
    The use of macros in the library implementation name space,
    such as __USE_MALLOC, which may change internal
    implementation can violate the one-definition rule of C++.
    
    A patch that correctly handles all one-definition issues
    with such a macro might be accepted.  However, I will be
    holding my nose.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6641


             reply	other threads:[~2002-05-13 20:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-13 13:20 ljrittle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-12 17:16 Sylvain.Pion

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=20020513202030.17964.qmail@sources.redhat.com \
    --to=ljrittle@gcc.gnu.org \
    --cc=Sylvain.Pion@sophia.inria.fr \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).