* [GIT PULL] pending fixes for sparse's next release
@ 2017-04-30 3:41 Luc Van Oostenryck
2017-05-01 14:51 ` Christopher Li
2017-05-03 22:04 ` Christopher Li
0 siblings, 2 replies; 7+ messages in thread
From: Luc Van Oostenryck @ 2017-04-30 3:41 UTC (permalink / raw)
To: Christopher Li; +Cc: linux-sparse
Hi Chris,
Please pull these patches for sparse's next release.
They are fixes, for sparse itself, but also for the testsuite
which contained test cases that failed on 32bit machines.
Regards,
Luc
--->8
The following changes since commit 14964df5373292af78b29529d4fc7e1a26b67a97:
avoid crash with test-linearize -vv (2017-03-31 13:14:17 +0800)
are available in the git repository at:
git://github.com/lucvoo/sparse.git tags/fixes-for-stable-20170430
for you to fetch changes up to e35efe330c6ae7d154197c29b127560d569016d0:
Merge branches 'sent/float-expand-v2', 'sent/fix-kill-ttsb-v2', 'sent/fix-cond-address' and 'careful-concat-user-list' into tip (2017-04-30 02:08:54 +0200)
----------------------------------------------------------------
Pending fixes for sparse's next release
----------------------------------------------------------------
Luc Van Oostenryck (17):
teach sparse about -Waddress
add is_func_type()
warn if testing the address of a function
add is_array_type()
warn if testing the address of an array
fix evaluation of a function or array symbol in conditionals
fix is_scalar_type()
fix test for cast to bool on 32bit machines
predefine __INT_MAX__ and friends
predefine __SIZEOF_INT__ & friends
fix test validation/div.c
do not depends on limits.h to test __CHAR_BIT__
fix cast to pointer to floating-point
fix expansion of integers to floats
fix OP_PHI usage in try_to_simplify_bb(), correctly
be more careful with concat_user_list()
Merge branches 'sent/float-expand-v2', 'sent/fix-kill-ttsb-v2', 'sent/fix-cond-address' and 'careful-concat-user-list' into tip
evaluate.c | 9 +-
expand.c | 3 +-
flow.c | 33 ++-
lib.c | 35 ++-
lib.h | 1 +
linearize.c | 3 +-
symbol.h | 16 +-
validation/bool-cast-explicit.c | 2 +-
validation/bool-cast-implicit.c | 2 +-
validation/builtin_char_bit.c | 7 -
validation/cast-constant-to-float.c | 35 +++
validation/cast-constants.c | 357 ++++++++++++++++++++++++++++++
validation/cond-address-array.c | 26 +++
validation/cond-address-function.c | 18 ++
validation/cond-address.c | 14 ++
validation/div.c | 22 +-
validation/fp-vs-ptrcast.c | 13 ++
validation/kill-phi-ttsbb2.c | 40 ++++
validation/preprocessor/predef-char-bit.c | 16 ++
validation/preprocessor/predef-max.c | 18 ++
validation/preprocessor/predef-sizeof.c | 25 +++
21 files changed, 662 insertions(+), 33 deletions(-)
delete mode 100644 validation/builtin_char_bit.c
create mode 100644 validation/cast-constant-to-float.c
create mode 100644 validation/cast-constants.c
create mode 100644 validation/cond-address-array.c
create mode 100644 validation/cond-address-function.c
create mode 100644 validation/cond-address.c
create mode 100644 validation/fp-vs-ptrcast.c
create mode 100644 validation/kill-phi-ttsbb2.c
create mode 100644 validation/preprocessor/predef-char-bit.c
create mode 100644 validation/preprocessor/predef-max.c
create mode 100644 validation/preprocessor/predef-sizeof.c
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [GIT PULL] pending fixes for sparse's next release
2017-04-30 3:41 [GIT PULL] pending fixes for sparse's next release Luc Van Oostenryck
@ 2017-05-01 14:51 ` Christopher Li
2017-05-03 22:04 ` Christopher Li
1 sibling, 0 replies; 7+ messages in thread
From: Christopher Li @ 2017-05-01 14:51 UTC (permalink / raw)
To: Luc Van Oostenryck; +Cc: Linux-Sparse
Thanks,
I will take a look today.
Chris
On Sat, Apr 29, 2017 at 11:41 PM, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
> Hi Chris,
>
> Please pull these patches for sparse's next release.
> They are fixes, for sparse itself, but also for the testsuite
> which contained test cases that failed on 32bit machines.
>
> Regards,
> Luc
>
> --->8
>
> The following changes since commit 14964df5373292af78b29529d4fc7e1a26b67a97:
>
> avoid crash with test-linearize -vv (2017-03-31 13:14:17 +0800)
>
> are available in the git repository at:
>
> git://github.com/lucvoo/sparse.git tags/fixes-for-stable-20170430
>
> for you to fetch changes up to e35efe330c6ae7d154197c29b127560d569016d0:
>
> Merge branches 'sent/float-expand-v2', 'sent/fix-kill-ttsb-v2', 'sent/fix-cond-address' and 'careful-concat-user-list' into tip (2017-04-30 02:08:54 +0200)
>
> ----------------------------------------------------------------
> Pending fixes for sparse's next release
>
> ----------------------------------------------------------------
> Luc Van Oostenryck (17):
> teach sparse about -Waddress
> add is_func_type()
> warn if testing the address of a function
> add is_array_type()
> warn if testing the address of an array
> fix evaluation of a function or array symbol in conditionals
> fix is_scalar_type()
> fix test for cast to bool on 32bit machines
> predefine __INT_MAX__ and friends
> predefine __SIZEOF_INT__ & friends
> fix test validation/div.c
> do not depends on limits.h to test __CHAR_BIT__
> fix cast to pointer to floating-point
> fix expansion of integers to floats
> fix OP_PHI usage in try_to_simplify_bb(), correctly
> be more careful with concat_user_list()
> Merge branches 'sent/float-expand-v2', 'sent/fix-kill-ttsb-v2', 'sent/fix-cond-address' and 'careful-concat-user-list' into tip
>
> evaluate.c | 9 +-
> expand.c | 3 +-
> flow.c | 33 ++-
> lib.c | 35 ++-
> lib.h | 1 +
> linearize.c | 3 +-
> symbol.h | 16 +-
> validation/bool-cast-explicit.c | 2 +-
> validation/bool-cast-implicit.c | 2 +-
> validation/builtin_char_bit.c | 7 -
> validation/cast-constant-to-float.c | 35 +++
> validation/cast-constants.c | 357 ++++++++++++++++++++++++++++++
> validation/cond-address-array.c | 26 +++
> validation/cond-address-function.c | 18 ++
> validation/cond-address.c | 14 ++
> validation/div.c | 22 +-
> validation/fp-vs-ptrcast.c | 13 ++
> validation/kill-phi-ttsbb2.c | 40 ++++
> validation/preprocessor/predef-char-bit.c | 16 ++
> validation/preprocessor/predef-max.c | 18 ++
> validation/preprocessor/predef-sizeof.c | 25 +++
> 21 files changed, 662 insertions(+), 33 deletions(-)
> delete mode 100644 validation/builtin_char_bit.c
> create mode 100644 validation/cast-constant-to-float.c
> create mode 100644 validation/cast-constants.c
> create mode 100644 validation/cond-address-array.c
> create mode 100644 validation/cond-address-function.c
> create mode 100644 validation/cond-address.c
> create mode 100644 validation/fp-vs-ptrcast.c
> create mode 100644 validation/kill-phi-ttsbb2.c
> create mode 100644 validation/preprocessor/predef-char-bit.c
> create mode 100644 validation/preprocessor/predef-max.c
> create mode 100644 validation/preprocessor/predef-sizeof.c
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [GIT PULL] pending fixes for sparse's next release
2017-04-30 3:41 [GIT PULL] pending fixes for sparse's next release Luc Van Oostenryck
2017-05-01 14:51 ` Christopher Li
@ 2017-05-03 22:04 ` Christopher Li
2017-05-03 22:30 ` Luc Van Oostenryck
1 sibling, 1 reply; 7+ messages in thread
From: Christopher Li @ 2017-05-03 22:04 UTC (permalink / raw)
To: Luc Van Oostenryck; +Cc: Linux-Sparse
On Sat, Apr 29, 2017 at 11:41 PM, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
> Hi Chris,
>
> Please pull these patches for sparse's next release.
> They are fixes, for sparse itself, but also for the testsuite
> which contained test cases that failed on 32bit machines.
Merged and push to sparse-next.
Chris
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [GIT PULL] pending fixes for sparse's next release
2017-05-03 22:04 ` Christopher Li
@ 2017-05-03 22:30 ` Luc Van Oostenryck
2017-05-04 1:37 ` Christopher Li
0 siblings, 1 reply; 7+ messages in thread
From: Luc Van Oostenryck @ 2017-05-03 22:30 UTC (permalink / raw)
To: Christopher Li; +Cc: Linux-Sparse
On Wed, May 03, 2017 at 06:04:19PM -0400, Christopher Li wrote:
> On Sat, Apr 29, 2017 at 11:41 PM, Luc Van Oostenryck
> <luc.vanoostenryck@gmail.com> wrote:
> > Hi Chris,
> >
> > Please pull these patches for sparse's next release.
> > They are fixes, for sparse itself, but also for the testsuite
> > which contained test cases that failed on 32bit machines.
>
> Merged and push to sparse-next.
>
> Chris
OK, thanks.
I see it as 'sparse-next-20170501' while 'sparse-next' contains
(a27c14511 "Add more declarations for more builtin functions").
Is it like this it should be?
-- Luc
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [GIT PULL] pending fixes for sparse's next release
2017-05-03 22:30 ` Luc Van Oostenryck
@ 2017-05-04 1:37 ` Christopher Li
2017-05-04 11:44 ` Luc Van Oostenryck
0 siblings, 1 reply; 7+ messages in thread
From: Christopher Li @ 2017-05-04 1:37 UTC (permalink / raw)
To: Luc Van Oostenryck; +Cc: Linux-Sparse
On Wed, May 3, 2017 at 6:30 PM, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
>
> I see it as 'sparse-next-20170501' while 'sparse-next' contains
> (a27c14511 "Add more declarations for more builtin functions").
> Is it like this it should be?
Oh, no. Thanks for the catch.
I did not reset sparse-next properly. Let me redo it.
Chris
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [GIT PULL] pending fixes for sparse's next release
2017-05-04 1:37 ` Christopher Li
@ 2017-05-04 11:44 ` Luc Van Oostenryck
2017-05-04 13:37 ` Christopher Li
0 siblings, 1 reply; 7+ messages in thread
From: Luc Van Oostenryck @ 2017-05-04 11:44 UTC (permalink / raw)
To: Christopher Li; +Cc: Linux-Sparse
On Wed, May 03, 2017 at 09:37:17PM -0400, Christopher Li wrote:
> On Wed, May 3, 2017 at 6:30 PM, Luc Van Oostenryck
> <luc.vanoostenryck@gmail.com> wrote:
> >
> > I see it as 'sparse-next-20170501' while 'sparse-next' contains
> > (a27c14511 "Add more declarations for more builtin functions").
> > Is it like this it should be?
>
> Oh, no. Thanks for the catch.
>
> I did not reset sparse-next properly. Let me redo it.
It's good now. Thanks.
I'll check if there is any pending fixes that should go in.
I think there may be two that should but important ones are
already in now.
Is there anything else than fixes that you would like to see
in the coming release?
Maybe you can already 'promote' to master the previous -next
(14964df53 "avoid crash with test-linearize -vv")?
-- Luc
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [GIT PULL] pending fixes for sparse's next release
2017-05-04 11:44 ` Luc Van Oostenryck
@ 2017-05-04 13:37 ` Christopher Li
0 siblings, 0 replies; 7+ messages in thread
From: Christopher Li @ 2017-05-04 13:37 UTC (permalink / raw)
To: Luc Van Oostenryck; +Cc: Linux-Sparse
On Thu, May 4, 2017 at 7:44 AM, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
> Is there anything else than fixes that you would like to see
> in the coming release?
Let me check.
> Maybe you can already 'promote' to master the previous -next
> (14964df53 "avoid crash with test-linearize -vv")?
Yes, I want to do that too.
Chris
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2017-05-04 13:37 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-04-30 3:41 [GIT PULL] pending fixes for sparse's next release Luc Van Oostenryck
2017-05-01 14:51 ` Christopher Li
2017-05-03 22:04 ` Christopher Li
2017-05-03 22:30 ` Luc Van Oostenryck
2017-05-04 1:37 ` Christopher Li
2017-05-04 11:44 ` Luc Van Oostenryck
2017-05-04 13:37 ` Christopher Li
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.