public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Alper G." <ozgurgezc@gmail.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Martin Jambor <mjambor@suse.cz>, GCC Development <gcc@gcc.gnu.org>
Subject: Re: Google GSOC Idea
Date: Tue, 5 Jan 2021 23:16:30 +0300	[thread overview]
Message-ID: <CACXJTsi2M+C-kjYScOXge83m0UhsemPOsPjVUn6zaRWC9oQLgQ@mail.gmail.com> (raw)
In-Reply-To: <CAGWvny=ykFJ1q34bUd3xqf6jEYYyU7aAQE6VNxz=COAnRrGSZg@mail.gmail.com>

We have a pre-implementation trial, although it is not very extensive.
We intend to develop this during gsoc and take it forward in a planned
manner.



David Edelsohn <dje.gcc@gmail.com>, 5 Oca 2021 Sal, 22:45 tarihinde şunu
yazdı:

> Are you trying to propose a JavaScript / TypeScript front-end and
> associated runtime for GCC?
>
> I don't believe that anyone would object to that.  It probably is much
> too ambitious for a GSoC project.  You could propose a subset as a
> GSoC project.
>
> It's unclear if you already have a preliminary implementation and want
> to incrementally continue it, like a Hackathon, as part of GSoC.
>
> Thanks, David
>
> On Tue, Jan 5, 2021 at 2:34 PM Alper G. via Gcc <gcc@gcc.gnu.org> wrote:
> >
> > I wanted to talk about a gcc front-end with the syntax js / ts, which is
> > ahead-of-time. The standard library will also contain basic functions
> that
> > will enable the use of several basic frameworks that can be used in
> > standard output. It was an e-mail that I could not fully explain because
> I
> > tried to correct the text a few times, I'm sorry :) We are a group of
> > several people who have already worked on compiler design and we thought
> of
> > applying this idea under the name gcc.
> >
> > Martin Jambor <mjambor@suse.cz>, 4 Oca 2021 Pzt, 17:37 tarihinde şunu
> yazdı:
> >
> > > Hi,
> > >
> > > On Sun, Dec 27 2020, Alper G. via Gcc wrote:
> > > > Hello, I am waiting for your suggestions and evaluations about an
> idea
> > > that
> > > > I am thinking about applying to this year's event of google gsoc. In
> > > short,
> > > > I can say about myself that I am an engineering student and worked on
> > > > compilers as well as several different fields. Nowadays, we see that
> > > > scripting languages such as javascript / typescript are more than
> just a
> > > > client-side language in the browser. In order to develop
> applications on
> > > > desktop and mobile devices, there are alternatives such as electron
> that
> > > > contain chromium and nodejs, have multi-disk-size requirements and
> cannot
> > > > be packaged statically before runtime, such as react-native. In
> order to
> > > > overcome such problems, it is necessary to create the ahead-of-time
> > > > compilation, which we are familiar with such as c / c ++, according
> to
> > > this
> > > > syntax and standards, and to call the graphics libraries and system
> calls
> > > > directly from within js. Therefore, I want to create a subset of gcc
> that
> > > > can be statically compiled and contains the ecmascript standards
> required
> > > > to run common js frameworks native. What are your comments on this
> > > > idea?
> > >
> > > I'm afraid I don't understand it at all.  Making GCC "run common js
> > > frameworks" makes very little sense to me.  Are you proposing some kind
> > > of JavaScript Front-end (which is not a JIT)?
> > >
> > > > What can we say about the acceptability for gsoc?
> > >
> > > Well, unfortunately I can say only that I do not understand it.  If it
> > > is the JavaScript Front-end, the project would too big for a GSoC, by
> > > orders of magnitude, even if severely reduced in scope.
> > >
> > > Martin
> > >
>

  reply	other threads:[~2021-01-05 20:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-27 12:44 Alper G.
2021-01-04 14:37 ` Martin Jambor
2021-01-05 19:32   ` Alper G.
2021-01-05 19:45     ` David Edelsohn
2021-01-05 20:16       ` Alper G. [this message]
2021-01-11 17:17         ` Google GSOC Idea (JS/TS FE) Martin Jambor

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=CACXJTsi2M+C-kjYScOXge83m0UhsemPOsPjVUn6zaRWC9oQLgQ@mail.gmail.com \
    --to=ozgurgezc@gmail.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mjambor@suse.cz \
    /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).