From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: esoteric escape <manips88@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: GCC Front-ends?
Date: Sun, 02 Jun 2019 19:27:00 -0000 [thread overview]
Message-ID: <CAH6eHdTxDj8pW0g7O3T_sv5L5Li1c2RtifThDR6aYH_gnbm-RA@mail.gmail.com> (raw)
In-Reply-To: <CAFB=4tskw4nToAg61RecujgRwux+K8NqWWQs1343WPFbGP8-6g@mail.gmail.com>
On Sun, 2 Jun 2019 at 16:53, esoteric escape <manips88@gmail.com> wrote:
>
> I was reading this page: https://www.gnu.org/software/gcc/frontends.html
>
>
> > Currently the main GCC distribution contains front ends for C (gcc), C++
> > (g++), Objective C, Fortran, Ada (GNAT), Go, and D.
>
>
> Can you tell if gcc and g++ are front ends here? or are they complete
> compilers?
Does it matter?
How do you define a "complete compiler"?
Strictly speaking they're driver programs which can perform any step
of a compilation, from preprocessing to linking. But the different
drivers have different defaults, e.g. g++ defaults to running the C++
front end.
prev parent reply other threads:[~2019-06-02 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 15:53 esoteric escape
2019-06-02 19:27 ` 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=CAH6eHdTxDj8pW0g7O3T_sv5L5Li1c2RtifThDR6aYH_gnbm-RA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=manips88@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).