and add a -Werror replacement for Solaris Studio.

This only makes Solaris Studio work with the default options, not for
--enable-developer-warnings

Partly addresses #2047

rather than the values from pkg-config only. CLAGS and LIBS
may contain important generic compiler / linker flags for this
platform.

test "x$ac_cv_prog_cc_c99" = "x" breaks autoconf for compilers which do not need
any extra arguments to support c99.

Partly addresses #2047

fix #2027

For match_tag == SLT_Timestamp, we'd miss a match otherwise.
Add the missing /* FALLTHROUGH */

This reverts commit 97bfb002.

If a log transaction is parsed that don't contain timestamps
(e.g. they are filtered in varnishd), then this would cause a NULL
pointer dereference.

Fix an issue where the new timestamp was set without locking.

Spotted by: Coverity

Spotted by: Coverity

It was counter-intuitive that, for pass objects, we logged the
parsed TTL when in fact the ttl visible from vcl was always 0.
In the builtin.vcl the Hit-For-Pass check was also called
for objects already classified as uncacheable.

Now, for passes, we

- do not parse Cache-Control / Expires
  - and, consequently, do not log TTL RFC
- do not call the hfp-code in builtin.vcl
  - and, consequently, do not log TTL VCL

Reflect this in b2.vtc

called

For some (out of workspace or stevedore allocationi failure) errors
VFP_Close would fail to be called when ending up not retrying the
fetch. This would then potentially leak VFP entry context data like
gzip buffers. Fix this by always calling VFP_Close() when changing
fetch state when VFP_Open() has been called.

Also VFP_Close() would for some retries be called twice, causing
double accounting log records print out. This happens when a late
error is caught and streaming is disabled, allowing a retry to be
attempted. Fix this by not unconditionally calling VFP_Close() in the
error state.

Also spring some VUT_Error() love.

Refs #2008

The child_poker lives in the manager process, and sends pings to the
child. With this patch we check that we actually get a PONG back, and
not some random data. If problems are detected, we kill the child.

Related to: #2010