From: Xi Ruoyao <xry111@mengyan1223.wang>
To: RICHU NORMAN <richunorman@cusat.ac.in>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Printing statements from compiler
Date: Tue, 05 Apr 2022 03:18:39 +0800 [thread overview]
Message-ID: <60cdb5bc954bf8917c4f7829432abde4d33b3f67.camel@mengyan1223.wang> (raw)
In-Reply-To: <CAPhpueXUykvN3NKJ+ZC6MuywHk0kLBc9jdbr3NLkC1aLQUGfmw@mail.gmail.com>
On Mon, 2022-04-04 at 23:39 +0530, RICHU NORMAN wrote:
> Hi,
> I am a beginner in gcc development
> 1. Is there a way to use print statements in gcc to track the flow or debug
> the code?
AFAIK you can call fprintf to print to stderr. But it's not a "print
statement": there is no such concept in C++.
> 2. After each edit do we use 'make' to build the gcc?
Yes.
> 3. Is there a way to individually compile the edited files, as using 'make'
> takes more time?
Why would it take more time? make tracks the timestamps of files and
only recompile a file when it's necessary.
--
Xi Ruoyao <xry111@mengyan1223.wang>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-04-04 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 18:09 RICHU NORMAN
2022-04-04 19:18 ` Xi Ruoyao [this message]
2022-04-04 19:57 ` RICHU NORMAN
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=60cdb5bc954bf8917c4f7829432abde4d33b3f67.camel@mengyan1223.wang \
--to=xry111@mengyan1223.wang \
--cc=gcc-help@gcc.gnu.org \
--cc=richunorman@cusat.ac.in \
/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).