Linux Sparse
[Prev Page][Next Page]
- [[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>
- Re: Warnings on global symbols accessed only from assembly code
- From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
- Re: Warnings on global symbols accessed only from assembly code
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Warnings on global symbols accessed only from assembly code
- From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
- Re: Warnings on global symbols accessed only from assembly code
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Warnings on global symbols accessed only from assembly code
- From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
- Re: typedefs and alignment
- From: Dan Carpenter <error27@xxxxxxxxx>
- Re: typedefs and alignment
- From: Chris Li <christ.li@xxxxxxxxx>
- Re: typedefs and alignment
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH 01/14] ARM: LPC32XX: Initial architecture header files
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCH 01/14] ARM: LPC32XX: Initial architecture header files
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- RE: [PATCH 01/14] ARM: LPC32XX: Initial architecture header files
- From: "H Hartley Sweeten" <hartleys@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 01/14] ARM: LPC32XX: Initial architecture header files
- From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
- typedefs and alignment
- From: Dan Carpenter <error27@xxxxxxxxx>
- Re: Re: Re: Re: Re: Getting info from used typedef
- From: Thomas Schmid <Thomas.Schmid@xxxxxxxxxxxxxxxxx>
- Re: Re: Re: Re: Getting info from used typedef
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Re: Re: Re: Getting info from used typedef
- From: Thomas Schmid <Thomas.Schmid@xxxxxxxxxxxxxxxxx>
- Re: Sparse licensing
- From: Dan Carpenter <error27@xxxxxxxxx>
- Re: Re: Re: Getting info from used typedef
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Detection of locking one lock twice
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Detection of locking one lock twice
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Detection of locking one lock twice
- From: Petr Muller <afri@xxxxxxx>
- Re: cgcc and REAL_CC help
- From: rubisher <rubisher@xxxxxxxxxx>
- Re: cgcc and REAL_CC help
- From: Chris Li <christ.li@xxxxxxxxx>
- Re: cgcc and REAL_CC help
- From: rubisher <rubisher@xxxxxxxxxx>
- Re: cgcc and REAL_CC help
- From: Bert Wesarg <bert.wesarg@xxxxxxxxxxxxxx>
- cgcc and REAL_CC help
- From: rubisher <rubisher@xxxxxxxxxx>
- Re: sparse 0.4.2: cgcc issue
- From: rubisher <rubisher@xxxxxxxxxx>
- Re: sparse 0.4.2: cgcc issue
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: sparse 0.4.2: cgcc issue
- From: Blue Swirl <blauwirbel@xxxxxxxxx>
- Re: sparse 0.4.2: cgcc issue
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: sparse 0.4.2: cgcc issue
- From: rubisher <rubisher@xxxxxxxxxx>
- sparse 0.4.2: cgcc issue
- From: rubisher <rubisher@xxxxxxxxxx>
- Re: Re: Re: Getting info from used typedef
- From: Thomas Schmid <Thomas.Schmid@xxxxxxxxxxxxxxxxx>
- Re: Re: Getting info from used typedef
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Antwort: Re: Getting info from used typedef
- From: Thomas Schmid <Thomas.Schmid@xxxxxxxxxxxxxxxxx>
- Re: Getting info from used typedef
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] Ignore "naked" attribute
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH] Ignore "naked" attribute
- From: Michael Buesch <mb@xxxxxxxxx>
- Re: [PATCH] sparse: Add more ignored attributes
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH] sparse: Add more ignored attributes
- From: Michael Buesch <mb@xxxxxxxxx>
- Re: [PATCH] sparse: Add more ignored attributes
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Getting info from used typedef
- From: Thomas Schmid <Thomas.Schmid@xxxxxxxxxxxxxxxxx>
- [PATCH] sparse: Add more ignored attributes
- From: Michael Buesch <mb@xxxxxxxxx>
- Re: [PATCH] Fix incorrect linearization of "x && y && z"
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: User question for __context__ or similiar
- From: Christopher Li <sparse@xxxxxxxxxxx>
- User question for __context__ or similiar
- From: Holger Freyther <zecke@xxxxxxxxxxx>
- Re: [PATCH] Makefile: fix permissions mixup on install
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: 'make install' target issues
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH] Makefile: fix permissions mixup on install
- From: Dan McGee <dan@xxxxxxxxxxxxx>
- 'make install' target issues
- From: Dan McGee <dan@xxxxxxxxxxxxx>
- [PATCH] Fix incorrect linearization of "x && y && z"
- From: Daniel De Graaf <danieldegraaf@xxxxxxxxx>
- Sparse 0.4.2 released
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] New attribute designated_init: mark a struct as requiring designated init
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCHv2] Rename -Wall to Wsparse-all, so it doesn't get turned on unintentionally
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCHv2] Rename -Wall to Wsparse-all, so it doesn't get turned on unintentionally
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] New attribute designated_init: mark a struct as requiring designated init
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCHv3] New attribute designated_init: mark a struct as requiring designated init
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- [PATCHv2] Rename -Wall to Wsparse-all, so it doesn't get turned on unintentionally
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- [PATCH] Rename -Wall to Wsparse-all, so it doesn't get turned on unintentionally
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- [PATCHv2] New attribute designated_init: mark a struct as requiring designated init
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCH] New attribute designated_init: mark a struct as requiring designated init
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCH] New attribute designated_init: mark a struct as requiring designated init
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH] New attribute designated_init: mark a struct as requiring designated init
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: Handle __builtin_ms_va_list.
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Handle __builtin_ms_va_list.
- From: Michael Stefaniuc <mstefani@xxxxxxxxxx>
- Re: [PATCH] Ignore the alloc_size attribute.
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Ignore the ms_abi/sysv_abi attributes.
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Ignore the ms_abi/sysv_abi attributes.
- From: Michael Stefaniuc <mstefani@xxxxxxxxxx>
- [PATCH] Ignore the alloc_size attribute.
- From: Michael Stefaniuc <mstefaniuc@xxxxxxxxx>
- [PATCH] Ignore the ms_abi/sysv_abi attributes.
- From: Michael Stefaniuc <mstefaniuc@xxxxxxxxx>
- Re: Ignore the ms_abi/sysv_abi attributes.
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Ignore the alloc_size attribute.
- From: Michael Stefaniuc <mstefani@xxxxxxxxxx>
- Ignore the ms_abi/sysv_abi attributes.
- From: Michael Stefaniuc <mstefani@xxxxxxxxxx>
- Sparse 0.4.2-rc1
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: new sparse release?
- From: Christopher Li <sparse@xxxxxxxxxxx>
- new sparse release?
- From: Jeff Layton <jlayton@xxxxxxxxxxxxxxx>
- Re: Warning from ring buffer code (Was: Re: linux-next: tip tree build warning)
- From: Frédéric Weisbecker <fweisbec@xxxxxxxxx>
- Re: Warning from ring buffer code (Was: Re: linux-next: tip tree build warning)
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
- Re: [PATCH] do not ignore attribute 'noreturn'...
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] do not ignore attribute 'noreturn'...
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] do not ignore attribute 'noreturn'...
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: Warning from ring buffer code (Was: Re: linux-next: tip tree build warning)
- From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
- Re: Warning from ring buffer code (Was: Re: linux-next: tip tree build warning)
- From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
- Re: Warning from ring buffer code (Was: Re: linux-next: tip tree build warning)
- From: Steven Rostedt <srostedt@xxxxxxxxxx>
- Re: Warning from ring buffer code (Was: Re: linux-next: tip tree build warning)
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
- Re: Warning from ring buffer code (Was: Re: linux-next: tip tree build warning)
- From: Steven Rostedt <srostedt@xxxxxxxxxx>
- Re: [PATCH] do not ignore attribute 'noreturn'...
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] do not ignore attribute 'noreturn'...
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] do not ignore attribute 'noreturn'...
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Warning from ring buffer code (Was: Re: linux-next: tip tree build warning)
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Warning from ring buffer code (Was: Re: linux-next: tip tree build warning)
- From: Steven Rostedt <srostedt@xxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: sparse: flow.c:804: rewrite_parent_branch: Asparse: flow.c:804: rewrite_parent_branch: Assertion `changed' failed.
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- sparse: flow.c:804: rewrite_parent_branch: Asparse: flow.c:804: rewrite_parent_branch: Assertion `changed' failed.
- From: Belisko Marek <marek.belisko@xxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Daniel Barkalow <barkalow@xxxxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Daniel Barkalow <barkalow@xxxxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Daniel Barkalow <barkalow@xxxxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Stephen Hemminger <shemminger@xxxxxxxxxx>
- Re: [PATCH] add warnings enum-to-int and int-to-enum
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- [PATCH] add warnings enum-to-int and int-to-enum
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: sparse segv with simple test
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: sparse segv with simple test
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: sparse segv with simple test
- From: Stephen Hemminger <shemminger@xxxxxxxxxx>
- Re: sparse segv with simple test
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: sparse segv with simple test
- From: Stephen Hemminger <shemminger@xxxxxxxxxx>
- Re: sparse segv with simple test
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- sparse segv with simple test
- From: Stephen Hemminger <shemminger@xxxxxxxxxx>
- Re: [PATCH] do not ignore attribute 'noreturn'...
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH] do not ignore attribute 'noreturn'...
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: Fixing "cast truncates bits from constant value"
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Fixing "cast truncates bits from constant value"
- From: Pavel Roskin <proski@xxxxxxx>
- Re: Fixing "cast truncates bits from constant value"
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Fixing "cast truncates bits from constant value"
- From: Pavel Roskin <proski@xxxxxxx>
- Re: [PATCH] sparse: Add GCC pre-defined macros for user-space
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCH] sparse: Add GCC pre-defined macros for user-space
- From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
- Re: [PATCH] sparse: Add GCC pre-defined macros for user-space
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCH] sparse: Add GCC pre-defined macros for user-space
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] sparse: Add GCC pre-defined macros for user-space
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCH] sparse: Add GCC pre-defined macros for user-space
- From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
- Re: [PATCH] sparse: Add GCC pre-defined macros for user-space
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCH] sparse: Add GCC pre-defined macros for user-space
- From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
- Re: [PATCH] sparse: Add GCC pre-defined macros for user-space
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCH] sparse: Add GCC pre-defined macros for user-space
- From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
- Re: [PATCH] sparse: Add GCC pre-defined macros for user-space
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH] sparse: Add GCC pre-defined macros for user-space
- From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
- Re: [PATCH 0/2] Fix sparc64 and x86_64 issues
- From: Blue Swirl <blauwirbel@xxxxxxxxx>
- Re: [PATCH] make sparse headers self-compilable...
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] make sparse headers self-compilable...
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] make sparse headers self-compilable...
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] show_token: handle TOKEN_UNTAINT and TOKEN_ARG_COUNT types
- From: Chris Li <christ.li@xxxxxxxxx>
- Re: [PATCH] make sparse headers self-compilable...
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] make sparse headers self-compilable...
- From: Hannes Eder <hannes@xxxxxxxxxxxxxx>
- Re: [PATCH] unssa: track uses when replacing a phi node
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH] show_token: handle TOKEN_UNTAINT and TOKEN_ARG_COUNT types
- From: Reinhard Tartler <siretart@xxxxxxxxxx>
- Re: [PATCH] make sparse headers self-compilable...
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] make sparse headers self-compilable...
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] make sparse headers self-compilable...
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH 0/2] Fix sparc64 and x86_64 issues
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH] cse: treat PHI-nodes as other instructions
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- [PATCH] unssa: track uses when replacing a phi node
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] make sparse headers self-compilable...
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- [PATCH] make sparse headers self-compilable...
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH 0/2] Fix sparc64 and x86_64 issues
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH 0/2] Fix sparc64 and x86_64 issues
- From: Blue Swirl <blauwirbel@xxxxxxxxx>
- Re: [PATCH] linearize.h: sanitize header
- From: Hannes Eder <hannes@xxxxxxxxxxxxxx>
- Re: Detect unused header files?
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] linearize.h: sanitize header
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] linearize.h: sanitize header
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Detect unused header files?
- From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
- Re: Detect unused header files?
- From: Michael Stefaniuc <mstefani@xxxxxxxxxx>
- Re: Detect unused header files?
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: Detect unused header files?
- From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
- Re: Detect unused header files?
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: Detect unused header files?
- From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
- Re: Detect unused header files?
- From: Marko Kreen <markokr@xxxxxxxxx>
- Re: [PATCH] linearize.h: sanitize header
- From: Hannes Eder <hannes@xxxxxxxxxxxxxx>
- Re: [PATCH] linearize.h: sanitize header
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] linearize.h: sanitize header
- From: Hannes Eder <hannes@xxxxxxxxxxxxxx>
- Re: [PATCH] linearize.h: sanitize header
- From: Hannes Eder <hannes@xxxxxxxxxxxxxx>
- Re: [PATCH] linearize.h: sanitize header
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- [PATCH] linearize.h: sanitize header
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- [PATCH 2/2] Define __LP64__ for x86_64 unless in 32 bit mode
- From: Blue Swirl <blauwirbel@xxxxxxxxx>
- [PATCH 1/2] Add support for TImode type (__int128_t)
- From: Blue Swirl <blauwirbel@xxxxxxxxx>
- [PATCH 0/2] Fix sparc64 and x86_64 issues
- From: Blue Swirl <blauwirbel@xxxxxxxxx>
- Re: Question: attribute 'naked'
- From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
- Re: Question: attribute 'naked'
- From: Sam Ravnborg <sam@xxxxxxxxxxxx>
- Re: Detect unused header files?
- From: Sam Ravnborg <sam@xxxxxxxxxxxx>
- Re: Detect unused header files?
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH 2/2] Subject: Add a few GCC builtins
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH 2/2] Subject: Add a few GCC builtins
- From: Blue Swirl <blauwirbel@xxxxxxxxx>
- Re: [PATCH 2/2] Subject: Add a few GCC builtins
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH 2/2] Subject: Add a few GCC builtins
- From: Blue Swirl <blauwirbel@xxxxxxxxx>
- [PATCH 1/2, RESEND] Ignore attribute __bounded__, used by OpenBSD headers.
- From: Blue Swirl <blauwirbel@xxxxxxxxx>
- [PATCH 0/2] builtins and __bounded__ attribute
- From: Blue Swirl <blauwirbel@xxxxxxxxx>
- Re: Detect unused header files?
- From: Sam Ravnborg <sam@xxxxxxxxxxxx>
- Re: Detect unused header files?
- From: Derek M Jones <derek@xxxxxxxxxxxx>
- Re: Detect unused header files?
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Detect unused header files?
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Detect unused header files?
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Detect unused header files?
- From: Sam Ravnborg <sam@xxxxxxxxxxxx>
- Re: Detect unused header files?
- From: Sam Ravnborg <sam@xxxxxxxxxxxx>
- Re: Detect unused header files?
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Detect unused header files?
- From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
- Re: Detect unused header files?
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Detect unused header files?
- From: Sam Ravnborg <sam@xxxxxxxxxxxx>
- Re: [PATCH 5/5] Add a --version option to sparse
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] test-suite: integrate unhandled proprocessor tests
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH] test-suite: integrate unhandled proprocessor tests
- From: Hannes Eder <hannes@xxxxxxxxxxxxxx>
- Re: [PATCH 5/5] Add a --version option to sparse
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH 2/5] Fix some "enum value 'SYM_...' not handled in switch" warnings
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH 5/5] Add a --version option to sparse
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 3/5] Makefile: suppress error message from shell
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 2/5] Fix some "enum value 'SYM_...' not handled in switch" warnings
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 2/5] Fix some "enum value 'SYM_...' not handled in switch" warnings
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCH] compile-i386: do not generate an infinite loop
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] compile-i386: do not generate an infinite loop
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] compile-i386: do not generate an infinite loop
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] compile-i386: do not generate an infinite loop
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] compile-i386: do not generate an infinite loop
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- Re: [PATCH] compile-i386: do not generate an infinite loop
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] compile-i386: do not generate an infinite loop
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] compile-i386: do not generate an infinite loop
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- Re: [PATCH] compile-i386: do not generate an infinite loop
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- Re: [PATCH] compile-i386: do not generate an infinite loop
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH 5/5] Add a --version option to sparse
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH 4/5] Fix some "plain integer as NULL pointer" warnings on cygwin
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH 3/5] Makefile: suppress error message from shell
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH 2/5] Fix some "enum value 'SYM_...' not handled in switch" warnings
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH 4/5] Fix some "plain integer as NULL pointer" warnings on cygwin
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 3/5] Makefile: suppress error message from shell
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/5] Fix an "'__sentinel__' attribute directive ignored" warning
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 2/5] Fix some "enum value 'SYM_...' not handled in switch" warnings
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 4/5] Fix some "plain integer as NULL pointer" warnings on cygwin
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH 3/5] Makefile: suppress error message from shell
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH 1/5] Fix an "'__sentinel__' attribute directive ignored" warning
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH 3/5] Makefile: suppress error message from shell
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCH 2/5] Fix some "enum value 'SYM_...' not handled in switch" warnings
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Sparse official tree merged
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Multiple translation unit regression
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH] compile-i386: do not generate an infinite loop
- From: Kamil Dudka <kdudka@xxxxxxxxxx>
- [PATCH 5/5] Add a --version option to sparse
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- [PATCH 4/5] Fix some "plain integer as NULL pointer" warnings on cygwin
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- [PATCH 3/5] Makefile: suppress error message from shell
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- [PATCH 2/5] Fix some "enum value 'SYM_...' not handled in switch" warnings
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- [PATCH 1/5] Fix an "'__sentinel__' attribute directive ignored" warning
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- Re: Multiple translation unit regression
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] test-suite: be more verbose on 'unhandled' and 'known to fail' tests
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH] test-suite: be more verbose on 'unhandled' and 'known to fail' tests
- From: Hannes Eder <hannes@xxxxxxxxxxxxxx>
- Re: Multiple translation unit regression
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- Re: bitwise with memcpy and void*
- From: Christopher Li <sparse@xxxxxxxxxxx>
- bitwise with memcpy and void*
- From: "Robert Catherall" <Robert.Catherall@xxxxxxx>
- Re: Multiple translation unit regression
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Multiple translation unit regression
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] kmemcheck: fix sparse warning
- From: Bernd Petrovitsch <bernd@xxxxxxxxx>
- Re: [PATCH] kmemcheck: fix sparse warning
- From: Hannes Eder <hannes@xxxxxxxxxxxxxx>
- Re: [PATCH] kmemcheck: fix sparse warning
- From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
- Re: [PATCH] kmemcheck: fix sparse warning
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Multiple translation unit regression
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Multiple translation unit regression
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] kmemcheck: fix sparse warning
- From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
- Re: [PATCH] kmemcheck: fix sparse warning
- From: Vegard Nossum <vegard.nossum@xxxxxxxxx>
- Re: Multiple translation unit regression
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Multiple translation unit regression
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Multiple translation unit regression
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
- Re: Meet the new maintainer
- From: Chris Li <christ.li@xxxxxxxxx>
- Re: RFC: Move sparse.git inside linux-kernel-2.6.git?
- From: Josh Triplett <josh@xxxxxxxxxxxxxxx>
- Re: RFC: Move sparse.git inside linux-kernel-2.6.git?
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Sparse licensing
- From: Josh Triplett <josh@xxxxxxxxxx>
- Re: Meet the new maintainer
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- Meet the new maintainer
- From: Josh Triplett <josh@xxxxxxxxxx>
- Re: RFC: Move sparse.git inside linux-kernel-2.6.git?
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
- Re: RFC: Move sparse.git inside linux-kernel-2.6.git?
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: RFC: Move sparse.git inside linux-kernel-2.6.git?
- From: Samuel Bronson <naesten@xxxxxxxxx>
- Re: RFC: Move sparse.git inside linux-kernel-2.6.git?
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: RFC: Move sparse.git inside linux-kernel-2.6.git?
- From: Samuel Bronson <naesten@xxxxxxxxx>
- Re: RFC: Move sparse.git inside linux-kernel-2.6.git?
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: RFC: Move sparse.git inside linux-kernel-2.6.git?
- From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
- Re: RFC: Move sparse.git inside linux-kernel-2.6.git?
- From: Sam Ravnborg <sam@xxxxxxxxxxxx>
- Re: RFC: Move sparse.git inside linux-kernel-2.6.git?
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- Re: RFC: Move sparse.git inside linux-kernel-2.6.git?
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- RFC: Move sparse.git inside linux-kernel-2.6.git?
- From: Sam Ravnborg <sam@xxxxxxxxxxxx>
- Avoid "attribute 'warning': unknown attribute" warning
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Turn off '-Wtransparent-union' by default
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Allow array declarators to have 'restrict' in them
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH-v2 2/4] Replace SYM_ and MOD_ #defines with enums in symbol.h.
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH-v2 2/4] Replace SYM_ and MOD_ #defines with enums in symbol.h.
- From: Samuel Bronson <naesten@xxxxxxxxx>
- Re: [PATCH 4/4] Have Makefile import config.mak if it exists.
- From: Samuel Bronson <naesten@xxxxxxxxx>
- Re: [PATCH-v2 2/4] Replace SYM_ and MOD_ #defines with enums in symbol.h.
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH 4/4] Have Makefile import config.mak if it exists.
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH 4/4] Have Makefile import config.mak if it exists.
- From: Samuel Bronson <naesten@xxxxxxxxx>
- [PATCH-v2 2/4] Replace SYM_ and MOD_ #defines with enums in symbol.h.
- From: Samuel Bronson <naesten@xxxxxxxxx>
- Re: [PATCH 1/3] Add -*- gdb-script -*- to the top of gdbhelpers, for Emacs
- From: Samuel Bronson <naesten@xxxxxxxxx>
- Re: [PATCH 1/3] Add -*- gdb-script -*- to the top of gdbhelpers, for Emacs
- From: Alexey Zaytsev <alexey.zaytsev@xxxxxxxxx>
- Re: [PATCH 1/3] Add -*- gdb-script -*- to the top of gdbhelpers, for Emacs
- From: Samuel Bronson <naesten@xxxxxxxxx>
- Re: [PATCH 1/3] Add -*- gdb-script -*- to the top of gdbhelpers, for Emacs
- From: Alexey Zaytsev <alexey.zaytsev@xxxxxxxxx>
- Re: [PATCH 1/3] Add -*- gdb-script -*- to the top of gdbhelpers, for Emacs
- From: Anderson Lizardo <anderson.lizardo@xxxxxxxxx>
- Re: [PATCH 1/3] Add -*- gdb-script -*- to the top of gdbhelpers, for Emacs
- From: Samuel Bronson <naesten@xxxxxxxxx>
- Re: [PATCH 1/3] Add -*- gdb-script -*- to the top of gdbhelpers, for Emacs
- From: Alexey Zaytsev <alexey.zaytsev@xxxxxxxxx>
- Re: [PATCH 2/3] Replace SYM_ and MOD_ #defines with enums in symbol.h.
- From: Samuel Bronson <naesten@xxxxxxxxx>
- [PATCH 2/3] Replace SYM_ and MOD_ #defines with enums in symbol.h.
- From: Samuel Bronson <naesten@xxxxxxxxx>
- [PATCH 3/3] Whitespace tweaks in symbol.h
- From: Samuel Bronson <naesten@xxxxxxxxx>
- [PATCH 1/3] Add -*- gdb-script -*- to the top of gdbhelpers, for Emacs
- From: Samuel Bronson <naesten@xxxxxxxxx>
- pysparse: Python bindings for sparse
- From: Anderson Lizardo <anderson.lizardo@xxxxxxxxx>
- Re: [PATCH] Support the __thread storage class
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH] Support the __thread storage class
- From: Alberto Bertogli <albertito@xxxxxxxxxxxxxx>
- Re: `char * s = "abc";' causes compile to crash with a segfault
- From: David Given <dg@xxxxxxxxxxx>
- Re: `char * s = "abc";' causes compile to crash with a segfault
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: `char * s = "abc";' causes compile to crash with a segfault
- From: "Alexander Sorockin" <sorockin@xxxxxxxxx>
- Re: `char * s = "abc";' causes compile to crash with a segfault
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: `char * s = "abc";' causes compile to crash with a segfault
- From: David Given <dg@xxxxxxxxxxx>
- Re: [PATCH v2] sparse: add LLVM code generation backend
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- Re: `char * s = "abc";' causes compile to crash with a segfault
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- `char * s = "abc";' causes compile to crash with a segfault
- From: "Alexander Sorockin" <sorockin@xxxxxxxxx>
- Re: [PATCH v2] sparse: add LLVM code generation backend
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH v2] sparse: add LLVM code generation backend
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH v2] sparse: add LLVM code generation backend
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- Re: [PATCH v2] sparse: add LLVM code generation backend
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH v2] sparse: add LLVM code generation backend
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- Re: sparse: Why test-parse shows "+=" as a store?
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- Re: sparse: Why test-parse shows "+=" as a store?
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH v2] sparse: add LLVM code generation backend
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: sparse: Why test-parse shows "+=" as a store?
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- Re: [PATCH v2] sparse: add LLVM code generation backend
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- Re: [PATCH v2] sparse: add LLVM code generation backend
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: sparse: Why test-parse shows "+=" as a store?
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: sparse: Why test-parse shows "+=" as a store?
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: sparse: Why test-parse shows "+=" as a store?
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- Re: [PATCH] Print an error if typeof() lacks an argument
- From: Martin Nagy <mnagy@xxxxxxxxxx>
- Re: [PATCH] Support the __thread storage class
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] Print an error if typeof() lacks an argument
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] Add missing checks for Waddress-space
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: sparse: Why test-parse shows "+=" as a store?
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH] Support the __thread storage class
- From: Alberto Bertogli <albertito@xxxxxxxxxxxxxx>
- [PATCH v2] sparse: add LLVM code generation backend
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- sparse: Why test-parse shows "+=" as a store?
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- Re: [PATCH] Print an error if typeof() lacks an argument
- From: Martin Nagy <nagy.martin@xxxxxxxxx>
- [PATCH] Print an error if typeof() lacks an argument
- From: Martin Nagy <mnagy@xxxxxxxxxx>
- Re: [PATCH] Add missing checks for Waddress-space
- From: Martin Nagy <nagy.martin@xxxxxxxxx>
- Re: [PATCH] sparse LLVM backend
- From: David Miller <davem@xxxxxxxxxxxxx>
- [PATCH] sparse LLVM backend (was Re: [rfc] built-in native compiler for Linux?)
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- Re: [PATCH] Add missing checks for Waddress-space
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] .gitignore: Ignore dependencies and Vim swap files
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH] .gitignore: Ignore dependencies and Vim swap files
- From: Martin Nagy <nagy.martin@xxxxxxxxx>
- [PATCH] Add missing checks for Waddress-space
- From: Martin Nagy <nagy.martin@xxxxxxxxx>
- Re: Novafora relicenses Transmeta sparse copyrights under the MIT license
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Novafora relicenses Transmeta sparse copyrights under the MIT license
- From: David Given <dg@xxxxxxxxxxx>
- Re: Novafora relicenses Transmeta sparse copyrights under the MIT license
- From: Alexey Zaytsev <alexey.zaytsev@xxxxxxxxx>
- Re: Novafora relicenses Transmeta sparse copyrights under the MIT license
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Novafora relicenses Transmeta sparse copyrights under the MIT license
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
- Re: Nasal demons in preprocessor use (Re: [PATCH] test-suite: new preprocessor test case)
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
- Re: [bug, bisected, -chrisl] Segfault at evaluate.c:341
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: bitfields treatment
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: bitfields treatment
- From: Derek M Jones <derek@xxxxxxxxxxxx>
- Re: [bug, bisected, -chrisl] Segfault at evaluate.c:341
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: Nasal demons in preprocessor use (Re: [PATCH] test-suite: new preprocessor test case)
- From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
- Re: [bug, bisected, -chrisl] Segfault at evaluate.c:341
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: Nasal demons in preprocessor use (Re: [PATCH] test-suite: new preprocessor test case)
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: Nasal demons in preprocessor use (Re: [PATCH] test-suite: new preprocessor test case)
- From: Vegard Nossum <vegard.nossum@xxxxxxxxx>
- bitfields treatment
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: Nasal demons in preprocessor use (Re: [PATCH] test-suite: new preprocessor test case)
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: Nasal demons in preprocessor use (Re: [PATCH] test-suite: new preprocessor test case)
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: Nasal demons in preprocessor use (Re: [PATCH] test-suite: new preprocessor test case)
- From: Ingo Molnar <mingo@xxxxxxx>
- [Patch] warning for preprocessor directive in macro Was: Segfault at evaluate.c:341
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [bug, bisected, -chrisl] Segfault at evaluate.c:341
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [bug, bisected, -chrisl] Segfault at evaluate.c:341
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: Nasal demons in preprocessor use (Re: [PATCH] test-suite: new preprocessor test case)
- From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
- Re: [bug, bisected, -chrisl] Segfault at evaluate.c:341
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: Nasal demons in preprocessor use (Re: [PATCH] test-suite: new preprocessor test case)
- From: Vegard Nossum <vegard.nossum@xxxxxxxxx>
- Re: [bug, bisected, -chrisl] Segfault at evaluate.c:341
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: Nasal demons in preprocessor use (Re: [PATCH] test-suite: new preprocessor test case)
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: Nasal demons in preprocessor use (Re: [PATCH] test-suite: new preprocessor test case)
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [PATCH] test-suite: new preprocessor test case
- From: Derek M Jones <derek@xxxxxxxxxxxx>
- Re: [bug, bisected, -chrisl] Segfault at evaluate.c:341
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Nasal demons in preprocessor use (Re: [PATCH] test-suite: new preprocessor test case)
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] test-suite: new preprocessor test case
- From: Hannes Eder <hannes@xxxxxxxxxxxxxx>
- Re: [bug, bisected, -chrisl] Segfault at evaluate.c:341
- From: Nicholas Mc Guire <der.herr@xxxxxxx>
- Re: [bug, bisected, -chrisl] Segfault at evaluate.c:341
- From: Hannes Eder <hannes@xxxxxxxxxxxxxx>
- Re: [PATCH] test-suite: new preprocessor test case
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- [PATCH] test-suite: new preprocessor test case
- From: Hannes Eder <hannes@xxxxxxxxxxxxxx>
- Re: [bug, bisected, -chrisl] Segfault at evaluate.c:341
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- [bug, bisected, -chrisl] Segfault at evaluate.c:341
- From: Hannes Eder <hannes@xxxxxxxxxxxxxx>
- Re: [RFC] potential DR in handling of signed int and unholy mess in our and gcc implementations
- From: Derek M Jones <derek@xxxxxxxxxxxx>
- Re: [RFC] potential DR in handling of signed int and unholy mess in our and gcc implementations
- From: David Given <dg@xxxxxxxxxxx>
- [RFC] potential DR in handling of signed int and unholy mess in our and gcc implementations
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: Braino in attribute_packed()
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Braino in attribute_packed()
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- Sanitize pointer()
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- Don't mix storage class bits with ctype->modifiers while parsing type
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- Simplify get_number_value() and ctype_integer()
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- Re: [patches] more declarations fixes
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: [patches] more declarations fixes
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [patches] more declarations fixes
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Fix __label__ handling
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- Fix declaration_specifiers() handling of typedef name shadowed by NS_SYMBOL
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- Fix enumeration constants' scope beginning
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- Re: [patches] more declarations fixes
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: [patches] more declarations fixes
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH 18/18] Restore __attribute__((mode)) handling
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 17/18] Pass decl_state down to ->attribute()
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 16/18] Pass decl_state down to ->declarator() and handle_attributes()
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 15/18] Clean up and split declaration_specifiers()
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 14/18] Have ->declarator() act directly on ctype being affected
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 13/18] Rewrite and fix specifiers handling
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 12/18] Saner type for __builtin_va_list
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 11/18] Take the rest of specifiers to parse.c
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 10/18] preparations to ->declarator() cleanup - separate typedef handling
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 9/18] Fix handling of typedefs with several declarators
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 8/18] Take the rest of storage class keywords to parse.c
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 7/18] Fix regression created by commit af30c6df74f01db10fa78ac0cbdb5c3c40b5c73f
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 6/18] Propagate decl_state to declaration_specifiers()
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 5/18] Separating ctype and parser state, part 1
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 4/18] Sanitize direct_declarator logics
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 3/18] Fix braino in which_kind()
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 2/18] Don't mess with passing symbol to declarator/direct_declarator
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 1/18] Leave applying attributes until we know whether it's a nested declarator
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [patches] more declarations fixes
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH] Ignore attribute __bounded__
- From: Blue Swirl <blauwirbel@xxxxxxxxx>
- Declarations with typedef (Was: Re: Messing typedefs?)
- From: Thomas Schmid <Thomas.Schmid@xxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/7] Fix handling of ident-less declarations
- From: Christopher Li <sparse@xxxxxxxxxxx>
- smatch_implied.c
- From: Dan Carpenter <error27@xxxxxxxxx>
- Re: [PATCH 1/7] Fix handling of ident-less declarations
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/7] Fix handling of ident-less declarations
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/7] Fix handling of ident-less declarations
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/7] Fix handling of ident-less declarations
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH 7/7] Apply attributes after ( to the right place
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 6/7] Warn about non-empty identifier list outside of definition
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 5/7] more direct_declarator() sanitizing
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 4/7] Fix attribute/asm handling
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 3/7] More nested declarator fixes
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 2/7] Separate parsing of identifier-list (in K&R-style declarations)
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- [PATCH 1/7] Fix handling of ident-less declarations
- From: Al Viro <viro@xxxxxxxxxxxxxxxx>
- Re: Re: [PATCH] Fix implicit cast to float (Was:Re: Initializing float variables without type suffix)
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Antwort: Re: [PATCH] Fix implicit cast to float (Was:Re: Initializing float variables without type suffix)
- From: Thomas Schmid <Thomas.Schmid@xxxxxxxxxxxxxxxxx>
- Re: fun with declarations and definitions
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: fun with declarations and definitions
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] Fix implicit cast to float (Was:Re: Initializing float variables without type suffix)
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH] Fix implicit cast to float (Was:Re: Initializing float variables without type suffix)
- From: Thomas Schmid <Thomas.Schmid@xxxxxxxxxxxxxxxxx>
- Re: fun with declarations and definitions
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: Initializing float variables without type suffix
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: fun with declarations and definitions
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: fun with declarations and definitions
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: fun with declarations and definitions
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: fun with declarations and definitions
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Fix type_info_expression()
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] Fix type_info_expression()
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: fun with declarations and definitions
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: fun with declarations and definitions
- From: Derek M Jones <derek@xxxxxxxxxxxx>
- Re: fun with declarations and definitions
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: [PATCH] Fix type_info_expression()
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Initializing float variables without type suffix
- From: Thomas Schmid <Thomas.Schmid@xxxxxxxxxxxxxxxxx>
- Re: fun with declarations and definitions
- From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
- Re: fun with declarations and definitions
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: fun with declarations and definitions
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: fun with declarations and definitions
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: fun with declarations and definitions
- From: Christopher Li <sparse@xxxxxxxxxxx>
- Re: fun with declarations and definitions
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: fun with declarations and definitions
- From: Christopher Li <sparse@xxxxxxxxxxx>
- [PATCH] Fix type_info_expression()
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- fun with declarations and definitions
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: source code transform
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
- Re: [PATCH] Add -fno-show-column
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- [PATCH] Add -fno-show-column
- From: Hannes Eder <hannes@xxxxxxxxxxxxxx>
- Re: source code transform
- From: Yoann Padioleau <padator@xxxxxxxxxx>
- Re: [PATCH] refactor handle_switch_f
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: source code transform
- From: Harvey Harrison <harvey.harrison@xxxxxxxxx>
- Re: source code transform
- From: Yoann Padioleau <padator@xxxxxxxxxx>
- [PATCH] refactor handle_switch_f
- From: Hannes Eder <hannes@xxxxxxxxxxxxxx>
- Re: [PATCH v3] Add -ftabstop=WIDTH
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- [PATCH v3] Add -ftabstop=WIDTH
- From: Hannes Eder <hannes@xxxxxxxxxxxxxx>
- Re: source code transform
- From: Nicholas Mc Guire <hofrat@xxxxxxx>
- Re: source code transform
- From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
- source code transform
- From: mosfet <forumer@xxxxxxxxxxxxxxx>
- Re: lock context warnings
- From: Christoph Hellwig <hch@xxxxxx>
- Re: lock context warnings
- From: "Alexey Zaytsev" <alexey.zaytsev@xxxxxxxxx>
- lock context warnings
- From: Christoph Hellwig <hch@xxxxxx>
- Re: [PATCH v2] Add -ftabstop=WIDTH
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH v2] Add -ftabstop=WIDTH
- From: Junio C Hamano <junio@xxxxxxxxx>
- Re: [PATCH v2] Add -ftabstop=WIDTH
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH v2] Add -ftabstop=WIDTH
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH v2] Add -ftabstop=WIDTH
- From: Junio C Hamano <junio@xxxxxxxxx>
- Re: [PATCH v2] Add -ftabstop=WIDTH
- From: "Hannes Eder" <hannes@xxxxxxxxxxxxxx>
- Re: [PATCH] Add -ftabstop=WIDTH
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH] Add -ftabstop=WIDTH
- From: "Alexey Zaytsev" <alexey.zaytsev@xxxxxxxxx>
- [PATCH] Add -ftabstop=WIDTH
- From: Hannes Eder <hannes@xxxxxxxxxxxxxx>
- Re: [PATCH] Null ctype should have ptr_ctype as its base type.
- From: "Alexey Zaytsev" <alexey.zaytsev@xxxxxxxxx>
- Re: [PATCH] Null ctype should have ptr_ctype as its base type.
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH] Null ctype should have ptr_ctype as its base type.
- From: "Alexey Zaytsev" <alexey.zaytsev@xxxxxxxxx>
- Re: [PATCH] Null ctype should have ptr_ctype as its base type.
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: My sparse repository
- From: "Alexey Zaytsev" <alexey.zaytsev@xxxxxxxxx>
- [PATCH] Null ctype should have ptr_ctype as its base type.
- From: Alexey Zaytsev <alexey.zaytsev@xxxxxxxxx>
- [PATCH]: clean up Makefile long lines
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: My sparse repository
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH] Also warn about sizeof(function)
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH]: Makefile automatic header dependency
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: My sparse repository
- From: "Alexey Zaytsev" <alexey.zaytsev@xxxxxxxxx>
- [PATCH] Also warn about sizeof(function)
- From: Alexey Zaytsev <alexey.zaytsev@xxxxxxxxx>
- Re: [PATCH] Warn about explicit usage of sizeof(void) and sizeof(function)
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH] Warn about explicit usage of sizeof(void)
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- [PATCH] Warn about explicit usage of sizeof(void) and sizeof(function)
- From: Alexey Zaytsev <alexey.zaytsev@xxxxxxxxx>
- Re: [PATCH] Warn about explicit usage of sizeof(void)
- From: Tommy Thorn <tommy@xxxxxxxxxxxx>
- Re: [PATCH 7/16] Let void have sizeof 1
- From: "Alexey Zaytsev" <alexey.zaytsev@xxxxxxxxx>
- Re: [PATCH]: Makefile automatic header dependency
- From: Sam Ravnborg <sam@xxxxxxxxxxxx>
- [PATCH]: Makefile automatic header dependency
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- [PATCH] Warn about explicit usage of sizeof(void)
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH 7/16] Let void have sizeof 1
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH 7/16] Let void have sizeof 1
- From: Derek M Jones <derek@xxxxxxxxxxxx>
- Re: [PATCH 03/15] Add type information to struct instruction.
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH 7/16] Let void have sizeof 1
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH 03/15] Add type information to struct instruction.
- From: David Given <dg@xxxxxxxxxxx>
- Re: [PATCH 7/16] Let void have sizeof 1
- From: David Given <dg@xxxxxxxxxxx>
- My sparse repository
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: Casting away noderef and address spaces?
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH 03/15] Add type information to struct instruction.
- From: "Alexey Zaytsev" <alexey.zaytsev@xxxxxxxxx>
- Re: [PATCH 03/15] Add type information to struct instruction.
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH 7/16] Let void have sizeof 1
- From: "Alexey Zaytsev" <alexey.zaytsev@xxxxxxxxx>
- Re: [PATCH 7/16] Let void have sizeof 1
- From: Derek M Jones <derek@xxxxxxxxxxxx>
- Re: [PATCH 7/16] Let void have sizeof 1
- From: "Alexey Zaytsev" <alexey.zaytsev@xxxxxxxxx>
- Re: [PATCH 03/15] Add type information to struct instruction.
- From: David Given <dg@xxxxxxxxxxx>
- Re: Casting away noderef and address spaces?
- From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
- Re: [PATCH 7/16] Let void have sizeof 1
- From: Derek M Jones <derek@xxxxxxxxxxxx>
- Re: [PATCH 7/16] Let void have sizeof 1
- From: "Alexey Zaytsev" <alexey.zaytsev@xxxxxxxxx>
- Re: [PATCH 7/16] Let void have sizeof 1
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH 03/15] Add type information to struct instruction.
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH 7/16] Let void have sizeof 1
- From: "Alexey Zaytsev" <alexey.zaytsev@xxxxxxxxx>
- Re: [PATCH 03/15] Add type information to struct instruction.
- From: "Alexey Zaytsev" <alexey.zaytsev@xxxxxxxxx>
- Re: [PATCH 7/16] Let void have sizeof 1
- From: "Alexey Zaytsev" <alexey.zaytsev@xxxxxxxxx>
- Re: [PATCH 7/16] Let void have sizeof 1
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: [PATCH 03/15] Add type information to struct instruction.
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: Casting away noderef and address spaces?
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: Casting away noderef and address spaces?
- From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
- Re: Casting away noderef and address spaces?
- From: "Christopher Li" <sparse@xxxxxxxxxxx>
- Re: Casting away noderef and address spaces?
- From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
- Re: Casting away noderef and address spaces?
- From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
- Re: Casting away noderef and address spaces?
- From: "Alexey Zaytsev" <alexey.zaytsev@xxxxxxxxx>
- Re: Casting away noderef and address spaces?
- From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
- Re: Casting away noderef and address spaces?
- From: "Alexey Zaytsev" <alexey.zaytsev@xxxxxxxxx>
- Re: Casting away noderef and address spaces?
- From: Sam Ravnborg <sam@xxxxxxxxxxxx>
[Index of Archives]
[Trinity Fuzzer Tool]
[Linux Kernel]
[Netdev]
[IETF Annouce]
[Security]
[Bugtraq]
