Re: -iface option to route(8) is broken

On 1/8/13 9:28 AM, Hiroki Sato wrote: Julian Elischer wrote in <50ec51a3.6020...@freebsd.org>: ju> On 1/8/13 6:42 AM, Ian FREISLICH wrote: ju> > Hi ju> > ju> > Adding routes using the -iface option to route(8) doesn't work any ju> > more. This was useful to select a specific interface for a

Re: -iface option to route(8) is broken

Julian Elischer wrote in <50ec51a3.6020...@freebsd.org>: ju> On 1/8/13 6:42 AM, Ian FREISLICH wrote: ju> > Hi ju> > ju> > Adding routes using the -iface option to route(8) doesn't work any ju> > more. This was useful to select a specific interface for a route ju> > when the remote gateway has

Re: -iface option to route(8) is broken

On 1/8/13 6:42 AM, Ian FREISLICH wrote: Hi Adding routes using the -iface option to route(8) doesn't work any more. This was useful to select a specific interface for a route when the remote gateway has the same IP address. Are there plans to restore this functionality? I agree.. thus was a

standards/173421: [patch] strptime() accepts formats that should be rejected

Anyone interested in a PR for a strptime() bug coming with a test case and a potential fix? > http://www.freebsd.org/cgi/query-pr.cgi?pr=173421 > > >Category: standards > >Responsible:freebsd-standards > >Synopsis: [patch] strptime() accepts formats that should be rejected > >Arri

Re: clang 3.2 RC2 miscompiles libgcc?

08.01.2013 03:21, Dimitry Andric пишет: > Can you please try the attached patch, which is a very horrid, atrocious > hack, and will only work for amd64. Then rebuild libgcc with clang, and > please try if this fixes at least some of the crashes... The patch fixed building editors/libreoffice. Wi

-iface option to route(8) is broken

Hi Adding routes using the -iface option to route(8) doesn't work any more. This was useful to select a specific interface for a route when the remote gateway has the same IP address. Are there plans to restore this functionality? tun0: flags=8051 metric 0 mtu 1492 options=8

Re: sysctl -a causes kernel trap 12

d wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 1/7/13 5:33 PM, Brandon Gooch wrote: > > On Mon, Jan 7, 2013 at 6:09 PM, Xin Li > > wrote: > > > > -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 > > > > On 01/07/13 16:02, Konstantin Belousov wrote:

Re: [RFC/RFT] calloutng

On Tue, Jan 08, 2013 at 12:55:27PM +0200, Alexander Motin wrote: > On 06.01.2013 18:20, Luigi Rizzo wrote: ... > > I think that for the time being it would be useful to run at least > > one set of tests with kern.timecounter.alloweddeviation=0 so we can > > tell how close we get to the required tim

Re: [RFC/RFT] calloutng

On 06.01.2013 18:20, Luigi Rizzo wrote: > On Sun, Jan 06, 2013 at 04:23:13PM +0100, Marius Strobl wrote: >> On Wed, Dec 26, 2012 at 09:24:46PM +0200, Alexander Motin wrote: >>> Here is small tool we are using for test correctness and performance of >>> different user-level APIs: http://people.free

Re: [RFC/RFT] calloutng

On 06.01.2013 17:23, Marius Strobl wrote: > On Wed, Dec 26, 2012 at 09:24:46PM +0200, Alexander Motin wrote: >> On 26.12.2012 01:21, Marius Strobl wrote: >>> On Tue, Dec 18, 2012 at 11:03:47AM +0200, Alexander Motin wrote: Experiments with dummynet shown ineffective support for very short

Re: clang 3.2 RC2 miscompiles libgcc?

On 2013-01-08 09:08, David Chisnall wrote: On 7 Jan 2013, at 23:21, Dimitry Andric wrote: This is at least the direction I'm looking at. It seems that in some cases with __builtin_eh_return(), llvm does not see that registers can be clobbered, and it doesn't save and restore them. Do you mean

Re: clang 3.2 RC2 miscompiles libgcc?

On Tue, Jan 08, 2013 at 12:21:12AM +0100, Dimitry Andric wrote: > On 2013-01-06 17:03, Stefan Farfeleder wrote: > > On Sun, Jan 06, 2013 at 03:59:59PM +0100, Dimitry Andric wrote: > ... > > The bug also affects ports software, e.g., I also experienced strange > > rtorrent segfaults that are now gon

Re: clang 3.2 RC2 miscompiles libgcc?

On 7 Jan 2013, at 23:21, Dimitry Andric wrote: > This is at least the direction I'm looking at. It seems that in some > cases with __builtin_eh_return(), llvm does not see that registers can > be clobbered, and it doesn't save and restore them. Do you mean that some registers were clobbered by a