Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

enable inline allocation of structs with pointers #34126

Merged
merged 1 commit into from
Apr 27, 2020

Conversation

JeffBezanson
Copy link
Sponsor Member

No description provided.

@JeffBezanson
Copy link
Sponsor Member Author

@nanosoldier runtests(ALL, vs = ":master")

@nanosoldier
Copy link
Collaborator

Something went wrong when running your job:

NanosoldierError: error when preparing/pushing to report repo: failed process: Process(`git push`, ProcessExited(128)) [128]

Unfortunately, the logs could not be uploaded.
cc @maleadt

@maleadt
Copy link
Member

maleadt commented Dec 18, 2019

Ah, forgot to add Nanosoldier as a repository collaborator after switching to his account... I pushed the report manually: https://github.com/maleadt/BasePkgEvalReports/blob/master/pkgeval-86ae65b_vs_630a551/report.md (and it's segfault-o-clock).

@JeffBezanson
Copy link
Sponsor Member Author

@nanosoldier runtests(ALL, vs = ":master")

@nanosoldier
Copy link
Collaborator

Your test job has completed - possible new issues were detected. A full report can be found here. cc @maleadt

@vtjnash
Copy link
Sponsor Member

vtjnash commented Dec 20, 2019

Working through this list, will update as I learn more:

time limited:
HTTP v0.8.8 (test duration exceeded the time limit, but works for me)

numeric and other problems with tests as written (these should be filed as issues against their respective packages):
AIBECS v0.4.1 (doesn't work locally)
Bridge v0.10.0
FastIOBuffers v0.3.1
KissMCMC v0.2.0 # confirmed flaky
LazyArrays v0.14.10
Nabla v0.12.1
PushVectors v0.2.0
SpatialJackknife v1.0.1

@JeffBezanson
Copy link
Sponsor Member Author

@nanosoldier runtests(ALL, vs = ":master")

@nanosoldier
Copy link
Collaborator

Your test job has completed - possible new issues were detected. A full report can be found here. cc @maleadt

@vtjnash
Copy link
Sponsor Member

vtjnash commented Dec 24, 2019

Unfortunately that didn't include #34186 or #34176, so it's not especially useful. AIBECS is still probably worth looking into, but fails when I try to run it locally. RoME and OhMyREPL might be interesting (appear to have hit a deadlock inside Pkg).

@JeffBezanson JeffBezanson added this to the 1.5 milestone Jan 15, 2020
@KristofferC
Copy link
Sponsor Member

OhMyREPL might be interesting (appear to have hit a deadlock inside Pkg).

I've seen it deadlock sometimes in PkgEval. My guess is that it is this test that hangs: https://github.com/KristofferC/OhMyREPL.jl/blob/70927549f78591e9b572714b5ed5b8e3a25f795a/test/flicker.jl#L5-L19. It is most likely unrelated to this PR though.

@JeffBezanson
Copy link
Sponsor Member Author

@nanosoldier runtests(ALL, vs = ":master")

@nanosoldier
Copy link
Collaborator

Your package evaluation job has completed - possible new issues were detected. A full report can be found here. cc @maleadt

@JeffBezanson
Copy link
Sponsor Member Author

JeffBezanson commented Mar 27, 2020

Found the issue in EfficientGlobalOptimization. NLopt has an array of immutable structs of two pointers (references) each (Callback_Data). It passes those objects to C for use as callback closure pointers, but they no longer have persistent addresses. That will need to be fixed by making the structs mutable.

@JeffBezanson
Copy link
Sponsor Member Author

@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 @ararslan

@vtjnash
Copy link
Sponsor Member

vtjnash commented Apr 20, 2020

That's looking super. Only one I wondered about (if it's real) was:

["string", "repeat", "repeat char 2"] | 1.74 (5%) ❌ | 1.00 (1%)

@JeffBezanson
Copy link
Sponsor Member Author

It looks like repeat char 2 is a really fast benchmark (~160ns). I don't see any difference locally.

@JeffBezanson JeffBezanson merged commit 8073ddf into master Apr 27, 2020
@JeffBezanson JeffBezanson deleted the jb/enable_inline_alloc branch April 27, 2020 17:20
@quinnj
Copy link
Member

quinnj commented Apr 28, 2020

Exciting!!

mbauman added a commit that referenced this pull request Apr 28, 2020
* origin/master: (833 commits)
  Improve typesubtract for tuples (#35600)
  Make searchsorted*/findnext/findprev return values of keytype (#32978)
  fix buggy rand(RandomDevice(), Bool) (#35590)
  remove `Ref` allocation on task switch (#35606)
  Revert "partr: fix multiqueue resorting stability" (#35589)
  exclude types with free variables from `type_morespecific` (#35555)
  fix small typo in NEWS.md (#35611)
  enable inline allocation of structs with pointers (#34126)
  SparseArrays: Speed up right-division by diagonal matrices (#35533)
  Allow hashing 1D OffsetArrays
  NEWS item for introspection macros (#35594)
  Special case empty covec-diagonal-vec product (#35557)
  [GCChecker] fix a few tests by looking through casts
  Use norm instead of abs in generic lu factorization (#34575)
  [GCChecker,NFC] run clang-format -style=llvm
  [GCChecker] fix tests and add Makefile
  Add introspection macros support for dot syntax (#35522)
  Specialize `union` for `OneTo` (#35577)
  add pop!(vector, idx, [default]) (#35513)
  bump Pkg version (#35584)
  ...
@oschulz
Copy link
Contributor

oschulz commented May 3, 2020

From what I understand, this would close #14955, @JeffBezanson ? If so, I'd update the docs of UnsafeArrays, which I guess would then be largely obsolete when using Julia v1.5. This is exciting!

@JeffBezanson
Copy link
Sponsor Member Author

Yes. Would be interesting to see how performance now compares with a non-trivial use of UnsafeArrays.

vtjnash added a commit that referenced this pull request May 7, 2020
And add load/store alignment annotations, because LLVM now prefers that
we try to specify those explicitly, even though it's not required.

This does not yet include correct load/store behaviors for objects with
inlined references (the recent #34126 PR).
@oschulz
Copy link
Contributor

oschulz commented May 29, 2020

@JeffBezanson , it's not a very involved benchmark, but looks like the result is dramatic, in a very positive way: JuliaArrays/UnsafeArrays.jl#8

vtjnash added a commit that referenced this pull request Jul 1, 2020
And add load/store alignment annotations, because LLVM now prefers that
we try to specify those explicitly, even though it's not required.

This does not yet include correct load/store behaviors for objects with
inlined references (the recent #34126 PR).
vtjnash added a commit that referenced this pull request Jul 1, 2020
And add load/store alignment annotations, because LLVM now prefers that
we try to specify those explicitly, even though it's not required.

This does not yet include correct load/store behaviors for objects with
inlined references (the recent #34126 PR).
vtjnash added a commit that referenced this pull request Jul 7, 2020
And add load/store alignment annotations, because LLVM now prefers that
we try to specify those explicitly, even though it's not required.

This does not yet include correct load/store behaviors for objects with
inlined references (the recent #34126 PR).
simeonschaub pushed a commit to simeonschaub/julia that referenced this pull request Aug 11, 2020
And add load/store alignment annotations, because LLVM now prefers that
we try to specify those explicitly, even though it's not required.

This does not yet include correct load/store behaviors for objects with
inlined references (the recent JuliaLang#34126 PR).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:minor change Marginal behavior change acceptable for a minor release performance Must go faster
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants