Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
T
tarantool
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
core
tarantool
Commits
c7823c5d
Unverified
Commit
c7823c5d
authored
3 years ago
by
Igor Munkin
Browse files
Options
Downloads
Patches
Plain Diff
luajit: bump new version
* memprof: report JIT-side allocations as internal Closes #5679
parent
2e9cbec3
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
changelogs/unreleased/gh-5679-memprof-report-jit-allocations-as-internal.md
+4
-0
4 additions, 0 deletions
...sed/gh-5679-memprof-report-jit-allocations-as-internal.md
third_party/luajit
+1
-1
1 addition, 1 deletion
third_party/luajit
with
5 additions
and
1 deletion
changelogs/unreleased/gh-5679-memprof-report-jit-allocations-as-internal.md
0 → 100644
+
4
−
0
View file @
c7823c5d
## feature/luajit
*
Now memory profiler reports allocations made by JIT engine while compiling
the trace as INTERNAL (gh-5679).
This diff is collapsed.
Click to expand it.
luajit
@
196d4ca8
Compare
f08aaf6d
...
196d4ca8
Subproject commit
f08aaf6de80ba83e55401263e72fc66f6b036ea6
Subproject commit
196d4ca81381236d57d7959659b0659ff6be8957
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment