[LLVMdev] Poolalloc project and trunk llvm

Will Dietz willdtz at gmail.com
Wed Apr 16 16:43:24 PDT 2014


Any improvements you've made to poolalloc would be much appreciated! :)

~Will

On Mon, Apr 14, 2014 at 7:51 PM, Zvonimir Rakamaric
<zvonimir at cs.utah.edu> wrote:
> Hi Robert,
>
> We've been relying as well on DSA in our SMACK verifier project:
> https://github.com/smackers/smack
>
> So, yeah, we are also very much interested in keeping DSA alive. We
> could maybe even push some of our modifications into the main trunk...
>
> Thanks a lot for your effort!
>
> Best,
> -- Zvonimir
>
> --
> http://zvonimir.info
> http://soarlab.org/
>
>
> Hey Robert,
>
> Thanks for putting effort into the project.
>
> We are not really using the pool allocation related parts of
> poolalloc, but we are using a modified version of DSA, which happens
> to be part of the project.
> So yes, we indeed are interested in keeping the project alive.
>
> Cheers,
> Kevin
>
>
> On Thu, Apr 10, 2014 at 7:03 PM, Robert Matusewicz <matekm at gmail.com> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>>
>> Hi,
>>
>> I wanted to test SAFEcode, but poolalloc fails to compile with trunk
>> version of LLVM. I managed to make it compile locally and would like to
>> push my changes for review soon, but firstly I wanted to ask if there is
>> any interest in keeping poolalloc project live? The last commit was to
>> align poolalloc to llvm 3.3.
>>
>> Cheers.
>> Robert
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2.0.22 (MingW32)
>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>>
>> iQIcBAEBAgAGBQJTRs76AAoJEATzNIO2M4RNWzgQANWF9mPx+jJHrrdgvlwckJ83
>> tR91FecHLEozkU89+kdvmg/6tjQjYP/OGc8A8BVKUcImftMtGqfWMry1+LNjhJp3
>> Xhs2DnHp8lJLpl3ReD3ER5SVmSMYULwSsqnWMPAxJUzijXxlgXM1m/XzzcLyKrL5
>> lNGjiJR5I4IZhkJ4eJCgOIiM5NEejlLNl3Knwn8jBBkEE9ujuZ6Qolm9gORT2cpf
>> mwQWAcDtk5ywVk6mZoL/M8RJxXbbJTS5v2CH54vKLGBFHHHcbo8DtiuCBntg5e18
>> ozFQ90zz7/OpqyWsPYV0/mX55la/YvqVpfpWpBFDweweuFYWXs9jRCsPjHzPZP47
>> nsLgny0DM73jON7QNGa169a6DftaVTcFiuPH9iElynS1KdFilPoj4e+DXAbcr7Zs
>> 7xuwL3muAfcMbx4ErqoCWyb7qG3o/pkJHMR5GevR/1yLUJ69UdNVm/BhyUVxII0a
>> fwchsmD4NiTixzNeoHa9+gxTSq9sh3Y+9KGrDRNG8x3cFqIRTf+ad0Ze+TPKsuMy
>> e3ElyA9hN7Ame/SnNzGMvIiRs0CJXgIHXH2u5TgWtoDQCDlGZ4+Qyimf7waHymL+
>> 91Oj0a1Iwt8zEyxS2PHjJNO3WJA0jpQIWXfHQ9GX42QF1j678VQBEoii1i/h1f7B
>> tMJ751pWYc7nOjkiJ4yY
>> =QhoP
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev



More information about the llvm-dev mailing list