>
> Sure. But in fact I was not able to create the .ll from .S and neither
> create the .s
> from the .S in some assembly files on kernel. Do you know how it works?
make arch/x86/kernel/preempt.s
Works for me.
Something broke in your setup?
Sam
--
To unsubscribe from this list: send
1) Can we drop the test for $(COMPILER) here?
Yes.
2) And help section should be updated to list .ll too.
I will be adding it too.
3) This chunk belongs together with the other chunk.
There is no reason to separate .S => .ll and .c => .ll rules.
Sure. But in fact I was not able to create the
1) Can we drop the test for $(COMPILER) here?
Yes.
2) And help section should be updated to list .ll too.
I will be adding it too.
3) This chunk belongs together with the other chunk.
There is no reason to separate .S = .ll and .c = .ll rules.
Sure. But in fact I was not able to create the
Sure. But in fact I was not able to create the .ll from .S and neither
create the .s
from the .S in some assembly files on kernel. Do you know how it works?
make arch/x86/kernel/preempt.s
Works for me.
Something broke in your setup?
Sam
--
To unsubscribe from this list: send the
On Sun, Jul 20, 2014 at 11:04:58PM +0200, Sam Ravnborg wrote:
> > >
> > > +ifeq ($(COMPILER),clang)
> > > +quiet_cmd_cc_ll_c = CC $(quiet_modtag) $@
> > > +cmd_cc_ll_c = $(CC) $(c_flags) $(DISABLE_LTO) -fverbose-asm
> > > -emit-llvm -S -o $@ $<
> >
> > Can we drop the test for COMPILER
> >
> > +ifeq ($(COMPILER),clang)
> > +quiet_cmd_cc_ll_c = CC $(quiet_modtag) $@
> > +cmd_cc_ll_c = $(CC) $(c_flags) $(DISABLE_LTO) -fverbose-asm
> > -emit-llvm -S -o $@ $<
>
> Can we drop the test for COMPILER here too?
> Do -fverbose-asm make sense when generating .ll files?
> It
On Fri, Jul 18, 2014 at 10:34:37PM -0300, Vinícius Tinti wrote:
> Allows kbuild to generate LLVM bitcode files with the .ll extension when
> building with Clang.
>
> # c code
> CC=clang make kernel/pid.ll
>
> # asm code
> CC=clang make arch/arm/kernel/calls.ll
>
> Signed-off-by:
On Fri, Jul 18, 2014 at 10:34:37PM -0300, Vinícius Tinti wrote:
Allows kbuild to generate LLVM bitcode files with the .ll extension when
building with Clang.
# c code
CC=clang make kernel/pid.ll
# asm code
CC=clang make arch/arm/kernel/calls.ll
Signed-off-by: Vinícius Tinti
+ifeq ($(COMPILER),clang)
+quiet_cmd_cc_ll_c = CC $(quiet_modtag) $@
+cmd_cc_ll_c = $(CC) $(c_flags) $(DISABLE_LTO) -fverbose-asm
-emit-llvm -S -o $@ $
Can we drop the test for COMPILER here too?
Do -fverbose-asm make sense when generating .ll files?
It looks like a
On Sun, Jul 20, 2014 at 11:04:58PM +0200, Sam Ravnborg wrote:
+ifeq ($(COMPILER),clang)
+quiet_cmd_cc_ll_c = CC $(quiet_modtag) $@
+cmd_cc_ll_c = $(CC) $(c_flags) $(DISABLE_LTO) -fverbose-asm
-emit-llvm -S -o $@ $
Can we drop the test for COMPILER here too?
Do
Allows kbuild to generate LLVM bitcode files with the .ll extension when
building with Clang.
# c code
CC=clang make kernel/pid.ll
# asm code
CC=clang make arch/arm/kernel/calls.ll
Signed-off-by: Vinícius Tinti
Signed-off-by: Behan Webster
---
Makefile | 7 +++
Allows kbuild to generate LLVM bitcode files with the .ll extension when
building with Clang.
# c code
CC=clang make kernel/pid.ll
# asm code
CC=clang make arch/arm/kernel/calls.ll
Signed-off-by: Vinícius Tinti viniciusti...@gmail.com
Signed-off-by: Behan Webster
12 matches
Mail list logo