Skip to content

Conversation

@yuyichao
Copy link
Contributor

@yuyichao yuyichao commented Jun 6, 2017

The change to isassigned(::SimpleVector, ...) and isassigned(::BitArray, ...)
are currently no op since they will unlikely be inlined.
The SimpleVector version is also currently unsafe to inline.
These might change with a better inlining heuristic (#22210) and a smarter GC frame
allocation pass (#21888).

The change to `isassigned(::SimpleVector, ...)` and `isassigned(::BitArray, ...)`
are currently no op since they will unlikely be inlined.
The `SimpleVector` version is also currently unsafe to inline.
These might change with a better inlining heuristic (#22210) and a smarter GC frame
allocation pass (#21888).
@yuyichao
Copy link
Contributor Author

yuyichao commented Jun 7, 2017

Comments?

@tkelman
Copy link
Contributor

tkelman commented Jun 7, 2017

why not? @nanosoldier runbenchmarks(ALL, vs = ":master")

@nanosoldier
Copy link
Collaborator

Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @jrevels

@yuyichao
Copy link
Contributor Author

yuyichao commented Jun 7, 2017

The difference looks like noise. I don't think there's actually any functions that uses isassigned....

@yuyichao yuyichao merged commit 0061f2a into master Jun 8, 2017
@yuyichao yuyichao deleted the yyc/isassigned-boundscheck branch June 8, 2017 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants