If you're new here and like what you read, you may want to subscribe to my RSS blog feed or free email updates. Thanks for visiting!
Now this is just typical. Last week I have finally gotten rid of my job board, because nobody was using it. Just a week later, my advisor asks me, where it went, because she would like to announce two job openings. Oh well. Murphy is everywhere. I won’t bring back the job board, because as we say in Germany One swallow does not make a summer (gotta love those word-for-word translations
), but I will not miss the chance to tell you about the openings. (more…)
Contrary to what the update-frequency of this blog suggests, I am not dead. Not even near that, I am very healthy the only problem is that with my new job, new house in the works and family I am left with very little time for blogging. Life is about setting the right priorities and at this point in time unfortunately this means I will not be able to keep up to my usual posting frequency of one post per week. Instead I am aiming for one post per month now, while leaving the door open to write more as soon as my time permits. There is always enough time for a short newsflash on interesting articles on the net, though:
I usually don’t post press releases. But this one is different, since my favorite parallel programming system has almost reached its third major release. That’s right, OpenMP 3.0 is right around the corner and this is your chance to get your early fix. The language committee has worked very hard to make it a true revolution. I have told you about the major change before (
I have been very quiet on this blog lately, mostly because my new job and the creation of our new house have kept me rather busy. Having to get up at 6 in the morning to be able to bring our son to kindergarden has not helped my productivity in the evenings either - and of course that’s the time when I am usually writing for this blog. But anyways, I will try to be more productive in the future. What I would like to write about today are two blog posts from Tim Mattson, the first one called
While at the
It has been a while since I have done a news-roundup - therefore it is time for a new one. But before I start, let me pass on a few personal remarks about my present situation. I am in the process of finishing my PhD. right now and hope to submit it for review next week. Of course, this also means that I am rather busy at the moment, therefore the comments to each article I present here are not as verbose as you may be used to. I have also moved back to
The very first step in every successful parallelization effort is always the same: you take a look at the problem that needs to be solved and start splitting it into tasks that can be computed in parallel. This sounds easy, but I can see from my students reactions that at least for some of them it is not. This article shows five ways to do just that. It is a short version for a blog article, the long version can be found in the book
It has been a while since I have done this little experiment, but I still find the results interesting. As some of you may know, I teach a class on parallel programming (this is an undergraduate class, by the way - may I have a
Mark Nelson does not believe in the
When I started my PhD.-thesis a couple of years ago, I took some time to look at auto-parallelizing compilers and research. After all, I wanted to work on making parallel programming easier, and the best way to do that would surely be to let compilers do all the work. Unfortunately, the field appeared to be quite dead at that time. There has been a huge amount of research done in the eighties and nineties, yet it all appeared to have settled down. And the compilers I tried could not parallelize more than the simplest loops. I have always been asking myself why this was the case, and when I had the chance to talk to Dr. Jay Hoeflinger, he had some very interesting answers for me. He agreed to let me re-ask these questions in an email interview and this is the result. Thanks, Jay, for sharing your knowledge!