From: Xi Ruoyao <xry111@mengyan1223.wang>
To: RICHU NORMAN <richunorman@cusat.ac.in>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: To display log comments on console or file
Date: Mon, 18 Apr 2022 20:22:26 +0800 [thread overview]
Message-ID: <357358469dccda1c1bb440f5943fe4702e0cdb29.camel@mengyan1223.wang> (raw)
In-Reply-To: <CAPhpueWPU40pTHh6Dbofi2-Lm7xv4YpzsDaLL_zuX1PgpDxcaA@mail.gmail.com>
On Mon, 2022-04-18 at 16:02 +0530, RICHU NORMAN wrote:
> Hi,
> Thanking you in advance.
> I am a beginner working on implementing new instructions in gcc. I am
> unable to display log comments on console or file. We want to put log
> comments to know if compilation entered certain functions that we edited.
> Either we should be able to print on console or print in a file. This would
> help us track the flow of execution as well.
You can use fprintf(stderr, ...) to output messages. But why not just
use a debugger?
--
Xi Ruoyao <xry111@mengyan1223.wang>
School of Aerospace Science and Technology, Xidian University
prev parent reply other threads:[~2022-04-18 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 10:32 RICHU NORMAN
2022-04-18 12:22 ` Xi Ruoyao [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=357358469dccda1c1bb440f5943fe4702e0cdb29.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).