public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/53489] suggest a feature for gcc.
Date: Fri, 25 May 2012 17:14:00 -0000 [thread overview]
Message-ID: <bug-53489-4-tfOPuwXbJ5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53489-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53489
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2012-05-25
Ever Confirmed|0 |1
Severity|normal |enhancement
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-05-25 16:21:45 UTC ---
(In reply to comment #0)
> It will be nice if it can add in a website like in sourceforge or google code,
> they have a nice table for bugs and features.
GCC already has a website and a bug database (you used it to submit this
request!) What do you mean?
>
> I see GCC is support a Java language and it combine with GCJ
> http://gcc.gnu.org/java/
>
> why not to do the same with C#?
What do you mean by "the same"?
If the mono team wanted to contribute their compiler to GCC they would do.
You'll need to be clearer what you are suggesting, as noone is going to work on
a vague suggestion that they can't understand. If you can't even be bothered
to escribe your idea properly why should anyone be bothered to work on it?
next prev parent reply other threads:[~2012-05-25 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 16:09 [Bug other/53489] New: " tal.regev at gmail dot com
2012-05-25 17:14 ` redi at gcc dot gnu.org [this message]
2013-01-08 10:59 ` [Bug other/53489] " tal.regev at gmail dot com
2013-11-09 23:08 ` pinskia at gcc dot gnu.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=bug-53489-4-tfOPuwXbJ5@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).