public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/28080] header dependencies
Date: Sun, 04 Mar 2007 00:20:00 -0000	[thread overview]
Message-ID: <20070304002039.13810.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28080-8082@http.gcc.gnu.org/bugzilla/>



------- Comment #20 from paolo at gcc dot gnu dot org  2007-03-04 00:20 -------
Subject: Bug 28080

Author: paolo
Date: Sun Mar  4 00:20:26 2007
New Revision: 122518

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=122518
Log:
2007-03-03  Paolo Carlini  <pcarlini@suse.de>

        PR libstdc++/28080 (partial)
        * include/tr1/functional: Split out hash bits to...
        * include/tr1/functional_hash.h: ...here.
        * include/Makefile.am: Add.
        * include/tr1/unordered_set: Include the latter instead.
        * include/tr1/unordered_map: Likewise.
        * include/Makefile.in: Regenerate.

        * include/tr1/utility (get(std::pair<>&), get(const std::pair<>&)):
        Mark inline.

Modified:
    branches/gcc-4_2-branch/libstdc++-v3/ChangeLog
    branches/gcc-4_2-branch/libstdc++-v3/include/Makefile.am
    branches/gcc-4_2-branch/libstdc++-v3/include/Makefile.in
    branches/gcc-4_2-branch/libstdc++-v3/include/tr1/functional
    branches/gcc-4_2-branch/libstdc++-v3/include/tr1/unordered_map
    branches/gcc-4_2-branch/libstdc++-v3/include/tr1/unordered_set
    branches/gcc-4_2-branch/libstdc++-v3/include/tr1/utility


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28080


  parent reply	other threads:[~2007-03-04  0:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19  7:50 [Bug libstdc++/28080] New: " Woebbeking at web dot de
2006-06-19 10:15 ` [Bug libstdc++/28080] " pcarlini at suse dot de
2006-06-19 16:57 ` pinskia at gcc dot gnu dot org
2006-06-19 17:07 ` pinskia at gcc dot gnu dot org
2006-06-19 18:05 ` Woebbeking at web dot de
2006-06-19 18:11 ` pcarlini at suse dot de
2006-06-23  5:00 ` pinskia at gcc dot gnu dot org
2006-06-23 15:40 ` chris at bubblescope dot net
2006-06-23 16:40 ` gdr at integrable-solutions dot net
2006-06-23 17:03 ` chris at bubblescope dot net
2007-02-17 17:34 ` pcarlini at suse dot de
2007-02-17 20:42 ` Woebbeking at web dot de
2007-02-18 11:33 ` paolo at gcc dot gnu dot org
2007-02-20 18:16 ` bkoz at gcc dot gnu dot org
2007-02-20 21:23 ` paolo at gcc dot gnu dot org
2007-02-24 10:15 ` pcarlini at suse dot de
2007-02-26  9:37 ` paolo at gcc dot gnu dot org
2007-02-27 17:48 ` paolo at gcc dot gnu dot org
2007-03-02 16:22 ` paolo at gcc dot gnu dot org
2007-03-03 10:29 ` paolo at gcc dot gnu dot org
2007-03-04  0:20 ` paolo at gcc dot gnu dot org [this message]
2007-03-04  0:23 ` paolo at gcc dot gnu dot org
2007-03-06 17:43 ` paolo at gcc dot gnu dot org
2007-03-07 22:59 ` paolo at gcc dot gnu dot org
2007-03-10 20:30 ` paolo at gcc dot gnu dot org
2007-03-11 12:04 ` paolo at gcc dot gnu dot org
2007-03-11 12:07 ` pcarlini at suse dot de

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=20070304002039.13810.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).