* how to see cpp(C preprocessor) output for a file?
@ 2021-12-14 8:23 ckim
2021-12-14 12:23 ` Rasmus Villemoes
0 siblings, 1 reply; 6+ messages in thread
From: ckim @ 2021-12-14 8:23 UTC (permalink / raw)
To: u-boot
Hello,
Is there any way I can see the cpp output of a file (for example
arch/arm/lib/vsprintf.c) after the build? (in the Makefile option for
example)
I see some code not executed though I think I have all the configs for the
lines.
Thanks!
Chan Kim
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: how to see cpp(C preprocessor) output for a file?
2021-12-14 8:23 how to see cpp(C preprocessor) output for a file? ckim
@ 2021-12-14 12:23 ` Rasmus Villemoes
2021-12-14 14:55 ` Chan Kim
2021-12-14 15:10 ` Chan Kim
0 siblings, 2 replies; 6+ messages in thread
From: Rasmus Villemoes @ 2021-12-14 12:23 UTC (permalink / raw)
To: ckim, u-boot
On 14/12/2021 09.23, ckim@etri.re.kr wrote:
> Hello,
>
> Is there any way I can see the cpp output of a file (for example
> arch/arm/lib/vsprintf.c) after the build? (in the Makefile option for
> example)
make foo/bar/baz.i
for any foo/bar/baz.c file which normally produces foo/bar/baz.o.
If you have a arch/bla/xyz.S file, you can similarly do
make arch/bla/xyz.s
to run the preprocessor on the .S code. And if you want to see the
assembly generated from a .c file,
make foo/bar/baz.s
also works.
Rasmus
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: how to see cpp(C preprocessor) output for a file?
2021-12-14 12:23 ` Rasmus Villemoes
@ 2021-12-14 14:55 ` Chan Kim
2021-12-14 15:10 ` Chan Kim
1 sibling, 0 replies; 6+ messages in thread
From: Chan Kim @ 2021-12-14 14:55 UTC (permalink / raw)
To: 'Rasmus Villemoes', u-boot
Wow that would be very helpful.
Thank you!
Chan
> -----Original Message-----
> From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
> Sent: Tuesday, December 14, 2021 9:23 PM
> To: ckim@etri.re.kr; u-boot@lists.denx.de
> Subject: Re: how to see cpp(C preprocessor) output for a file?
>
> On 14/12/2021 09.23, ckim@etri.re.kr wrote:
> > Hello,
> >
> > Is there any way I can see the cpp output of a file (for example
> > arch/arm/lib/vsprintf.c) after the build? (in the Makefile option for
> > example)
>
> make foo/bar/baz.i
>
> for any foo/bar/baz.c file which normally produces foo/bar/baz.o.
>
> If you have a arch/bla/xyz.S file, you can similarly do
>
> make arch/bla/xyz.s
>
> to run the preprocessor on the .S code. And if you want to see the
> assembly generated from a .c file,
>
> make foo/bar/baz.s
>
> also works.
>
> Rasmus
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: how to see cpp(C preprocessor) output for a file?
2021-12-14 12:23 ` Rasmus Villemoes
2021-12-14 14:55 ` Chan Kim
@ 2021-12-14 15:10 ` Chan Kim
2021-12-15 7:28 ` Rasmus Villemoes
1 sibling, 1 reply; 6+ messages in thread
From: Chan Kim @ 2021-12-14 15:10 UTC (permalink / raw)
To: 'Rasmus Villemoes', u-boot
But when I do
make CROSS_COMPILE=aarch64-none-elf- lib/tiny-printf.1
make: *** No rule to make target 'lib/tiny-printf.1'. Stop.
It doesn't work for me..
But make x/y/z.s works.
> -----Original Message-----
> From: Chan Kim <ckim@etri.re.kr>
> Sent: Tuesday, December 14, 2021 11:56 PM
> To: 'Rasmus Villemoes' <rasmus.villemoes@prevas.dk>; 'u-
> boot@lists.denx.de' <u-boot@lists.denx.de>
> Subject: RE: how to see cpp(C preprocessor) output for a file?
>
> Wow that would be very helpful.
> Thank you!
> Chan
>
> > -----Original Message-----
> > From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
> > Sent: Tuesday, December 14, 2021 9:23 PM
> > To: ckim@etri.re.kr; u-boot@lists.denx.de
> > Subject: Re: how to see cpp(C preprocessor) output for a file?
> >
> > On 14/12/2021 09.23, ckim@etri.re.kr wrote:
> > > Hello,
> > >
> > > Is there any way I can see the cpp output of a file (for example
> > > arch/arm/lib/vsprintf.c) after the build? (in the Makefile option
> > > for
> > > example)
> >
> > make foo/bar/baz.i
> >
> > for any foo/bar/baz.c file which normally produces foo/bar/baz.o.
> >
> > If you have a arch/bla/xyz.S file, you can similarly do
> >
> > make arch/bla/xyz.s
> >
> > to run the preprocessor on the .S code. And if you want to see the
> > assembly generated from a .c file,
> >
> > make foo/bar/baz.s
> >
> > also works.
> >
> > Rasmus
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: how to see cpp(C preprocessor) output for a file?
2021-12-14 15:10 ` Chan Kim
@ 2021-12-15 7:28 ` Rasmus Villemoes
2021-12-15 7:36 ` Chan Kim
0 siblings, 1 reply; 6+ messages in thread
From: Rasmus Villemoes @ 2021-12-15 7:28 UTC (permalink / raw)
To: Chan Kim, u-boot
On 14/12/2021 16.10, Chan Kim wrote:
> But when I do
> make CROSS_COMPILE=aarch64-none-elf- lib/tiny-printf.1
> make: *** No rule to make target 'lib/tiny-printf.1'. Stop.
letter i , not digit 1
Rasmus
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: how to see cpp(C preprocessor) output for a file?
2021-12-15 7:28 ` Rasmus Villemoes
@ 2021-12-15 7:36 ` Chan Kim
0 siblings, 0 replies; 6+ messages in thread
From: Chan Kim @ 2021-12-15 7:36 UTC (permalink / raw)
To: 'Rasmus Villemoes', u-boot
Ah, sorry, thanks!
Chan
> -----Original Message-----
> From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
> Sent: Wednesday, December 15, 2021 4:29 PM
> To: Chan Kim <ckim@etri.re.kr>; u-boot@lists.denx.de
> Subject: Re: how to see cpp(C preprocessor) output for a file?
>
> On 14/12/2021 16.10, Chan Kim wrote:
> > But when I do
> > make CROSS_COMPILE=aarch64-none-elf- lib/tiny-printf.1
> > make: *** No rule to make target 'lib/tiny-printf.1'. Stop.
>
> letter i , not digit 1
>
> Rasmus
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2021-12-15 7:36 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-12-14 8:23 how to see cpp(C preprocessor) output for a file? ckim
2021-12-14 12:23 ` Rasmus Villemoes
2021-12-14 14:55 ` Chan Kim
2021-12-14 15:10 ` Chan Kim
2021-12-15 7:28 ` Rasmus Villemoes
2021-12-15 7:36 ` Chan Kim
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox