Personal info for willembryce
This person is currently certified at Master level.Name: Bryce Kampjes
Homepage: www.kampjes.demon.co.uk
Notes: Most (all) of my Squeaking is going into a little compiler called Exupery. Exupery is almost useful now, if you're running Squeak on an x86 Linux box feel free to try it. With luck the next release should be generally useful.
This person is:
- a User on project Monticello.
- a Admirer on project BFAV.
- a User on project UnixVM.
- a Lead Developer on project Exupery.
- a User on project Refactoring Browser and related tools.
- a Admirer on project Traits.
- a Admirer on project Video Flow.
- a Admirer on project Squat.
- a User on project Look Enhancements.
- a User on project Connectors.
- a User on project Seaside.
- a User on project Shout.
- a User on project Genie.
- a User on project VMMaker.
Recent diary entries for willembryce:
London Smalltalk Meeting this SaturdayThe meeting is this Saturday. There's a good list of people attending, if you'd like to attend please add your name to the wiki page so building security will know to let you in.
If there's anything you'd like to present, please feel free to add your name to the list.
The wiki page is here.
Discussion and our monthly meetings are organised on the UK Smalltalk mailing list here.
Reminder London Smalltalk Meeting Saturday 8th of MarchThere will be a Smalltalk meeting in London on Saturday the 8th of March. We plan to start at 10am with the morning focussed on beginners. Feel free to show up later, normally the afternoon will start around 1pm.
There's already about 20 people signed up on the wiki page, please add your name if you're interested in coming or presenting soemthing so building security will know to let you in.
RSPV required as it's being hosted in corporate offices.
Discussion or suggestions is best placed on the UK Smalltalk mailing list.
Smalltalk UK meeting on Saturday 8th MarchWe're organising a Smalltalk event in London. This is going to be on a Saturday afternoon, we'll probably head to a pub afterwards. We'll aim to get a room with a projector.
Details are here. RSPV required as it's being hosted in corporate offices. Please add your name if you're interested in either attending or presenting.
Discussion will be on the UK Smalltalk mailing list.
The next Saturday London Smalltalk GatheringWe're thinking about organising the next Saturday London Smalltalk gathering on the 8th of March. If there's any good reason to pick a better date please tell us before we start booking rooms. We'll aim to have a room with a projector so people can give talks. As always we'll probably migrate to a pub for dinner then a few beers afterwards
Discussion will be on the UK Smalltalk mailing list.
Thinking about Exupery 0.14The primary goal for the next releases will be making the following benchmarks more compelling. I've added a compile time benchmark as there are a few performance bugs in the compiler that should be removed.
arithmaticLoopBenchmark 1396 compiled 128 ratio: 10.906 bytecodeBenchmark 2111 compiled 460 ratio: 4.589 sendBenchmark 1637 compiled 668 ratio: 2.451 doLoopsBenchmark 1081 compiled 715 ratio: 1.512 pointCreation 1245 compiled 1317 ratio: 0.945 largeExplorers 728 compiled 715 ratio: 1.018 compilerBenchmark 483 compiled 489 ratio: 0.988 Cumulative Time 1125 compiled 537 ratio 2.093ExuperyBenchmarks>>arithmeticLoop 249ms SmallInteger>>benchmark 1112ms InstructionStream>>interpretExtension:in:for: 113460ms Average 3155.360
First, I'll get the register allocator to allocate each section of method separately. After that, I'll probably do some work on further optimising the register allocator but I might work on improving the generated native code.
Register allocating each section separately will both allow for better and faster allocation. It will make it easy to avoid dealing with registers and interference from other sections of the code and will reduce the size of the problem. Colouring register allocation written well should be on average n log n time but the performance bugs will raise that to probably n^2.
It's possible that just allocating each section of the method separately will be enough to bring allocation down to a reasonable time. It should definitely help for the larger methods but is unlikely to do anything for the arithmaticLoop and will only help the bytecode benchmark slightly. Compiling quicker will make it easier to run more extensive tests.
This person has certified others as follows:
- willembryce certified rowledge as Master
- willembryce certified tween as Journeyer
- willembryce certified chrismuller as Journeyer
- willembryce certified daniel as Apprentice
- willembryce certified bwbadger as Apprentice
Others have certified this person as follows:
- water certified willembryce as Journeyer
- AndreasRaab certified willembryce as Journeyer
- cwp certified willembryce as Apprentice
- bkv certified willembryce as Apprentice
- KenCausey certified willembryce as Journeyer
- DanyAltman certified willembryce as Apprentice
- RomainRobbes certified willembryce as Journeyer
- mue certified willembryce as Apprentice
- GermanArduino certified willembryce as Master
- humasect certified willembryce as Apprentice
- Ozzard certified willembryce as Journeyer
- BertFreudenberg certified willembryce as Journeyer
- SergeStinckwich certified willembryce as Apprentice
- sikirk certified willembryce as Journeyer
- iakovz certified willembryce as Master
- FrankShearar certified willembryce as Journeyer
- mikevdg certified willembryce as Journeyer
- mivsek certified willembryce as Master
- mathk certified willembryce as Master
- ron certified willembryce as Journeyer
- GazzaGuru certified willembryce as Master
[ Certification disabled because you're not logged in. ]
[ Home | Articles | Login/Account | People | Projects ]