public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: srishty bedi <bedisrishty07@gmail.com>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GSoC project idea
Date: Fri, 12 Mar 2021 17:43:50 +0000	[thread overview]
Message-ID: <CAH6eHdTWodBMTuvFqf8BGFaWNz9M799bTs3jRxkf2HZf_W_Uzw@mail.gmail.com> (raw)
In-Reply-To: <efae0234dd4ef01bcaa6cd4d049ef90d4c90bd74.camel@redhat.com>

On Fri, 12 Mar 2021 at 15:35, David Malcolm via Gcc wrote:
> On Thu, 2021-03-11 at 12:59 +0530, srishty bedi via Gcc wrote:
> > 1) I was thinking that whenever we run a code on gcc compiler its
> > beautify
> > feature doesn't work well it shifts the whole code to the left
> > instead so
> > thought of creating a good beautify feature as we have in vs code so
> > that
> > the code is easily understandable .
>
> I'm not sure what you mean by the "beautify feature" shifting "the
> whole code to the left".

I wonder if this is actually referring to a feature in an IDE which
happens to use GCC, maybe Code::Blocks of Dev-C++ or something.

> > 2) And we can also make the gcc compiler accessible to phones and
> > ipads so
> > that it may be compatible for touch devices also as it will be very
> > beneficial.
>
> It's possible to use GCC from such devices using the excellent
> godbolt.org website.

I find godbolt.org unusable on an Android phone, the UI just doesn't
fit on a small screen, but that's not a GCC problem.

      reply	other threads:[~2021-03-12 17:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11  7:29 srishty bedi
2021-03-12 14:33 ` David Malcolm
2021-03-12 17:43   ` Jonathan Wakely [this message]

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=CAH6eHdTWodBMTuvFqf8BGFaWNz9M799bTs3jRxkf2HZf_W_Uzw@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=bedisrishty07@gmail.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc@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).