| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Due to a problem with ripper we do not recognize `break` as invalid code. It's confusing that "Syntax OK" is output in that case.
When there's no syntax error, the algorithm should not say anything. The exception is in the CLI and that's for compatibility with `ruby -wc`
```
$ cat /tmp/break.rb
break
⛄️ 3.1.2 🚀 /Users/rschneeman/Documents/projects/syntax_suggest (schneems/no-syntax-not-okay-break)
$ ruby -wc /tmp/break.rb
Syntax OK
```
> Note that this is invalid, running this code will raise a Syntax error.
```
$ exe/syntax_suggest /tmp/break.rb
Syntax OK
```
Close https://github.com/ruby/syntax_suggest/pull/157
https://github.com/ruby/syntax_suggest/commit/d7bd8f03a2
|
|
|
|
| |
https://github.com/ruby/syntax_suggest/commit/14e8cdc916
|
|
|
|
| |
`sync_default_gems_with_commits` also needs the default branch.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit ccd8dd6ad395bbd9f5290e0fcb7929e5e5d36767.
Revert "MJIT: Fix miniruby with MJIT_FORCE_ENABLE"
This reverts commit b033775ed9d9226ba73c1d4a197e55ba89575142.
GitHub Actions is failing. I ran out of time today to investigate it.
will try it again tomorrow.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Solargraph complains about it
|
| |
|
|
|
|
| |
https://github.com/ruby/ruby/actions/runs/3562236318/jobs/5983796689
|
|
|
|
| |
Faster code generation and cleaner code.
|
| |
|
|
|
|
|
| |
Regexp tests are flaky.
http://rubyci.s3.amazonaws.com/s390x/ruby-master/log/20221128T050004Z.fail.html.gz
|
|
|
|
|
|
|
|
|
|
| |
You shouldn't assume bf->compiler is always non-zero. While struct
aref/aset is no longer a builtin function since
https://github.com/ruby/ruby/pull/5131, it seems like you could still
load such an iseq binary.
The refactored code fallbacks to compile_insn_default correctly when
bf->compiler is zero.
|
|
|
|
|
|
|
| |
instead of FILE*.
Using C.fprintf is slower than String manipulation on memory. I'm going
to change the way MJIT writes files, and this is a prerequisite for it.
|
| |
|
| |
|
| |
|
|
|
|
| |
https://github.com/ruby/cgi/commit/827b7d43cc
|
|
|
|
| |
https://github.com/ruby/rdoc/commit/33925f885f
|
|
|
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/cgi/pull/29)
* Loosen the domain regex to accept '.'
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
https://github.com/ruby/cgi/commit/5e09d632f3
Co-authored-by: Hiroshi SHIBATA <hsbt@ruby-lang.org>
|
| |
|
|
|
|
| |
https://github.com/ruby/cgi/commit/710a647855
|
|
|
| |
Update `bundled_gems` to bundle RBS 2.8.1
|
| |
|
|
|
| |
Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
|
|
|
|
| |
and clean up legacy comments for the Ruby migration
|
|
|
|
|
|
|
|
|
|
|
| |
process. Completely isolating the MJIT compilation process complicates a
lot of things for ensuring consistency before and after the fork.
Just running this synchronously makes things a lot easier, for example
the race condition of capture_cc_entries could be fixed by this patch
alone. Hopefully, the bottleneck is the C compiler and not this Ruby
code. Also, this change doesn't negatively impact MJIT's final numbers
on yjit-bench while "1st itr" is degraded for sure.
|
|
|
|
| |
https://github.com/ruby/ruby/actions/runs/3560006749/jobs/5979749144
|
|
|
|
|
|
|
|
|
| |
We've disabled MJIT CI on GitHub Actions for a while. It's convenient
that fork repositories need to see failures or disable it.
We should remove unused CI by default instead of silently disabling it.
Since I saw --mjit-wait passed on my fork, I'd like to try running
--mjit-wait one.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
http://ci.rvm.jp/results/trunk-yjit@phosphorus-docker/4309535
http://ci.rvm.jp/results/trunk-random0@phosphorus-docker/4309536
http://ci.rvm.jp/results/trunk-random1@phosphorus-docker/4309538
http://ci.rvm.jp/results/trunk-random2@phosphorus-docker/4309541
http://ci.rvm.jp/results/trunk-random3@phosphorus-docker/4309544
http://ci.rvm.jp/results/trunk-no-mjit@phosphorus-docker/4309550
http://ci.rvm.jp/results/trunk-yjit@phosphorus-docker/4309556
http://ci.rvm.jp/results/trunk-random0@phosphorus-docker/4309562
http://ci.rvm.jp/results/trunk-random1@phosphorus-docker/4309564
http://ci.rvm.jp/results/trunk-random2@phosphorus-docker/4309567
http://ci.rvm.jp/results/trunk-random3@phosphorus-docker/4309570
http://rubyci.s3.amazonaws.com/solaris10-gcc/ruby-master/log/20221127T200003Z.fail.html.gz
http://ci.rvm.jp/results/trunk-random-repeat@phosphorus-docker/4309581
http://rubyci.s3.amazonaws.com/freebsd12/ruby-master/log/20221127T203002Z.fail.html.gz
http://ci.rvm.jp/results/trunk-yjit@phosphorus-docker/4309588
|
|
|
|
|
|
| |
This reverts commit https://github.com/ruby/rdoc/commit/41ceae93b3bc.
https://github.com/ruby/rdoc/commit/5d2c47e8b8
|
|
|
|
|
|
| |
Make verbatims text or newline only, and simplify `build_verbatim`.
https://github.com/ruby/rdoc/commit/41ceae93b3
|
|
|
|
|
|
|
|
|
| |
This way, custom CSS styles can be easily applied to the entire method
header at once. Otherwise, it can be tricky to make a border that goes
around the entire set of method call-seq, but not the method
description.
https://github.com/ruby/rdoc/commit/5db4bce01e
|
|
|
|
|
|
|
| |
This uses `<details><summary>heading</summary><ul>nested</ul></detail>`,
similar to how the classes and pages lists are now nested.
https://github.com/ruby/rdoc/commit/e57beff287
|
|
|
|
| |
https://github.com/ruby/rdoc/commit/a976fb9d39
|
|
|
|
|
|
| |
To share with the duplicate code in RDoc::Parser::Ruby#initialize.
https://github.com/ruby/rdoc/commit/27829ac119
|
| |
|
|
|
|
| |
https://github.com/ruby/erb/commit/3bb67009dd
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/erb/pull/39)
* Skip using the extension for truffleruby as well
* Just skip building the C extension for TruffleRuby
* Skip rake compile for truffleruby
* Use resolve_feature_path
* Revert "Use resolve_feature_path"
This reverts commit https://github.com/ruby/erb/commit/acc1e0c0ffaf.
* Use resolve_feature_path with LoadError guard
https://github.com/ruby/erb/commit/85dcb08439
|
|
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/irb/pull/459)
* Activate yamatanooroti tests on CI
* Fix delete test
https://github.com/ruby/irb/commit/750cf4c480
|
|
|
|
| |
https://github.com/ruby/net-http/commit/77c6878970
|
|
|
|
|
| |
`#compile` has a catch-call rescue, so compile_insn_entry shouldn't do
that. It was a temporary code needed during the migration.
|
|
|
|
| |
There are too many mjit_compiler.* files. It was hard to find files.
|
|
|
|
|
|
|
| |
The error raised for broken coderanges was changed in ruby/ruby@571d21f
and the test was fixed in that commit but not ported to this repo.
ruby/net-http@e6185dda26ea6db7a3515d4f47ab231f5f4ac902
|