From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mengyan1223.wang (mengyan1223.wang [89.208.246.23]) by sourceware.org (Postfix) with ESMTPS id 9582D3858D28 for ; Mon, 18 Apr 2022 12:22:29 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 9582D3858D28 Received: from localhost.localdomain (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-384)) (Client did not present a certificate) (Authenticated sender: xry111@mengyan1223.wang) by mengyan1223.wang (Postfix) with ESMTPSA id E0F76659A7; Mon, 18 Apr 2022 08:22:27 -0400 (EDT) Message-ID: <357358469dccda1c1bb440f5943fe4702e0cdb29.camel@mengyan1223.wang> Subject: Re: To display log comments on console or file From: Xi Ruoyao To: RICHU NORMAN , gcc-help Date: Mon, 18 Apr 2022 20:22:26 +0800 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.0 MIME-Version: 1.0 X-Spam-Status: No, score=-3031.8 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, JMQ_SPF_NEUTRAL, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-help@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-help mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2022 12:22:31 -0000 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 wou= ld > help us track the flow of execution as well. You can use fprintf(stderr, ...) to output messages. But why not just use a debugger? --=20 Xi Ruoyao School of Aerospace Science and Technology, Xidian University