You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some differences in features between current Soil implementations. Some of this is because of differing states of maintenance, but certain features may not make sense for some use cases.
For example, the kernel module omits floating point support, since floating point arithmetic is not generally usable in the Linux kernel. Also, some syscalls, e.g. those related to graphics, may not be always be available.
Proposal
Introduce a new section kind features. I see two possible implementations here:
Make the section word-sized and define each bit to toggle a feature from a fixed list, to be defined in the specification.
Make the section a list of key-value pairs of feature names to values.
While the first solution is more efficient in terms of binary size, the second allows for greater flexibility in feature definition and could also allow for non-boolean features.
The text was updated successfully, but these errors were encountered:
There are some differences in features between current Soil implementations. Some of this is because of differing states of maintenance, but certain features may not make sense for some use cases.
For example, the kernel module omits floating point support, since floating point arithmetic is not generally usable in the Linux kernel. Also, some syscalls, e.g. those related to graphics, may not be always be available.
Proposal
Introduce a new section kind
features
. I see two possible implementations here:While the first solution is more efficient in terms of binary size, the second allows for greater flexibility in feature definition and could also allow for non-boolean features.
The text was updated successfully, but these errors were encountered: