public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Jones <chrisjones@spin.net.au>
To: linux-kernel@vger.kernel.org
Cc: Cong Wang <xiyou.wangcong@gmail.com>
Subject: Re: gcc compiler modification to cater for new programming language
Date: Tue, 12 Jun 2012 17:06:03 +1000	[thread overview]
Message-ID: <4FD6EA5B.5030905@spin.net.au> (raw)
In-Reply-To: <CAM_iQpXyMhx5JszEew1O9ehQ0z-eOCZ_DjpdFPNJuKfVafcL3g@mail.gmail.com>

Cong Wang wrote:
> On Sun, Jun 10, 2012 at 10:02 AM, Chris Jones<chrisjones@spin.net.au>  wrote:
>> Is it possible to modify the source code of gcc to enable to compilation of
>> a completely new programming language, as yet unrecognized? How much of a
>> big job would I be looking at for such a task?
> Yeah, you need to write a gcc front-end for it.
>
>

Why would you suggest writing a front-end for it? I think you're wrong 
there as a front-end has nothing to do with the functionality of gcc. 
Explain to me why you would suggest this? Curious.

I am aware it is off-topic and have also brought it up on the gcc 
mailing list, thanks.


Regards

-- 
		Chris Jones

OpenSUSE Linux x86_64 (PC)|Android (Smartphone)|Windows x86 (Gaming!)
Kernel developer|Lead Developer of SDL|Lead Developer of Nest Linux|Gamer and Emulator nut|Web Services|Digital Imaging Services
Controllers: Rapier V2 Gaming mouse|Logitech Precision|PS3 controller|XB360 controller|Logitech Attack 3 j/stick
Emulators: Fusion|Gens|ZSNES|Project64|PCSX-R|Stella|WinVICE|WinUAE


  reply	other threads:[~2012-06-12  7:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-10  2:02 gcc compiler modification to cater for new programming language Chris Jones
2012-06-10  2:18 ` Cong Wang
2012-06-12  7:06   ` Chris Jones [this message]
2012-06-13 11:38     ` Bernd Petrovitsch
2012-06-10  8:31 ` Lukasz

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=4FD6EA5B.5030905@spin.net.au \
    --to=chrisjones@spin.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    /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