Re: [PATCH 4/8] riscv: ensure RISC-V C model definitions are passed to static analyzers

On Thu, 17 Oct 2019 21:39:29 PDT (-0700), Paul Walmsley wrote: On Fri, 18 Oct 2019, Luc Van Oostenryck wrote: On Thu, Oct 17, 2019 at 05:49:25PM -0700, Paul Walmsley wrote: > Static analysis tools such as sparse don't set the RISC-V C model > preprocessor directives such as "__riscv_cmodel_meda

Re: [PATCH 4/8] riscv: ensure RISC-V C model definitions are passed to static analyzers

On Thu, Oct 17, 2019 at 09:39:29PM -0700, Paul Walmsley wrote: > On Fri, 18 Oct 2019, Luc Van Oostenryck wrote: > > On Thu, Oct 17, 2019 at 05:49:25PM -0700, Paul Walmsley wrote: > > > ifeq ($(CONFIG_CMODEL_MEDANY),y) > > > KBUILD_CFLAGS += -mcmodel=medany > > > + CHECKFLAGS += -D__riscv_cm

Re: [PATCH 4/8] riscv: ensure RISC-V C model definitions are passed to static analyzers

On Fri, 18 Oct 2019, Luc Van Oostenryck wrote: > On Thu, Oct 17, 2019 at 05:49:25PM -0700, Paul Walmsley wrote: > > Static analysis tools such as sparse don't set the RISC-V C model > > preprocessor directives such as "__riscv_cmodel_medany", set by the C > > compilers. This causes the static ana

Re: [PATCH 4/8] riscv: ensure RISC-V C model definitions are passed to static analyzers

On Thu, Oct 17, 2019 at 05:49:25PM -0700, Paul Walmsley wrote: > Static analysis tools such as sparse don't set the RISC-V C model > preprocessor directives such as "__riscv_cmodel_medany", set by the C > compilers. This causes the static analyzers to evaluate different > preprocessor paths than C

[PATCH 4/8] riscv: ensure RISC-V C model definitions are passed to static analyzers

Static analysis tools such as sparse don't set the RISC-V C model preprocessor directives such as "__riscv_cmodel_medany", set by the C compilers. This causes the static analyzers to evaluate different preprocessor paths than C compilers would. Fix this by defining the appropriate C model macros