Eregon (Benoit Daloze)
- Login: Eregon
- Registered on: 07/30/2009
- Last sign in: 03/13/2026
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 3 | 65 | 68 |
| Reported issues | 28 | 195 | 223 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| Ruby | Committer | 08/02/2012 |
Activity
03/13/2026
-
03:13 PM Ruby Revision 17747554 (git): [ruby/prism] Make it possible to lazily deserialize DefNode in Loader.java
- * TRUFFLERUBY_METRICS_REPS=5 jt metrics time --experimental-options -e0
For parsing-core:
before: 0.097 0.099 0.092 0.096
after: 0.061 0.063 0.066 0.059
* Remove extra trailing spaces by using `<%-#`.
https://github.com/ruby/pris...
03/12/2026
-
10:15 AM Ruby Feature #21950: Add a built-in CPU-time profiler
- byroot (Jean Boussier) wrote in #note-11:
> But I suspect supporting both isn't that much extra work?
I think it'd be good for this API to be able to say which one it wants (like `StackProf`'s `mode:` kwarg). -
10:12 AM Ruby Feature #21950: Add a built-in CPU-time profiler
- osyoyu (Daisuke Aritomo) wrote in #note-8:
> I don't want the API/output format to restrict what a profiler could emit. I wouldn't say such design is not doable, but careful consideration would be needed.
Careful consideration is exa...
03/11/2026
-
01:40 PM Ruby Feature #21950: Add a built-in CPU-time profiler
- osyoyu (Daisuke Aritomo) wrote in #note-5:
> I am rather doubtful that CRuby/JRuby/TruffleRuby can share any profiler implementation at all.
They can't share the implementation of gathering backtraces (that's implementation-specific)... -
01:37 PM Ruby Feature #21950: Add a built-in CPU-time profiler
- osyoyu (Daisuke Aritomo) wrote in #note-5:
> I am rather doubtful that CRuby/JRuby/TruffleRuby can share any profiler implementation at all.
I think the opposite, I think it's actually easy to implement such an API on TruffleRuby and... -
12:22 PM Ruby Bug #21828: An incorrect warning message related to `benchmark` is shown when using `benchmark-ips`
- Thank you for the quick fix!
-
09:56 AM Ruby Bug #21828: An incorrect warning message related to `benchmark` is shown when using `benchmark-ips`
- A main difference between both reproductions are the Gemfile.lock, for the reproduction in the issue description:
```
GEM
remote: https://rubygems.org/
specs:
benchmark-ips (2.14.0)
PLATFORMS
ruby
x86_64-linux
DE... -
09:52 AM Ruby Bug #21828: An incorrect warning message related to `benchmark` is shown when using `benchmark-ips`
- Interestingly it seems fixed for the original reproduction in the issue description, but *not* for the new reproduction of running `benchmark-ips`'s tests.
-
09:46 AM Ruby Bug #21828: An incorrect warning message related to `benchmark` is shown when using `benchmark-ips`
- Also happens on `4.0-dev` from `ruby-build` (`ruby 4.0.1 (2026-03-10 revision 21f2bbf322) +PRISM [x86_64-linux]`).
-
09:38 AM Ruby Bug #21828 (Open): An incorrect warning message related to `benchmark` is shown when using `benchmark-ips`
- As I said:
Eregon (Benoit Daloze) wrote in #note-6:
> still a problem on master
I have tried with `ruby 4.1.0dev (2026-03-11T07:46:22Z master c08f977ac7) +PRISM [x86_64-linux]` specifically.
Please try the reproduction before closing.