public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/52957] Missing suggestions on '=' and '==' confusion Date: Sat, 14 Apr 2012 12:43:00 -0000 [thread overview] Message-ID: <bug-52957-4-Gnf2RHa0Fg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52957-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52957 --- Comment #9 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-04-14 12:42:53 UTC --- (In reply to comment #8) > (In reply to comment #7) > > It is not *technically* hard. Anyone that knows C and a bit of C++ can fix > > hundreds (if you know C++ well and have a some experience with the C++ parser, > > There's the problem. I know C++ very well but don't know the front end well > enough to work on it, and don't have time to learn it. My main problem is that > everything is a void* so I have no idea what I can do with a given tree or what > type it is, so I just try something, it compiles (because there's no type > checking) so I run it then debug an ICE and continue by trial and error. > That's not productive. The bottleneck is not the bureaucracy for me. Thanks for sharing this. This broadens my perception of the issues contributors have with GCC. That said, it should be possible right now to use a C++ wrapper around tree, and use that in the C++ FE (and require C++ to bootstrap the C++ FE). What do you think about that? > > Indeed, but my point is that moving to C++ does little (in my opinion) to fix > > the infrastructure issues in GCC: dejagnu is awful, the wiki is unmaintained, > > Why should the wiki be maintained? If people want to add to it they can, why > should there be a maintainer? Well, the wiki is just a minor example, but it is awfully slow, nobody has administrator login (I can access as Daniel Berlin and ban users, but little more), and it is a unsupported version with known security issues.
next prev parent reply other threads:[~2012-04-14 12:43 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-12 22:03 [Bug c++/52957] New: " xinliangli at gmail dot com 2012-04-12 22:54 ` [Bug c++/52957] " pinskia at gcc dot gnu.org 2012-04-12 23:00 ` pinskia at gcc dot gnu.org 2012-04-12 23:08 ` manu at gcc dot gnu.org 2012-04-12 23:29 ` xinliangli at gmail dot com 2012-04-13 1:03 ` manu at gcc dot gnu.org 2012-04-13 5:02 ` xinliangli at gmail dot com 2012-04-14 12:10 ` manu at gcc dot gnu.org 2012-04-14 12:25 ` redi at gcc dot gnu.org 2012-04-14 12:43 ` manu at gcc dot gnu.org [this message] 2012-04-14 13:16 ` redi at gcc dot gnu.org 2012-04-15 4:10 ` xinliangli at gmail 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-52957-4-Gnf2RHa0Fg@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: linkBe 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).