Import tzdata2016d from ftp://ftp.iana.org/tz/releases/tzdata2016d.tar.gz
Summary of changes in tzdata2016d (2016-04-17 22:50:29 -0700):
* America/Caracas switches from -0430 to -04 on 2016-05-01 at 02:30.
* Asia/Magadan switches from +10 to +11 on 2016-04-24 at 02:00.
* New zone Asia/Tomsk, split off from Asia/Novosibirsk.
* New zone Europe/Kirov, split off from Europe/Volgograd.
* Russia and nearby locations had daylight-saving transitions on
1992-03-29 at 02:00 and 1992-09-27 at 03:00, instead of on
1992-03-28 at 23:00 and 1992-09-26 at 23:00.
* Many corrections to historical time in Kazakhstan from 1991
through 2005.
* Mention Internet RFCs 7808 (TZDIST) and 7809 (CalDAV time zone references).
Summary of changes in tzdata2016c (2016-03-23 00:51:27 -0700):
* Azerbaijan no longer observes DST.
* Chile reverts from permanent to seasonal DST.
* Europe/Kaliningrad and Europe/Vilnius changed from +03/+04 to
+02/+03 on 1989-03-26, not 1991-03-31.
* Several updates and URLs for historical and proposed Russian changes.
Import tzdata2016d from ftp://ftp.iana.org/tz/releases/tzdata2016d.tar.gz
Summary of changes in tzdata2016d (2016-04-17 22:50:29 -0700):
* America/Caracas switches from -0430 to -04 on 2016-05-01 at 02:30.
* Asia/Magadan switches from +10 to +11 on 2016-04-24 at 02:00.
* New zone Asia/Tomsk, split off from Asia/Novosibirsk.
* New zone Europe/Kirov, split off from Europe/Volgograd.
* Russia and nearby locations had daylight-saving transitions on
1992-03-29 at 02:00 and 1992-09-27 at 03:00, instead of on
1992-03-28 at 23:00 and 1992-09-26 at 23:00.
* Many corrections to historical time in Kazakhstan from 1991
through 2005.
* Mention Internet RFCs 7808 (TZDIST) and 7809 (CalDAV time zone references).
Summary of changes in tzdata2016c (2016-03-23 00:51:27 -0700):
* Azerbaijan no longer observes DST.
* Chile reverts from permanent to seasonal DST.
* Europe/Kaliningrad and Europe/Vilnius changed from +03/+04 to
+02/+03 on 1989-03-26, not 1991-03-31.
* Several updates and URLs for historical and proposed Russian changes.
Summary of changes in tzdata2016d (2016-04-17 22:50:29 -0700):
* America/Caracas switches from -0430 to -04 on 2016-05-01 at 02:30.
* Asia/Magadan switches from +10 to +11 on 2016-04-24 at 02:00.
* New zone Asia/Tomsk, split off from Asia/Novosibirsk.
* New zone Europe/Kirov, split off from Europe/Volgograd.
* Russia and nearby locations had daylight-saving transitions on
1992-03-29 at 02:00 and 1992-09-27 at 03:00, instead of on
1992-03-28 at 23:00 and 1992-09-26 at 23:00.
* Many corrections to historical time in Kazakhstan from 1991
through 2005.
* Mention Internet RFCs 7808 (TZDIST) and 7809 (CalDAV time zone references).
Summary of changes in tzdata2016c (2016-03-23 00:51:27 -0700):
* Azerbaijan no longer observes DST.
* Chile reverts from permanent to seasonal DST.
* Europe/Kaliningrad and Europe/Vilnius changed from +03/+04 to
+02/+03 on 1989-03-26, not 1991-03-31.
* Several updates and URLs for historical and proposed Russian changes.
number of warnings during build.
XXX There are still some other warnings remaining to be resolved.
Fixes PR bin/48195 although we really should go back someday and fix
this correctly (by replacing all uses of mktemp(3)!)
This is actually unnecessary as the call in question uses only fields
that have been set explicitly, but good practice regardless and it's
not like it's on a performance-critical path.
buffer. If snprintf truncated the output, the length returned will be
greater and we'll write trash. Just call strlen instead. (And since
what we're doing is writing progress messages to the user, checking
carefully for truncation isn't really worthwhile either.)
Spotted when attending to PR 50998 from David Binderman; the issue
there (computation of an unused value) popped up because one of the
prints was already calling strlen.
The loop that picks delay_divisor might conceivably reject all values,
particularly if the hardware is sulking for some reason; in that case
it'll be left zero. Use 1 instead of 0 so we don't then crash.
If we don't find one of the expected device addresses, reject the
match, but do it by checking whether the loop matched something rather
than by testing an array entry that might be one past the end.
Note: I have also moved the test to be with the loop; since the call
to intio_map_allocate_region had gotten placed in between them, I've
moved it to go before rather than after them as (a) it doesn't
interact with the loop itself and (b) this seems like the best choice
given the history as it was deliberately added before the original
test.
I have not tried running this, not having an x68k, but as best I can
tell by reading the intio code it seems like it should be harmless
even if it's not really correct.
do anything with it...) because it's zooming off the end of the array it's
trying to use.
It looks to me as if NEW_MAP_SIZE has been accidentally used as both
the number of blocks occupied by the new partition table and also the
number of entries in it. Or something. This needs platform knowledge
to sort out. XXX.
Workaround for PR 50757.
