Re: c preprocessor output: first four lines

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "Roman B." <rbyshko@xxxxxxxxx>
Subject: Re: c preprocessor output: first four lines
From: Ian Lance Taylor <iant@xxxxxxxxxx>
Date: Mon, 03 Oct 2011 13:33:29 -0700
Cc: gcc-help@xxxxxxxxxxx
In-reply-to: <CAMXmWB=tZVeXU9aCvei_9YWs4ikOx=2UoU47jPkXfOUs_yPC3Q@mail.gmail.com> (Roman B.'s message of "Sun, 2 Oct 2011 21:05:41 +0200")
References: <CAMXmWB=tZVeXU9aCvei_9YWs4ikOx=2UoU47jPkXfOUs_yPC3Q@mail.gmail.com>
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)

"Roman B." <rbyshko@xxxxxxxxx> writes:

> # 1 "file.c"
> # 1 "<built-in>"
> # 1 "<command-line>"
> # 1 "file.c"
>
> Where as words are self-explanatory I cannot understand the meaning in
> the whole. I could not find any explanation in the documentation also.

http://gcc.gnu.org/onlinedocs/gcc-4.6.1/cpp/Preprocessor-Output.html

Ian

Follow-Ups:
- Re: c preprocessor output: first four lines
  - From: Roman B.

References:
- c preprocessor output: first four lines
  - From: Roman B.

Prev by Date: Alignment Issue
Next by Date: Re: Alignment Issue
Previous by thread: Re: c preprocessor output: first four lines
Next by thread: Re: c preprocessor output: first four lines
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux