- clarify and correct the notes on the format of the file on top;
- remove spurious trailing whitespace on several places;
- update `Version' (4.1.34 was imported on 2010-04-17) and `Current
Version' fields for the `ipf' entry, as well as correct the path
to its license file (which uses the non-American spelling, using
a `c' instead of an `s') and use a semicolon in its line instead
of a comma;
- update / correct `Curr Vers', `Home page' and `Notes' fields for
the pkg_install entry, as well as correct some minor typing
mistakes there;
- add note for the license change for rcs-5.8;
- since 5.8 is released, change the note on rcs concerning its
Purdue FTP site (the line as it was dates from r1.1 of this file);
- clarify the license field for the `texinfo' entry;
- update version fields of the `services' / `protocols' entry,
split those for the two (like was already done for the `Archive
Site' field in r1.780 of this file), clarify the `Archive Site'
fields for the two, and add a trailing slash (`/') to its `Home
Page' field.
with improved German translations from Martin Husemann and Julian
Djamil Fagir. French, Spanish, and Polish translations are
still needed. OK christos, riz.
- Rework p5pb driver - simplify, cleanup, make more flexible.
- Add p5membar driver, which handles PCI resources autoconfigured by the firmware.
- Introduce intermediate p5bus layer, between zbus and CSPPC/BPPC on-board devices (p5pb, cbiiisc, bppcsc).
- Add experimental G-REX support to p5pb (first slot support only).
- Split CV64/3D PCI bridge support into separate cv3dpb driver (to be committed later).
Approved by phx.
GCC can generate bogus dwarf attributes with DW_AT_byte_size set to 0xFFFFFFFF.
See http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35998 .
GCC is currently doing this for external/bsd/tmux/dist/compat/imsg-buffer.c:
readelf -a --debug-dump imsg-buffer.o
...
<2><6e3>: Abbrev Number: 32 (DW_TAG_union_type)
<6e4> DW_AT_byte_size : 0xffffffff
<6e8> DW_AT_decl_file : 1
<6e9> DW_AT_decl_line : 229
<6ea> DW_AT_sibling : <0x705>
This resulted in ctfconvert generating a faulty CTF entry which then caused the
segfault in ctfmerge.
The fix has ctfconvert check for the bogus 0xFFFFFFFF value and works around it.
It also adds some protection to ctfmerge to avoid the segfault and fail
more gracefully if the error should occur in the future.
