objc4

By apple-opensource

Objc4 Alternatives

Similar projects and alternatives to objc4

  • wgpu

    197 objc4 VS wgpu

    A cross-platform, safe, pure-Rust graphics API.

  • MoltenVK

    103 objc4 VS MoltenVK

    MoltenVK is a Vulkan Portability implementation. It layers a subset of the high-performance, industry-standard Vulkan graphics and compute API over Apple's Metal graphics framework, enabling Vulkan applications to run on macOS, iOS and tvOS.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • metal-cpp

    Metal-cpp is a low-overhead C++ interface for Metal that helps developers add Metal functionality to graphics apps, games, and game engines that are written in C++.

  • clspv

    Clspv is a compiler for OpenCL C to Vulkan compute shaders

  • metal-rs

    Rust bindings for Metal

  • SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better objc4 alternative or higher similarity.

objc4 reviews and mentions

Posts with mentions or reviews of objc4. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-11-22.
  • Low overhead C++ interface for Apple's Metal API
    8 projects | news.ycombinator.com | 22 Nov 2021
    > The specific method that's causing me trouble right at the moment is "computeCommandEncoder"

    Yeah, it looks like there's no way to avoid autorelease here.

    > It looks like objc_retainAutoreleasedReturnValue might be exactly what I'm looking for, even if it isn't 100% guaranteed; if I'm understanding, it would be safe, and wouldn't actually leak as long as you had an autorelease pool somewhere in the chain.

    Indeed it would be safe and wouldn't leak, but the optimization is very much not guaranteed. It's based on the autorelease implementation manually reading the instruction at its return address to see if it's about to call objc_retainAutoreleaseReturnValue. See the description here:

    https://github.com/apple-opensource/objc4/blob/a367941bce42b...

    In fact – I did not know this before just now – on every arch other than x86-64 it requires a magic assembly sequence to be placed between the call to an autoreleasing method and the call to objc_retainAutoreleaseReturnValue.

    It looks like swiftc implements this by just emitting LLVM inline asm blocks:

        %6 = call %1* bitcast (void ()* @objc_msgSend to %1* (i8*, i8*, %0*)*)(i8* %5, i8* %3, %0* %4) #4

Stats

Basic objc4 repo stats
2
6
0.0
almost 3 years ago

apple-opensource/objc4 is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.

The primary programming language of objc4 is Objective-C++.


Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com