search for: 111643

...eems to be that `outs()` returns a static object > > created from `raw_fd_stream(STDOUT_FILENO, true)` - the `true` being > > the `shouldClose` parameter. > > > > Surely LLVM is not supposed to close `stdout` as part of its operations? > > Looks like this was added in r111643: > > commit 5d56d9df928c48571980efe8d4205de8ab557b7c > Author: Dan Gohman <gohman at apple.com> > Date: Fri Aug 20 16:44:56 2010 +0000 > > Make outs() close its file when its stream is destructed, so that > pending output errors are detected. > > >...

I was just fixing a bug that was caused by `stdout` being closed before the runtime has done `fflush(stdout)` [or however this is implemented in the runtime]. The cause of this seems to be that `outs()` returns a static object created from `raw_fd_stream(STDOUT_FILENO, true)` - the `true` being the `shouldClose` parameter. Surely LLVM is not supposed to close `stdout` as part of its operations?

We have recently switched providers, and have been re-assigned a network in the 72.0.0.0 block, which was released last year. We are finding a significant number of sites that are filtering traffic from the 70/71/72 networks due to them being previously reserved. Trying to change this is like pushing a rope. So we are considering trying to NAT our outgoing proxy, incoming web, and mail