Stop the war!

Остановите войну!

for scientists:

default search action

combined dblp search
author search
venue search
publication search

ask others

Christopher M. Poskitt

◀ ▶ joint publications with Alexey Kolesnichenko

> Home > Persons > Christopher M. Poskitt

Publications

2017
[j3]
- view
  authority control:
- export record
  dblp key:
  - journals/cl/KolesnichenkoPN17
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/journals/cl/KolesnichenkoPN17
Alexey Kolesnichenko, Christopher M. Poskitt, Sebastian Nanz:
SafeGPU: Contract- and library-based GPGPU for object-oriented languages. Comput. Lang. Syst. Struct. 48: 68-88 (2017)
2015
[c9]
- view
  authority control:
- export record
  dblp key:
  - conf/gpce/KolesnichenkoPN15
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/gpce/KolesnichenkoPN15
Alexey Kolesnichenko, Christopher M. Poskitt, Sebastian Nanz, Bertrand Meyer:
Contract-based general-purpose GPU programming. GPCE 2015: 75-84
2014
[i1]
- view
  - electronic edition @ arxiv.org (open access)
  - references & citations
- export record
  dblp key:
  - journals/corr/KolesnichenkoPNM14
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/journals/corr/KolesnichenkoPNM14
Alexey Kolesnichenko, Christopher M. Poskitt, Sebastian Nanz, Bertrand Meyer:
Contract-Based General-Purpose GPU Programming. CoRR abs/1410.6685 (2014)
2013
[c3]
- view
  authority control:
- export record
  dblp key:
  - conf/ssbse/KolesnichenkoPM13
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/ssbse/KolesnichenkoPM13
Alexey Kolesnichenko, Christopher M. Poskitt, Bertrand Meyer:
Applying Search in an Automatic Contract-Based Testing Tool. SSBSE 2013: 318-323

a service of

manage site settings

To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.