7dec7afe4b
Introduce new attribute classes: * addrptr represents an offset into the .debug_addr_section * loclist represents an offset or an index to a location list * rangelist represents an offset or an index to a range list * stroffsetsptr represents an index to the indirect string table The semantics of some existing attribute classes changed: * loclistptr represents an offset into the .debug_loc / .debug_loclist section It will be used only when setting loclists_base attribute. In all other places we should use loclist attribute class. * rangelistptr represents an offset into the .debug_ranges / .debug_rnglist section It will be used only when setting rnglists_base attribute. In all other places we should use rangelist attribute class. Define lookup table for new DW_AT_* attribute types * change the existing references to AC_LOCLISTPTR to AC_LOCLIST as in those places now either an index or an offset can be accepted (previously there were no indexes, only offsets everywhere) * only DW_AT_loclists_base uses AC_LOCLISTPTR * similarly for AC_RANGELISTPTR and AC_RANGELIST as ranges can be specified using either an index or an offset * only DW_AT_rnglists_base uses AC_RANGELISTPTR Define lookup table for new DW_FORM_* attribute forms * similar reshuffle for location lists and range lists Change-Id: I78d307889cd6082a19870afdc571dc0c83d19644 Reviewed-on: https://review.haiku-os.org/c/haiku/+/6982 Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org> Reviewed-by: Adrien Destugues <pulkomandy@pulkomandy.tk> Reviewed-by: waddlesplash <waddlesplash@gmail.com> |
||
|---|---|---|
| 3rdparty | ||
| build | ||
| data | ||
| docs | ||
| headers | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| .gitreview | ||
| configure | ||
| Jamfile | ||
| Jamrules | ||
| lgtm.yml | ||
| License.md | ||
| ReadMe.Compiling.md | ||
| ReadMe.md | ||
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:
- https://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.