public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/51699] Clang refuses to compile ext/rope citing scope resolution issues
Date: Thu, 29 Dec 2011 10:17:00 -0000	[thread overview]
Message-ID: <bug-51699-4-sqTIvIel4Y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51699-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-12-29 10:15:31 UTC ---
Unfortunately rope is largely unmaintained. Assuming these issues are easy to
handle somebody with access to clang should do the work.

Note: before touching the library at all, the C++ issue should be analyzed in
detail, make sure we have a Bugzilla open for it, etc, it doesn't really make
sense blindly "fixing" the library for the benefit of another compiler without
being able to double check what is going on with GCC. Is there a Bugzilla open
for the C++ front-end issue? Otherwise, can you please open one?


  reply	other threads:[~2011-12-29 10:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-29  6:01 [Bug libstdc++/51699] New: " fedorabugmail at yahoo dot com
2011-12-29 10:17 ` paolo.carlini at oracle dot com [this message]
2011-12-29 14:47 ` [Bug libstdc++/51699] " redi at gcc dot gnu.org
2011-12-29 14:47 ` redi at gcc dot gnu.org
2011-12-29 15:08 ` paolo.carlini at oracle dot com
2011-12-29 15:09 ` redi at gcc dot gnu.org
2011-12-29 15:31 ` paolo.carlini at oracle dot com

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=bug-51699-4-sqTIvIel4Y@http.gcc.gnu.org/bugzilla/ \
    --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).