Linux Sparse

• Thread Index

• Re: Fwd: dependency tee from c parser entities downto token
  • From: Konrad Eisele <eiselekd@xxxxxxxxx>
• Re: [PATCH] Updated __nocast vs __bitwise documentation
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Fwd: dependency tee from c parser entities downto token
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] Updated __nocast vs __bitwise documentation
  • From: Shakthi Kannan <shakthimaan@xxxxxxxxx>
• Re: [PATCH] Updated __nocast vs __bitwise documentation
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] simplify: conservative handling of casts with pointers
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Fwd: dependency tee from c parser entities downto token
  • From: Konrad Eisele <konrad@xxxxxxxxxxx>
• Re: Fwd: dependency tee from c parser entities downto token
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Fwd: dependency tee from c parser entities downto token
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH] Updated __nocast vs __bitwise documentation
  • From: Shakthi Kannan <shakthimaan@xxxxxxxxx>
• Re: Fwd: dependency tee from c parser entities downto token
  • From: Konrad Eisele <konrad@xxxxxxxxxxx>
• Re: Fwd: dependency tee from c parser entities downto token
  • From: Konrad Eisele <konrad@xxxxxxxxxxx>
• Re: Fwd: dependency tee from c parser entities downto token
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] simplify: conservative handling of casts with pointers
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• Re: Fwd: dependency tee from c parser entities downto token
  • From: Konrad Eisele <konrad@xxxxxxxxxxx>
• Re: Fwd: dependency tee from c parser entities downto token
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• simplify: conservative handling of casts with pointers
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• Re: Fwd: dependency tee from c parser entities downto token
  • From: Konrad Eisele <konrad@xxxxxxxxxxx>
• Re: Fwd: dependency tee from c parser entities downto token
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Fwd: dependency tee from c parser entities downto token
  • From: Konrad Eisele <konrad@xxxxxxxxxxx>
• Re: Fwd: dependency tee from c parser entities downto token
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Fwd: dependency tee from c parser entities downto token
  • From: Konrad Eisele <eiselekd@xxxxxxxxx>
• Fwd: dependency tee from c parser entities downto token
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Konrad Eisele <eiselekd@xxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Konrad Eisele <eiselekd@xxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Konrad Eisele <eiselekd@xxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Konrad Eisele <eiselekd@xxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Konrad Eisele <eiselekd@xxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Konrad Eisele <eiselekd@xxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Konrad Eisele <eiselekd@xxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Konrad Eisele <eiselekd@xxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Konrad Eisele <konrad@xxxxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Konrad Eisele <konrad@xxxxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] unssa: track use of newly added pseudo
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH] unssa: track use of newly added pseudo
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Konrad Eisele <eiselekd@xxxxxxxxx>
• Re: dependency tee from c parser entities downto token
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] depend.c: build up a dependency tree from c entities downto tokens: entries in the tree are: macro-depend: tree of #if nesting macro-expansions: possible macro expansion source of a token tok->macro-expansions->macro tok->macro-depend->ma
  • From: Konrad Eisele <eiselekd@xxxxxxxxx>
• Re: [PATCH] depend.c: build up a dependency tree from c entities downto tokens: entries in the tree are: macro-depend: tree of #if nesting macro-expansions: possible macro expansion source of a token tok->macro-expansions->macro tok->macro-depend->ma
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] depend.c: build up a dependency tree from c entities downto tokens: entries in the tree are: macro-depend: tree of #if nesting macro-expansions: possible macro expansion source of a token tok->macro-expansions->macro tok->macro-depend->ma
  • From: Konrad Eisele <eiselekd@xxxxxxxxx>
• [PATCH] depend.c: build up a dependency tree from c entities downto tokens: entries in the tree are: macro-depend: tree of #if nesting macro-expansions: possible macro expansion source of a token tok->macro-expansions->macro tok->macro-depend->macro c entities are linked in via [stmt|expr|sym]->start-end-token
  • From: Konrad Eisele <eiselekd@xxxxxxxxx>
• dependency tee from c parser entities downto token
  • From: Konrad Eisele <konrad@xxxxxxxxxxx>
• Re: Killing off __cond_lock()
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxx>
• Re: Killing off __cond_lock()
  • From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
• Re: Killing off __cond_lock()
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: Killing off __cond_lock()
  • From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
• Killing off __cond_lock()
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse: Fix including glibc headers on x86-64
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse: Fix including glibc headers on x86-64
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• help needed: document __nocast vs __bitwise (Was: [PATCH 00/16] mm: prepare for converting vm->vm_flags to 64-bit)
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse: Fix including glibc headers on x86-64
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: Patch: add __builtin_stpcpy and __sync_synchronize to builtin functions
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Patch: add __builtin_stpcpy and __sync_synchronize to builtin functions
  • From: Frederic Crozat <fcrozat@xxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse: Fix including glibc headers on x86-64
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Patch: add __builtin_stpcpy and __sync_synchronize to builtin functions
  • From: Frederic Crozat <fcrozat@xxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse: Fix including glibc headers on x86-64
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse: Fix including glibc headers on x86-64
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse: Fix including glibc headers on x86-64
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Patch: add __builtin_stpcpy and __sync_synchronize to builtin functions
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Using c2xml on kernel sources
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Using c2xml on kernel sources
  • From: Shakthi Kannan <shakthimaan@xxxxxxxxx>
• Re: Using c2xml on kernel sources
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Using c2xml on kernel sources
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Using c2xml on kernel sources
  • From: Shakthi Kannan <shakthimaan@xxxxxxxxx>
• Re: Patch: add __builtin_stpcpy and __sync_synchronize to builtin functions
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Patch: add __builtin_stpcpy and __sync_synchronize to builtin functions
  • From: Frederic Crozat <fcrozat@xxxxxxxx>
• strings
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: sparse-llvm: pseudo_to_value: Assertion `sym->ident == ((void *)0)' failed
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• sparse-llvm: pseudo_to_value: Assertion `sym->ident == ((void *)0)' failed
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [RFC/PATCH 2/2] sparse, llvm: Fix varargs functions
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [RFC/PATCH 2/2] sparse, llvm: Fix varargs functions
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• [RFC/PATCH 2/2] sparse, llvm: Fix varargs functions
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH] evaluate: reject post-ops on void*
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [RFC] evaluate: pointer arithmetics on plain void* (was: [PATCH] evaluate: reject post-ops on void*)
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [RFC] evaluate: pointer arithmetics on plain void*
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• [RFC] evaluate: pointer arithmetics on plain void* (was: [PATCH] evaluate: reject post-ops on void*)
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• [PATCH] evaluate: reject post-ops on void*
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• sparse-llvm has been merged
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] sparse: Add 'leaf' to ignored attributes.
  • From: Ethan Jackson <ethan@xxxxxxxxxx>
• Re: [PATCH] sparse: Add 'leaf' to ignored attributes.
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] sparse: Add 'leaf' to ignored attributes.
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH] sparse: Add 'leaf' to ignored attributes.
  • From: Ethan Jackson <ethan@xxxxxxxxxx>
• Re: [PATCH 2/3] sparse, llvm: Add test case for <stdbool.h> type
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH 2/3] sparse, llvm: Add test case for <stdbool.h> type
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 2/3] sparse, llvm: Add test case for <stdbool.h> type
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH 2/3] sparse, llvm: Add test case for <stdbool.h> type
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• [PATCH 3/3] Revert "sparse: Bump up sizeof(_Bool) to 8 bits"
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH 2/3] sparse, llvm: Add test case for <stdbool.h> type
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH 1/3] sparse, llvm: Use LLVMInt1Type() in sym_basetype_type()
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Sparse 0.4.4 is released
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH] sparse, llvm: Don't fail the build if LLVM is too old
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [GIT PULL] Sparse LLVM backend
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH] sparse, llvm: Don't fail the build if LLVM is too old
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: cannot size expression - exported array in kernel
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: cannot size expression - exported array in kernel
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH] sparse, llvm: Simplify comparison op code generation
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] sparse, llvm: Simplify comparison op code generation
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH] sparse, llvm: FP comparison op code generation
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH] sparse, llvm: Simplify comparison op code generation
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] sparse, llvm: Simplify comparison op code generation
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH] sparse, llvm: Simplify comparison op code generation
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] sparse, llvm: Simplify comparison op code generation
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH] sparse, llvm: More comparison ops code generation
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] sparse, llvm: More comparison ops code generation
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH 2/2] sparse, llvm: OP_SET_B and OP_SET_A code generation
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH 1/2] sparse, llvm: Pointer cast code generation
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: suggestion for Merging LLVM
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• suggestion for Merging LLVM
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH 3/3] sparse, llvm: Make llc output to stdout in sparsec
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH 2/3] sparse, llvm: Fix 'extern' symbol code generation
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH 1/3] sparse, llvm: Fix symbol initializer code generation
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• cannot size expression - exported array in kernel
  • From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
• [PATCH 2/2] sparse, llvm: Function pointer code generation
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH 1/2] sparse, llvm: Make 'sparsec' error handling more robust
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: OP_CALL and function pointers
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: OP_CALL and function pointers
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• OP_CALL and function pointers
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: Reduced call graph
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Reduced call graph
  • From: Nguyen Thai Ngoc Duy <pclouds@xxxxxxxxx>
• Re: Reduced call graph
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: variable size array declarations
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] recognize binary constants
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Reduced call graph
  • From: Nguyen Thai Ngoc Duy <pclouds@xxxxxxxxx>
• Re: [PATCH] recognize binary constants
  • From: Dan Carpenter <error27@xxxxxxxxx>
• sparse repository at kernel.org is back
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Sparse at git.kernel.org
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Sparse at git.kernel.org
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• variable size array declarations
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] sparse, llvm: Add support for union types
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH] sparse, llvm: Add support for array types
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH] sparse, llvm: Fix symbol_type() for bitfields and enums
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH 2/2] sparse, llvm: Fix struct code generation
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH 1/2] sparse, llvm: Use new LLVM type system API for structs
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH] sparse, llvm: Fix 'void *' pointer code generation
  • From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
• Re: [PATCH] sparse, llvm: Fix 'void *' pointer code generation
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH] sparse, llvm: Fix 'void *' pointer code generation
  • From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
• Re: [PATCH] sparse, llvm: Fix 'void *' pointer code generation
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• Re: [PATCH] sparse, llvm: Fix 'void *' pointer code generation
  • From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
• Re: [PATCH] sparse, llvm: Fix 'void *' pointer code generation
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] sparse, llvm: Fix 'void *' pointer code generation
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [RFC/PATCH 2/2] sparse: Use native sizes for data types
  • From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
• Re: [RFC/PATCH 2/2] sparse: Use native sizes for data types
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [RFC/PATCH 2/2] sparse: Use native sizes for data types
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• [RFC/PATCH 2/2] sparse: Use native sizes for data types
  • From: penberg@xxxxxxxxxxxxxx
• [RFC/PATCH 1/2] sparse: Fix including glibc headers on x86-64
  • From: penberg@xxxxxxxxxxxxxx
• [PATCH 2/2] sparse, llvm: Add support for logical ops
  • From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
• [PATCH 1/2] sparse: Bump up sizeof(_Bool) to 8 bits
  • From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
• RE: improper sparse warnings in linux kernel build?
  • From: H Hartley Sweeten <hartleys@xxxxxxxxxxxxxxxxxxx>
• Re: improper sparse warnings in linux kernel build?
  • From: Dan Carpenter <error27@xxxxxxxxx>
• improper sparse warnings in linux kernel build?
  • From: H Hartley Sweeten <hartleys@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] recognize binary constants
  • From: Kamal Mostafa <kamal@xxxxxxxxxxxxx>
• Re: [PATCH] recognize binary constants
  • From: Dan Carpenter <error27@xxxxxxxxx>
• [sparse-llvm] LLVM and alignment
  • From: Pekka Enberg <penberg@xxxxxxxxx>
• Re: [PATCH] Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH v2] sparse: Reduce 'test-suite' run output
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 1/3] evaluate: warn on identical exprs around '&&'
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH v2] sparse: Reduce 'test-suite' run output
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [ANNOUNCE] LLVM backend for Sparse
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [ANNOUNCE] LLVM backend for Sparse
  • From: Derek M Jones <derek@xxxxxxxxxxxx>
• Re: [ANNOUNCE] LLVM backend for Sparse
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [ANNOUNCE] LLVM backend for Sparse
  • From: Derek M Jones <derek@xxxxxxxxxxxx>
• Re: [ANNOUNCE] LLVM backend for Sparse
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [ANNOUNCE] LLVM backend for Sparse
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH] Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH] Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH] Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [ANNOUNCE] LLVM backend for Sparse
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [ANNOUNCE] LLVM backend for Sparse
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH 1/3] evaluate: warn on identical exprs around '&&'
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Sparse 0.4.4-rc2
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 1/3] evaluate: warn on identical exprs around '&&'
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• Re: [ANNOUNCE] LLVM backend for Sparse
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [ANNOUNCE] LLVM backend for Sparse
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH] Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH] Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH] Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [PATCH] Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [ANNOUNCE] LLVM backend for Sparse
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [ANNOUNCE] LLVM backend for Sparse
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [ANNOUNCE] LLVM backend for Sparse
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH] Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH] Re: LLVM and PSEUDO_REG/PSEUDO_PHI
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH] cse: update PHI users when throwing away an instruction
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [ANNOUNCE] LLVM backend for Sparse
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 2/3] Make 'linearize_switch()' helper function
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] cse: update PHI users when throwing away an instruction
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH] cse: update PHI users when throwing away an instruction
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: linearize bug?
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [ANNOUNCE] LLVM backend for Sparse
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH 1/3] evaluate: warn on identical exprs around '&&'
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [PATCH 1/3] evaluate: warn on identical exprs around '&&'
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [PATCH 0/3] linearize_statement: split up into helper functions
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH 3/3] evaluate: warn on identical exprs on ?:
  • From: Chris Forbes <chrisf@xxxxxxxxx>
• [PATCH 2/3] evaluate: warn on identical exprs around '||'
  • From: Chris Forbes <chrisf@xxxxxxxxx>
• [PATCH 1/3] evaluate: warn on identical exprs around '&&'
  • From: Chris Forbes <chrisf@xxxxxxxxx>
• Re: [PATCH 1/3] evaluate: warn on identical exprs around '&&'
  • From: Chris Forbes <chrisf@xxxxxxxxx>
• Re: [PATCH 1/3] evaluate: warn on identical exprs around '&&'
  • From: Chris Forbes <chrisf@xxxxxxxxx>
• Re: [PATCH 3/3] evaluate: warn on identical exprs on ?:
  • From: Chris Forbes <chrisf@xxxxxxxxx>
• Re: [PATCH 1/3] evaluate: warn on identical exprs around '&&'
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [PATCH 3/3] evaluate: warn on identical exprs on ?:
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [PATCH] cse: update PHI users when throwing away an instruction
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] cse: update PHI users when throwing away an instruction
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• [PATCH 3/3] evaluate: warn on identical exprs on ?:
  • From: Chris Forbes <chrisf@xxxxxxxxx>
• [PATCH 2/3] evaluate: warn on identical exprs around '||'
  • From: Chris Forbes <chrisf@xxxxxxxxx>
• [PATCH 1/3] evaluate: warn on identical exprs around '&&'
  • From: Chris Forbes <chrisf@xxxxxxxxx>
• Re: linearize bug?
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 0/3] linearize_statement: split up into helper functions
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 3/3] Make 'linearize_return()' helper function
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 2/3] Make 'linearize_switch()' helper function
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 1/3] Make 'linearize_iterator()' helper function
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 0/3] linearize_statement: split up into helper functions
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: linearize bug?
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: linearize bug?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] sparse: Reduce 'test-suite' run output
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• Re: linearize bug?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: linearize bug?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: linearize bug?
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: linearize bug?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: linearize bug?
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH] sparse: Reduce 'test-suite' run output
  • From: blp@xxxxxxxxxxxxxxx (Ben Pfaff)
• Re: linearize bug?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] sparse: Reduce 'test-suite' run output
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• Re: linearize bug?
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: [PATCH 1/5] sparse: Show expected vs. actual output on test failure
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH 1/5] sparse: Show expected vs. actual output on test failure
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH] sparse: Reduce 'test-suite' run output
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• linearize bug?
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH] sparse: Reduce 'test-suite' run output
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 1/5] sparse: Show expected vs. actual output on test failure
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH] sparse: Reduce 'test-suite' run output
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH 1/5] sparse: Show expected vs. actual output on test failure
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH 4/5] sparse, i386: Fix boolean bit size
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH 4/5] sparse, i386: Fix boolean bit size
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH 4/5] sparse, i386: Fix boolean bit size
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 2/5] sparse: Enable unhandled validation tests
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 2/5] sparse: Enable unhandled validation tests
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH 5/5] sparse: Add end-to-end compiler shell script
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• sparse considers LONG_MAX too big for long on x86-64
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: sparse and multiarch include paths
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: sparse and multiarch include paths
  • From: Ludovic Brenta <ludovic@xxxxxxxxxxxxxxxxxx>
• Re: sparse and multiarch include paths
  • From: Chris Forbes <chrisf@xxxxxxxxx>
• sparse and multiarch include paths
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [PATCH 2/5] sparse: Enable unhandled validation tests
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 2/2] mmc: fix integer assignments to pointer
  • From: "S, Venkatraman" <svenkatr@xxxxxx>
• Re: [PATCH 2/2] mmc: fix integer assignments to pointer
  • From: "S, Venkatraman" <svenkatr@xxxxxx>
• (slightly) inconsistent code in evaluate.c:type_difference
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• Re: [PATCH 2/2] mmc: fix integer assignments to pointer
  • From: J Freyensee <james_p_freyensee@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/5] sparse: Show expected vs. actual output on test failure
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: bad asm goto ?
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] Ignore the ms_hook_prologue attribute.
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 2/2] mmc: fix integer assignments to pointer
  • From: Ben Pfaff <blp@xxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] mmc: fix integer assignments to pointer
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: [PATCH 2/2] mmc: fix integer assignments to pointer
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: [PATCH 2/2] mmc: fix integer assignments to pointer
  • From: blp@xxxxxxxxxxxxxxx (Ben Pfaff)
• Re: [PATCH 2/2] mmc: fix integer assignments to pointer
  • From: Chris Ball <cjb@xxxxxxxxxx>
• Re: [PATCH 2/2] mmc: fix integer assignments to pointer
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] mmc: fix integer assignments to pointer
  • From: Chris Ball <cjb@xxxxxxxxxx>
• Re: [PATCH 2/2] mmc: fix integer assignments to pointer
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] mmc: fix integer assignments to pointer
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: [PATCH 2/2] mmc: fix integer assignments to pointer
  • From: Chris Ball <cjb@xxxxxxxxxx>
• [PATCH] FAQ: update the website address and call it Wiki
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• Re: [PATCH 2/5] sparse: Enable unhandled validation tests
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [PATCH 4/5] sparse, i386: Fix boolean bit size
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [PATCH 5/5] sparse: Add end-to-end compiler shell script
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• [PATCH 2/5] sparse: Enable unhandled validation tests
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH 3/5] sparse: Fix __builtin_safe_p for pure and const functions
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH 5/5] sparse: Add end-to-end compiler shell script
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH 4/5] sparse, i386: Fix boolean bit size
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• [PATCH 1/5] sparse: Show expected vs. actual output on test failure
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: bad asm goto ?
  • From: Harvey Harrison <harvey.harrison@xxxxxxxxx>
• [PATCH] Ignore the ms_hook_prologue attribute.
  • From: Michael Stefaniuc <mstefani@xxxxxxxxxx>
• Re: Sparse 0.4.4-rc1
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 2/2] fix common misspellings with codespell
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 1/2] FAQ: fix a typo ("because or")
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH 2/2] fix common misspellings with codespell
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• [PATCH 1/2] FAQ: fix a typo ("because or")
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• Sparse 0.4.4-rc1
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: more "unreplaced symbol" warnings
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [RFC PATCH 0/2] check for identical exprs on LHS and RHS of '&&'
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: [RFC PATCH 0/2] check for identical exprs on LHS and RHS of '&&'
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: intended use of "safe"?
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: intended use of "safe"?
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: relicensing Sparse
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: relicensing Sparse
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: relicensing Sparse
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• intended use of "safe"?
  • From: blp@xxxxxxxxxxxxxxx (Ben Pfaff)
• Re: relicensing Sparse
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: [PATCH] fix a memory leak in compile-i386.c
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: relicensing Sparse
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• relicensing Sparse
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: [RFC PATCH 0/2] check for identical exprs on LHS and RHS of '&&'
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/2] check for identical exprs on LHS and RHS of '&&'
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• [PATCH 2/2] initial work on check for identical exprs on both sides of '&&'; needs more
  • From: Chris Forbes <chrisf@xxxxxxxxx>
• [PATCH 1/2] add test case for identical exprs on LHS and RHS of '&&' operator
  • From: Chris Forbes <chrisf@xxxxxxxxx>
• [RFC PATCH 0/2] check for identical exprs on LHS and RHS of '&&'
  • From: Chris Forbes <chrisf@xxxxxxxxx>
• Re: [PATCH] fix a memory leak in compile-i386.c
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• [PATCH] fix a memory leak in compile-i386.c
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• sparse problems with __acquires, __releases
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: [PATCH] Recognize and ignore _Complex, artificial and vector_size
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH] Recognize and ignore _Complex, artificial and vector_size
  • From: Pavel Roskin <proski@xxxxxxx>
• Re: [PATCH] sparse: Add 'artifical' to ignore attributes
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH] sparse: Add 'artifical' to ignore attributes
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Missing bitwise warnings
  • From: Emil Langrock <emil.langrock@xxxxxx>
• Re: more "unreplaced symbol" warnings
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: more "unreplaced symbol" warnings
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: more "unreplaced symbol" warnings
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: vector_size attribute?
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: more "unreplaced symbol" warnings
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: more "unreplaced symbol" warnings
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: vector_size attribute?
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: "advancing past deep designator" warnings
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: "advancing past deep designator" warnings
  • From: Dan Carpenter <error27@xxxxxxxxx>
• more "unreplaced symbol" warnings
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• "advancing past deep designator" warnings
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: vector_size attribute?
  • From: Avi Kivity <avi@xxxxxxxxxx>
• vector_size attribute?
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: Flow graph - identify loop body
  • From: Diego Pinheiro <diegoquintanap@xxxxxxxxx>
• Re: Flow graph - identify loop body
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Flow graph - identify loop body
  • From: Diego Pinheiro <diegoquintanap@xxxxxxxxx>
• Re: [PATCH] evaluate: Allow sizeof(_Bool) to succeed.
  • From: Ben Pfaff <blp@xxxxxxxxxx>
• Re: [PATCH] evaluate: Allow sizeof(_Bool) to succeed.
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] evaluate: Allow sizeof(_Bool) to succeed.
  • From: Ben Pfaff <blp@xxxxxxxxxx>
• Re: [PATCH] evaluate: Allow sizeof(_Bool) to succeed.
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] evaluate: Allow sizeof(_Bool) to succeed.
  • From: Ben Pfaff <blp@xxxxxxxxxx>
• Re: [PATCH] evaluate: Allow sizeof(_Bool) to succeed.
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH] evaluate: Allow sizeof(_Bool) to succeed.
  • From: Ben Pfaff <blp@xxxxxxxxxx>
• Re: [PATCH] fix sparse happy borkage when including gfp.h
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] parse.c: "if(" -> "if (" adjustment
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] use ARRAY_SIZE() when possible (continued)
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: sparse, gcc 4.6 and a few build changes
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 1/2] Add new streams to a hash-list based on their names
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/2] Fix 'already_tokenized()' performance problem
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] Add new streams to a hash-list based on their names
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 0/2] Fix 'already_tokenized()' performance problem
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• PATCH 2/2] Teach 'already_tokenized()' to use the stream name hash table
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 1/2] Add new streams to a hash-list based on their names
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 0/2] Fix 'already_tokenized()' performance problem
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] better dealing with OP_PHISOURCE insn
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• Re: [PATCH] memops.c: fix load instruction simplification
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• Re: [PATCH 2/2] better dealing with OP_PHISOURCE insn
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• [PATCH] parse.c: "if(" -> "if (" adjustment
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• Re: [PATCH 2/2] better dealing with OP_PHISOURCE insn
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• Re: [PATCH 2/2] better dealing with OP_PHISOURCE insn
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• Re: [PATCH 2/2] better dealing with OP_PHISOURCE insn
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• Re: [PATCH] fix sparse happy borkage when including gfp.h
  • From: Dave Hansen <dave@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] better dealing with OP_PHISOURCE insn
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 1/3] build: allow easy override of GCC_BASE
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 3/3] Fix build with GCC 4.6 series.
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 2/3] build: add an all-installable target that builds the targets to install.
  • From: Diego Elio Pettenò <flameeyes@xxxxxxxxx>
• Re: [PATCH 2/3] build: add an all-installable target that builds the targets to install.
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: sparse, gcc 4.6 and a few build changes
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH] treat `enum opcode' as enumeration rather than int
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• [PATCH] use ARRAY_SIZE() when possible (continued)
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• [PATCH 3/3] Fix build with GCC 4.6 series.
  • From: Diego Elio Pettenò <flameeyes@xxxxxxxxx>
• [PATCH 2/3] build: add an all-installable target that builds the targets to install.
  • From: Diego Elio Pettenò <flameeyes@xxxxxxxxx>
• [PATCH 1/3] build: allow easy override of GCC_BASE
  • From: Diego Elio Pettenò <flameeyes@xxxxxxxxx>
• Re: sparse, gcc 4.6 and a few build changes
  • From: Diego Elio Pettenò <flameeyes@xxxxxxxxx>
• Re: [PATCH] flow.c: make comment for `dominates' reflect code
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] remove unused "container" macro
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: sparse, gcc 4.6 and a few build changes
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH] show_instruction: tolerate NULL sym for OP_SYMADDR
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• Re: [PATCH 2/4] more transparent dealing with tokens/position
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• [PATCH 4/4] more transparent dealing with tokens/position
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• [PATCH 3/4] more transparent dealing with tokens/position
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• [PATCH 2/4] more transparent dealing with tokens/position
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• [PATCH 1/4] more transparent dealing with tokens/position
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• Re: [PATCH] unify usage of VOID
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• Re: [PATCH] unify usage of VOID
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH] unify usage of VOID
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• Re: [PATCH] memops.c: fix load instruction simplification
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• Re: [PATCH 2/2] better dealing with OP_PHISOURCE insn
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• [PATCH 2/2] better dealing with OP_PHISOURCE insn
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• [PATCH 1/2] better dealing with OP_PHISOURCE insn
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• [PATCH] flow.c: make comment for `dominates' reflect code
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• [PATCH] remove unused "container" macro
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• [PATCH] memops.c: fix load instruction simplification
  • From: Jan Pokorný <pokorny_jan@xxxxxxxxx>
• Re: [PATCH] Makefile: warn user when libxml and/or libgtk2 are not available
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] Makefile: warn user when libxml and/or libgtk2 are not available
  • From: Florian Fainelli <f.fainelli@xxxxxxxxx>
• Re: [PATCH] Makefile: warn user when libxml and/or libgtk2 are not available
  • From: Florian Fainelli <f.fainelli@xxxxxxxxx>
• Re: [PATCH] Makefile: warn user when libxml and/or libgtk2 are not available
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH] Makefile: warn user when libxml and/or libgtk2 are not available
  • From: Florian Fainelli <f.fainelli@xxxxxxxxx>
• Re: relicensing Sparse
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: relicensing Sparse
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: Novafora relicenses Transmeta sparse copyrights under the MIT license
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Novafora relicenses Transmeta sparse copyrights under the MIT license
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Novafora relicenses Transmeta sparse copyrights under the MIT license
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: [PATCH 1/2] Fix tokenizer for octal escape sequences
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH 2/2] Update the validation check for escape sequences
  • From: Namhyung Kim <namhyung@xxxxxxxxx>
• [PATCH 1/2] Fix tokenizer for octal escape sequences
  • From: Namhyung Kim <namhyung@xxxxxxxxx>
• Re: [PATCH] use ARRAY_SIZE() when possible
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] use ARRAY_SIZE() when possible
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] use ARRAY_SIZE() when possible
  • From: Nicholas Mc Guire <der.herr@xxxxxxx>
• [PATCH] use ARRAY_SIZE() when possible
  • From: Namhyung Kim <namhyung@xxxxxxxxx>
• Re: [PATCH] memops.c: always true expression
  • From: Anderson Lizardo <anderson.lizardo@xxxxxxxxx>
• Re: [PATCH] memops.c: always true expression
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH] memops.c: always true expression
  • From: Nicolas Kaiser <nikai@xxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• sparse 0.4.3
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [B.A.T.M.A.N.] "wrong count at exit" after spin_lock/_unlock pair
  • From: Sven Eckelmann <sven.eckelmann@xxxxxx>
• Sparse complains about __constant_cpu_to_be32(1)
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: including sparse headers in C++ code
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxx>
• "wrong count at exit" after spin_lock/_unlock pair
  • From: Sven Eckelmann <sven.eckelmann@xxxxxx>
• Re: bad asm goto ?
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: bad asm goto ?
  • From: Harvey Harrison <harvey.harrison@xxxxxxxxx>
• Re: bad asm goto ?
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: bad asm goto ?
  • From: Harvey Harrison <harvey.harrison@xxxxxxxxx>
• Re: bad asm goto ?
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: bad asm goto ?
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: bad asm goto ?
  • From: Dave Jones <davej@xxxxxxxxxx>
• Re: bad asm goto ?
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• bad asm goto ?
  • From: Dave Jones <davej@xxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Tomas Klacko <tomas.klacko@xxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: David Malcolm <dmalcolm@xxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Tomas Klacko <tomas.klacko@xxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Tomas Klacko <tomas.klacko@xxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Tomas Klacko <tomas.klacko@xxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Tomas Klacko <tomas.klacko@xxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxx>
• Re: [patch 1/2] OSS: soundcard: locking bug in sound_ioctl()
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [patch 1/2] OSS: soundcard: locking bug in sound_ioctl()
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Tomas Klacko <tomas.klacko@xxxxxxxxx>
• Re: [patch 1/2] OSS: soundcard: locking bug in sound_ioctl()
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [patch 1/2] OSS: soundcard: locking bug in sound_ioctl()
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [patch 1/2] OSS: soundcard: locking bug in sound_ioctl()
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [patch 1/2] OSS: soundcard: locking bug in sound_ioctl()
  • From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
• Re: [patch 1/2] OSS: soundcard: locking bug in sound_ioctl()
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxx>
• Re: [patch 1/2] OSS: soundcard: locking bug in sound_ioctl()
  • From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
• Re: [patch 1/2] OSS: soundcard: locking bug in sound_ioctl()
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: including sparse headers in C++ code
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• including sparse headers in C++ code
  • From: Tomas Klacko <tomas.klacko@xxxxxxxxx>
• sparse 2.4.3-rc1
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH v2] parser: add Blackfin gcc info
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH v2] parser: add Blackfin gcc info
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: [PATCH] parser: add Blackfin gcc info
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] parser: add Blackfin gcc info
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: [PATCH] parser: add Blackfin gcc info
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: [PATCH] parser: add Blackfin gcc info
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] parser: add Blackfin gcc info
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [PATCH] parser: add Blackfin gcc info
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [PATCH] parser: add Blackfin gcc info
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: [PATCH] parser: add Blackfin gcc info
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] parser: add Blackfin gcc info
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: [PATCH] parser: add Blackfin gcc info
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• [PATCH] parser: add Blackfin gcc info
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: [PATCH] trivial: disable sparse' warning for "potentially expensive pointer subtraction".
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxx>
• Re: [PATCH] Fixup and cleanup of the modifier_string() function
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH] Fixup and cleanup of the modifier_string() function
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxx>
• Re: [PATCH] Fixup and cleanup of the modifier_string() function (was Re: modifier_string() inconsistency with modifiers)
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH] removed an unused parameter for show_symbol_list()
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxx>
• [PATCH] Fixup and cleanup of the modifier_string() function (was Re: modifier_string() inconsistency with modifiers)
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxx>
• Re: modifier_string() inconsistency with modifiers
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: modifier_string() inconsistency with modifiers
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxx>
• Re: modifier_string() inconsistency with modifiers
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [[PATCH]] Fix a typo - "typdef" is neither C nor plain English
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [[PATCH]] Fix a typo - "typdef" is neither C nor plain English
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxx>
• modifier_string() inconsistency with modifiers
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxx>
• Re: Lots of "error: multiple storage classes" warnings on the Linux kernel
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: Lots of "error: multiple storage classes" warnings on the Linux kernel
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Lots of "error: multiple storage classes" warnings on the Linux kernel
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxx>
• Re: sparse ignores __attribute__((packed))
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• sparse ignores __attribute__((packed))
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: Bogus warning when comparing nocast short variables
  • From: Chris Li <christ.li@xxxxxxxxx>
• Bogus warning when comparing nocast short variables
  • From: Pavel Roskin <proski@xxxxxxx>
• Re: Spurious symbol 'foo' was not declared
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Spurious symbol 'foo' was not declared
  • From: Morten Welinder <mortenw@xxxxxxxxx>
• Re: [PATCH 2/2] parser: define __builtin_unreachable
  • From: Chris Li <christ.li@xxxxxxxxx>
• Re: [PATCH 2/2] parser: define __builtin_unreachable
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] parser: define __builtin_unreachable
  • From: Chris Li <christ.li@xxxxxxxxx>
• Re: Small patch for __builtin_fabs and an attribute
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 1/2] parser: fix and simplify support of asm goto
  • From: Chris Li <christ.li@xxxxxxxxx>
• Re: Small patch for __builtin_fabs and an attribute
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 2/2] parser: define __builtin_unreachable
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• [PATCH 2/2] parser: define __builtin_unreachable
  • From: Jiri Slaby <jslaby@xxxxxxx>
• [PATCH 1/2] parser: fix and simplify support of asm goto
  • From: Jiri Slaby <jslaby@xxxxxxx>
• Small patch for __builtin_fabs and an attribute
  • From: Morten Welinder <mortenw@xxxxxxxxx>
• Re: Warning message when using sparse
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Warning message when using sparse
  • From: Jiri Slaby <jirislaby@xxxxxxxxx>
• Re: Warning message when using sparse
  • From: Larry Finger <Larry.Finger@xxxxxxxxxxxx>
• Re: Warning message when using sparse
  • From: Jiri Slaby <jirislaby@xxxxxxxxx>
• Re: [PATCH 1/1] parser: add support for asm goto
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 1/1] parser: add support for asm goto
  • From: Jiri Slaby <jslaby@xxxxxxx>
• Re: [PATCH 1/1] parser: add support for asm goto
  • From: Jiri Slaby <jslaby@xxxxxxx>
• Re: [PATCH 1/1] parser: add support for asm goto
  • From: Jiri Slaby <jslaby@xxxxxxx>
• Re: [PATCH 1/1] parser: add support for asm goto
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: L'\0' handling
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 1/1] parser: add support for asm goto
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [PATCH 1/1] parser: add support for asm goto
  • From: Jiri Slaby <jslaby@xxxxxxx>
• Re: [PATCH 1/1] parser: add support for asm goto
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: help for using sparse
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: help for using sparse
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: help for using sparse
  • From: bonneta <bonneta@xxxxxxxxxx>
• Re: help for using sparse
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: help for using sparse
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: help for using sparse
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• help for using sparse
  • From: bonneta <bonneta@xxxxxxxxxx>
• Re: [PATCH] Ignore the may_alias GCC attribute
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH] Ignore the may_alias GCC attribute
  • From: Damien Lespiau <damien.lespiau@xxxxxxxxx>
• packed struct sizeof wrong
  • From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
• Re: [0/4] inspector for sparse
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: [0/4] inspector for sparse
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: [0/4] inspector for sparse
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: L'\0' handling
  • From: Michael Stefaniuc <mstefani@xxxxxxxxxx>
• Re: L'\0' handling
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: L'\0' handling
  • From: Michael Stefaniuc <mstefani@xxxxxxxxxx>
• Re: L'\0' handling
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: L'\0' handling
  • From: Michael Stefaniuc <mstefani@xxxxxxxxxx>
• Re: L'\0' handling
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: L'\0' handling
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: L'\0' handling
  • From: Michael Stefaniuc <mstefani@xxxxxxxxxx>
• Re: L'\0' handling
  • From: Yura Pakhuchiy <pakhuchiy@xxxxxxxxx>
• Re: L'\0' handling
  • From: Michael Stefaniuc <mstefani@xxxxxxxxxx>
• L'\0' handling
  • From: Yura Pakhuchiy <pakhuchiy@xxxxxxxxx>
• Re: [0/4] inspector for sparse
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH 1/4] inspect: add custom ast treeview model
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• PATCH 4/4] inspect: add some expression inspection
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH 3/4] inspect: Add test-inspect program
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH 2/4] inspect: add some example inspect for symbol and statement
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [0/4] inspector for sparse
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: building of call tree
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• building of call tree
  • From: Sergey Lapin <slapinid@xxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Pavel Roskin <proski@xxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: [PATCH] eliminate insane conversions from int to enum
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: segfault in sparse snapshot 2010-02-13
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: segfault in sparse snapshot 2010-02-13
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: segfault in sparse snapshot 2010-02-13
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• [PATCH] eliminate insane conversions from int to enum
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: segfault in sparse snapshot 2010-02-13
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: segfault in sparse snapshot 2010-02-13
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: segfault in sparse snapshot 2010-02-13
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: segfault in sparse snapshot 2010-02-13
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: segfault in sparse snapshot 2010-02-13
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: segfault in sparse snapshot 2010-02-13
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: segfault in sparse snapshot 2010-02-13
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: segfault in sparse snapshot 2010-02-13
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: segfault in sparse snapshot 2010-02-13
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• segfault in sparse snapshot 2010-02-13
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Pavel Roskin <proski@xxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Pavel Roskin <proski@xxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Pavel Roskin <proski@xxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Pavel Roskin <proski@xxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Pavel Roskin <proski@xxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: Sparse crash when mixing int and enum in ternary operator
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Sparse crash when mixing int and enum in ternary operator
  • From: Pavel Roskin <proski@xxxxxxx>
• Re: linux kernel warnings/errors (#8)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: linux kernel warnings/errors (#7)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: linux kernel warnings/errors
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: linux kernel warnings/errors
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• linux kernel warnings/errors
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: Defect in linearization of short circuit &&
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: enum warning patch (was Re: Defect in linearization of short circuit &&)
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: Defect in linearization of short circuit &&
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: enum warning patch (was Re: Defect in linearization of short circuit &&)
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: enum warning patch (was Re: Defect in linearization of short circuit &&)
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• enum warning patch (was Re: Defect in linearization of short circuit &&)
  • From: Kamil Dudka <kdudka@xxxxxxxxxx>
• Re: Defect in linearization of short circuit &&
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Defect in linearization of short circuit &&
  • From: Jacek Śliwerski <sliwers@xxxxxxxxxxxxxx>
• Re: Defect in linearization of short circuit &&
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Defect in linearization of short circuit &&
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Defect in linearization of short circuit &&
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: Defect in linearization of short circuit &&
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Defect in linearization of short circuit &&
  • From: Jacek Śliwerski <sliwers@xxxxxxxxxxxxxx>
• Re: Defect in linearization of short circuit &&
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Defect in linearization of short circuit &&
  • From: Jacek Śliwerski <sliwers@xxxxxxxxxxxxxx>
• Re: Defect in linearization of short circuit &&
  • From: Christopher Li <sparse@xxxxxxxxxxx>
• Re: Defect in linearization of short circuit &&
  • From: Jacek Śliwerski <sliwers@xxxxxxxxxxxxxx>
• Defect in linearization of short circuit &&
  • From: Jacek Śliwerski <sliwers@xxxxxxxxxxxxxx>