Slight API change, finalization of (desktop) UI (gotta do mobile web view still)
This commit is contained in:
@ -76,12 +76,14 @@ Gets a (paginated) list of all C/C++(-like) types used by the intrinsics. The ty
|
||||
Searches the database using the given filters. The filters are passed as query parameters, and can be combined. All filters are optional. The following filters are available:
|
||||
- `name=[string]`: searches based on the name of the intrinsic; employs fuzzy-search (using `LIKE %it%`)
|
||||
- `return=[string]`: searches based on the return type of the intrinsic; exact search only
|
||||
- `cpuid=[string]`: searches based on the CPUID of the intrinsic; exact search only
|
||||
- `tech=[string]`: searches based on the technology of the intrinsic; exact search only
|
||||
- `category=[string]`: searches based on the category of the intrinsic; exact search only
|
||||
- `cpuid=[*]`: searches based on the CPUID of the intrinsic; exact search only
|
||||
- `tech=[*]`: searches based on the technology of the intrinsic; exact search only
|
||||
- `category=[*]`: searches based on the category of the intrinsic; exact search only
|
||||
- `desc=[string]`: searches based on the description of the intrinsic; employs fuzzy-search (using `LIKE %it%`)
|
||||
- `page=[int]`: specifies the page number to return (default is 0)
|
||||
|
||||
Parameters marked by `[*]` are JSON-lists (so you should pass them as `cpuid=["PREFETCHI", "SSE2"]`). They are considered to be OR-ed together (i.e. the results will contain a mix of all intrinsics matching either of the CPUIDs (from the example)).
|
||||
|
||||
Passing no filters is equivalent to using `GET /all`, and data is returned in the same format:
|
||||
```json
|
||||
{
|
||||
|
Reference in New Issue
Block a user