Displaying 5 results from an estimated 5 matches for "ppopp".
Did you mean:
mpopp
2007 Oct 29
1
[LLVMdev] malloc() vs. MallocInst
Hi Vikram,
I want to use poolalloc as a means for partitioning memory in Software
Transactional Memory. We will have a paper about tuning parameters in
word-based STMs in PPoPP 08, but there we use one configuration for the
complete TM, which obviously has limitations in heterogenous workloads.
Partitioning with poolalloc should give me (1) hopefully meaningful partitions
(ie, datastructures) with locality without requiring user annotations, (2)
spatial locality that...
2016 Oct 18
2
LLVM Performance Workshop at CGO 2017
An LLVM Performance Workshop will be held at CGO 2017. The workshop
is co-located with CC, HPCA, and PPoPP.
If you are interested in attending the workshop, please register at
the CGO website: http://cgo.org/cgo2017/workshops.html
Call for Speakers
We invite speakers from academia and industry to present their work on the
following list of topics (including and not limited to:)
- improving performanc...
2007 Oct 29
0
[LLVMdev] malloc() vs. MallocInst
Torvald,
For what are you interested in poolalloc? I'm asking because we are
trying to decide how to prioritize work on it. Thanks,
--Vikram
http://www.cs.uiuc.edu/~vadve
http://llvm.org
On Oct 27, 2007, at 11:10 AM, Torvald Riegel wrote:
> Hi,
>
> I recently looked quite some time for why poolalloc wouldn't
> transform calls
> to malloc() in my program, until I
2017 Jan 03
3
LLVM Performance Workshop at CGO 2017 (early registration ends January 6th)
FYI,
The LLVM Performance Workshop will be held at CGO 2017. The workshop
is co-located with CC, HPCA, and PPoPP.
If you are interested in attending the workshop, please register at
the CGO website: http://cgo.org/cgo2017/workshops.html
When: Saturday February 4th, 2017
Where: Austin, Texas, USA
----
Hi, CGO workshop and tutorial organizers,
This is a friendly reminder that early registration rates for CGO...
2007 Oct 27
3
[LLVMdev] malloc() vs. MallocInst
Hi,
I recently looked quite some time for why poolalloc wouldn't transform calls
to malloc() in my program, until I noticed that it handles calls to malloc()
(eg, stdlib pass) -- but only transforms MallocInst's.
Is there a general policy on how passes should behave? Should they handle both
representations, is doing -raiseallocs the preferred way, or do we
explicitely not want any