-
-
Notifications
You must be signed in to change notification settings - Fork 924
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: jruby/jruby
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 424e3512a772
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: jruby/jruby
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: bf4bacb6081b
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 13 commits
- 33 files changed
- 3 contributors
Commits on May 12, 2015
-
3
Configuration menu - View commit details
-
Copy full SHA for 6b59f27 - Browse repository at this point
Copy the full SHA 6b59f27View commit details
Commits on May 13, 2015
-
Remove fragile temp-specific local opts from OptimizeTempVars code
* This pass was written way back when ... when we were concerned about interp perf on its own, and this was running before local opt pass and could disable some local opts because of introducing RAW hazards. So, I had added some temp-specific local opts in there which were fragile (and over time, code and comments had diverged). * Since we swapped the ordering to run local opt pass before this one (before disabling it), we no longer need to run the fragile local opts all over again in this pass (which also happened to have been buggy!). * With these fixes, we can once again re-enable this pass, if we want to without breaking tests. Let us make that decision separately if this pass is even worth it, and let us measure how much perf. this even gains us. Does it produce any memory savings? If so, how significant. If this is not useful perf-wise, we should just kill this code since we are more interested in JIT perf now.
Configuration menu - View commit details
-
Copy full SHA for dbe9b34 - Browse repository at this point
Copy the full SHA dbe9b34View commit details -
Configuration menu - View commit details
-
Copy full SHA for a0b8c74 - Browse repository at this point
Copy the full SHA a0b8c74View commit details -
Configuration menu - View commit details
-
Copy full SHA for 20396fd - Browse repository at this point
Copy the full SHA 20396fdView commit details -
Configuration menu - View commit details
-
Copy full SHA for 01a2709 - Browse repository at this point
Copy the full SHA 01a2709View commit details -
Configuration menu - View commit details
-
Copy full SHA for 54e28cd - Browse repository at this point
Copy the full SHA 54e28cdView commit details -
Configuration menu - View commit details
-
Copy full SHA for 843129c - Browse repository at this point
Copy the full SHA 843129cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 59d1520 - Browse repository at this point
Copy the full SHA 59d1520View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6329bb4 - Browse repository at this point
Copy the full SHA 6329bb4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1b6729a - Browse repository at this point
Copy the full SHA 1b6729aView commit details -
Configuration menu - View commit details
-
Copy full SHA for b925a73 - Browse repository at this point
Copy the full SHA b925a73View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0f5f903 - Browse repository at this point
Copy the full SHA 0f5f903View commit details -
Configuration menu - View commit details
-
Copy full SHA for bf4bacb - Browse repository at this point
Copy the full SHA bf4bacbView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 424e3512a772...bf4bacb6081b