Search results

Jump to navigation Jump to search

Page title matches

  • r6.0.1:Porting Guide
    There are four issues to deal with when it comes to porting liblfds; ...tions always correspond to a single underlying CPU instruction and it is important that the abstraction layer functions are inlined by the compiler, otherw
    13 KB (1,966 words) - 14:07, 4 January 2015
  • r6.0.0:Porting Guide
    There are four issues to deal with when it comes to porting liblfds; ...tions always correspond to a single underlying CPU instruction and it is important that the abstraction layer functions are inlined by the compiler, otherw
    13 KB (1,966 words) - 14:07, 4 January 2015
  • r6:Porting Guide
    There are four issues to deal with when it comes to porting liblfds; ...tions always correspond to a single underlying CPU instruction and it is important that the abstraction layer functions are inlined by the compiler, otherw
    13 KB (1,905 words) - 14:07, 4 January 2015
  • r7.1.1:Porting Guide (testing)
    {{DISPLAYTITLE:Porting Guide (testing)}} Each of these components offers a porting abstraction layer, to mask platform differences.
    915 bytes (126 words) - 20:16, 17 February 2017
  • r7.1.1:Porting Guide (test)
    {{DISPLAYTITLE:Porting Guide (test)}} ...ayers are provided. However, the ''test'' binary is so simple there is no porting abstraction layer. All that is required is a hosted environment.
    376 bytes (53 words) - 20:16, 17 February 2017
  • r7.1.1:Porting Guide (libtest)
    {{DISPLAYTITLE:Porting Guide (libtest)}} ...traction layer has been written. Porting simply involves implementing the porting abstraction layer; the library will then compile and work. Implementati
    3 KB (361 words) - 15:56, 1 April 2018
  • r7.1.1:Porting Guide (libshared)
    {{DISPLAYTITLE:Porting Guide (libshared)}} ...traction layer has been written. Porting simply involves implementing the porting abstraction layer; the library will then compile and work. Implementati
    2 KB (316 words) - 15:53, 1 April 2018
  • r7.1.1:Porting Guide (liblfds)
    {{DISPLAYTITLE:Porting Guide (liblfds)}} ...orting abstraction layer has been written. Porting means to implement the porting abstraction layer for the new platform; the library will then compile an
    13 KB (1,819 words) - 11:01, 5 March 2019
  • r7.1.1:Porting Guide (libbenchmark)
    {{DISPLAYTITLE:Porting Guide (libbenchmark)}} ...traction layer has been written. Porting simply involves implementing the porting abstraction layer; the library will then compile and work. Implementati
    2 KB (249 words) - 15:59, 1 April 2018
  • r7.1.1:Porting Guide (benchmarking)
    {{DISPLAYTITLE:Porting Guide (benchmarking)}} Each of these components offers a porting abstraction layer, to mask platform differences.
    961 bytes (124 words) - 20:16, 17 February 2017
  • r7.1.1:Porting Guide (benchmark)
    {{DISPLAYTITLE:Porting Guide (benchmark)}} ...traction layer has been written. Porting simply involves implementing the porting abstraction layer; the library will then compile and work. Implementati
    2 KB (247 words) - 20:16, 17 February 2017
  • r7.1.0:Porting Guide (benchmark)
    {{DISPLAYTITLE:Porting Guide (benchmark)}} ...traction layer has been written. Porting simply involves implementing the porting abstraction layer; the library will then compile and work. Implementati
    2 KB (247 words) - 17:07, 30 May 2016
  • r7.1.0:Porting Guide (test)
    {{DISPLAYTITLE:Porting Guide (test)}} ...ayers are provided. However, the ''test'' binary is so simple there is no porting abstraction layer. All that is required is a hosted environment.
    376 bytes (53 words) - 20:28, 29 May 2016
  • r7.1.0:Porting Guide (benchmarking)
    {{DISPLAYTITLE:Porting Guide (benchmarking)}} Each of these components offers a porting abstraction layer, to mask platform differences.
    961 bytes (124 words) - 20:25, 29 May 2016
  • r7.1.0:Porting Guide (testing)
    {{DISPLAYTITLE:Porting Guide (testing)}} Each of these components offers a porting abstraction layer, to mask platform differences.
    915 bytes (126 words) - 20:25, 29 May 2016
  • r7.1.0:Porting Guide (libbenchmark)
    {{DISPLAYTITLE:Porting Guide (libbenchmark)}} ...traction layer has been written. Porting simply involves implementing the porting abstraction layer; the library will then compile and work. Implementati
    2 KB (245 words) - 17:06, 30 May 2016
  • r7.1.0:Porting Guide (libtest)
    {{DISPLAYTITLE:Porting Guide (libtest)}} ...traction layer has been written. Porting simply involves implementing the porting abstraction layer; the library will then compile and work. Implementati
    3 KB (384 words) - 17:08, 30 May 2016
  • r7.1.0:Porting Guide (libshared)
    {{DISPLAYTITLE:Porting Guide (libshared)}} ...traction layer has been written. Porting simply involves implementing the porting abstraction layer; the library will then compile and work. Implementati
    2 KB (312 words) - 17:01, 30 May 2016
  • r7.1.0:Porting Guide (liblfds)
    {{DISPLAYTITLE:Porting Guide (liblfds)}} ...traction layer has been written. Porting simply involves implementing the porting abstraction layer; the library will then compile and work. Implementati
    16 KB (2,389 words) - 16:53, 30 May 2016
  • r7.0.0:Porting Guide (test)
    {{DISPLAYTITLE:Porting Guide (test)}} ...porting abstraction layer; the programme will then compile and work. The porting abstraction layer is implemented as a single header file and three C fil
    4 KB (530 words) - 23:57, 24 December 2015

Page text matches

  • r7.1.1:Porting Guide (testing)
    {{DISPLAYTITLE:Porting Guide (testing)}} Each of these components offers a porting abstraction layer, to mask platform differences.
    915 bytes (126 words) - 20:16, 17 February 2017
  • r7.1.1:Porting Guide (benchmarking)
    {{DISPLAYTITLE:Porting Guide (benchmarking)}} Each of these components offers a porting abstraction layer, to mask platform differences.
    961 bytes (124 words) - 20:16, 17 February 2017
  • r7.1.0:Porting Guide (benchmarking)
    {{DISPLAYTITLE:Porting Guide (benchmarking)}} Each of these components offers a porting abstraction layer, to mask platform differences.
    961 bytes (124 words) - 20:25, 29 May 2016
  • r7.1.0:Porting Guide (testing)
    {{DISPLAYTITLE:Porting Guide (testing)}} Each of these components offers a porting abstraction layer, to mask platform differences.
    915 bytes (126 words) - 20:25, 29 May 2016
  • r7.1.1:Release 7.1.1 Documentation
    * [[r7.1.1:Building Guide (liblfds)|Building Guide (liblfds)]] * [[r7.1.1:Building Guide (testing)|Building Guide (testing)]]
    3 KB (366 words) - 11:21, 18 February 2017
  • r7.1.0:Release 7.1.0 Documentation
    * [[r7.1.0:Building Guide (liblfds)|Building Guide (liblfds)]] * [[r7.1.0:Building Guide (testing)|Building Guide (testing)]]
    3 KB (366 words) - 11:21, 18 February 2017
  • r6.1.1:Release 6.1.1 Documentation
    * [[r6.1.1:Building Guide (lfds)|Building Guide (lfds)]] * [[r6.1.1:Building Guide (test)|Building Guide (test)]]
    2 KB (284 words) - 14:07, 4 January 2015
  • r6.1.0:Release 6.1.0 Documentation
    * [[r6.1.0:Building Guide (lfds)|Building Guide (lfds)]] * [[r6.1.0:Building Guide (test)|Building Guide (test)]]
    2 KB (284 words) - 14:07, 4 January 2015
  • r7.0.0:Release 7.0.0 Documentation
    * [[r7.0.0:Building Guide (liblfds)|Building Guide (liblfds)]] * [[r7.0.0:Building Guide (test)|Building Guide (test)]]
    3 KB (316 words) - 21:02, 7 May 2016
  • r7.1.0:Porting Guide (libshared)
    {{DISPLAYTITLE:Porting Guide (libshared)}} ...traction layer has been written. Porting simply involves implementing the porting abstraction layer; the library will then compile and work. Implementati
    2 KB (312 words) - 17:01, 30 May 2016
  • r7.1.1:Porting Guide (libshared)
    {{DISPLAYTITLE:Porting Guide (libshared)}} ...traction layer has been written. Porting simply involves implementing the porting abstraction layer; the library will then compile and work. Implementati
    2 KB (316 words) - 15:53, 1 April 2018
  • r7.1.1:Introduction
    Welcome to ''liblfds'', a portable, license-free, lock-free data structure library written in C. ==Out-of-the-Box Supported Data Structures and Platforms==
    24 KB (3,409 words) - 20:16, 17 February 2017
  • r7.1.0:Introduction
    Welcome to ''liblfds'', a portable, license-free, lock-free data structure library written in C. ==Out-of-the-Box Supported Data Structures and Platforms==
    24 KB (3,409 words) - 20:14, 18 June 2016
  • r7.1.1:Porting Guide (test)
    {{DISPLAYTITLE:Porting Guide (test)}} ...ayers are provided. However, the ''test'' binary is so simple there is no porting abstraction layer. All that is required is a hosted environment.
    376 bytes (53 words) - 20:16, 17 February 2017
  • r7.1.0:Porting Guide (test)
    {{DISPLAYTITLE:Porting Guide (test)}} ...ayers are provided. However, the ''test'' binary is so simple there is no porting abstraction layer. All that is required is a hosted environment.
    376 bytes (53 words) - 20:28, 29 May 2016
  • r7.0.0:Introduction
    Welcome to liblfds, a portable, license-free, lock-free data structure library written in C. Both ''liblfds'' and ''test'' provide a porting abstraction layer, which acts to mask platform differences.
    24 KB (3,683 words) - 20:14, 18 June 2016
  • r7.1.1:Define BENCHMARK PAL MEMORY TYPE
    └───libbenchmark_porting_abstraction_layer_operating_system.h ...iven a proper porting abstraction layer, and it will be the main way users port benchmarking functionality.
    1 KB (190 words) - 20:16, 17 February 2017
  • r7.1.0:Define BENCHMARK PAL MEMORY TYPE
    └───libbenchmark_porting_abstraction_layer_operating_system.h ...iven a proper porting abstraction layer, and it will be the main way users port benchmarking functionality.
    1 KB (190 words) - 00:28, 30 May 2016
  • r7.1.1:Define BENCHMARK PAL OS STRING
    └───libbenchmark_porting_abstraction_layer_operating_system.h * [[r7.1.1:Porting Guide (benchmark)|Porting Guide (benchmark)]]
    612 bytes (74 words) - 20:16, 17 February 2017
  • r7.1.0:Define BENCHMARK PAL OS STRING
    └───libbenchmark_porting_abstraction_layer_operating_system.h * [[r7.1.0:Porting Guide (benchmark)|Porting Guide (benchmark)]]
    612 bytes (74 words) - 00:28, 30 May 2016

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Retrieved from ‘https://www.liblfds.org/mediawiki/index.php?title=Special:Search’