Freaky (Thomas Hurst)
- Login: Freaky
- Email: tom@hur.st
- Registered on: 08/28/2018
- Last sign in: 02/27/2025
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 2 | 2 |
Activity
10/05/2023
09/27/2023
-
06:52 PM Ruby Bug #19875: Ruby 3.0 -> 3.1 Performance regression in String#count
- ahorek (Pavel Rosický) wrote in #note-18:
> I think if the platform support is sufficient, there are multiple places where this feature could be beneficial.
I think the platform support covers the major bases. I'm testing a PHP buil... -
- I've updated [fast-bytecount](https://github.com/Freaky/fast-bytecount) with autotools support, which detects the needed compiler features and exposes flags to disable bits of it.
Perhaps there are other places in MRI that would benef... -
- ahorek (Pavel Rosický) wrote in #note-15:
> @Freaky here's an alternative approach https://godbolt.org/z/zWhTYv8x5
> ...
I think it's too much of a maintenance burden to reimplement this stuff from first principles when there's compil...
09/19/2023
-
- nobu (Nobuyoshi Nakada) wrote in #note-13:
> Freaky (Thomas Hurst) wrote in #note-12:
> ...
If only!
I've added an AVX2 path and worked on getting runtime dispatch working on both clang and gcc. I've combined the result into a sing...
09/18/2023
-
- nobu (Nobuyoshi Nakada) wrote in #note-11:
> Freaky (Thomas Hurst) wrote in #note-9:
> ...
Thanks for trying it!
> But it seems no significant difference on x86_64-darwin.
I see a difference if I configure with cflags=-msse4.2 - ...
09/15/2023
-
- nobu (Nobuyoshi Nakada) wrote in #note-7:
> These are all generated by the same compiler?
Yes - FreeBSD clang version 14.0.5. I also try 15.0.7 to no effect.
gcc 12.2.0 performs much better, though it too has a slightly more mo... -
- Annotated disassemblies attached.
05/30/2019
-
- Calling `#size` on an infinite `each_slice` Enumerator results in a `FloatDomainError` exception:
``` ruby
1.step.size # => Infinity
1.step.each_slice(2).size # => FloatDomainError
```
```
Traceback (most recent call last):
.....
09/01/2018
-
- shyouhei (Shyouhei Urabe) wrote:
> While I'm not against these points, I feel it is not a good idea to wait for such new API. Can we focus on fixing FreeBSD first? Maybe the OpenBSD issue should be handled separately in another thread...