search for: what'll

...ywhere near as weird as you're framing them to be. :) I now think this weirdness actually does not have to do anything with guard_on or bail_to_interpeter, but it has to do with deopt bundles itself. Our notion of of "deopt bundles are readonly" is broken to begin with, and that is what's manifesting as the complication we're seeing here. Consider something like ``` declare @foo() readonly def @bar() { call @foo() [ "deopt"(XXX) ] } def @baz() { call @bar() [ "deopt"(YYY) ] } ``` Right now according to the semantics of "deopt" operand bundl...

Some general comments on using the patch: * For libguestfs I chose to add -compat deprecated-input=reject,deprecated-output=hide This is only enabled in developer builds of libguestfs when we are running qemu directly (not via libvirt). The patch for this is attached. * What's the point/difference in having reject vs crash? * I hope that by hiding deprecated QAPI fields we may detect errors in libguestfs, but I suspect what'll happen is it'll cause fall-back behaviour which might be harder to detect. * Be *really* good to have this for command line pa...

Full_Name: Stephen Milborrow Version: R 2.8.0 OS: Windows XP Submission from: (NULL) (81.159.65.46) Under certain conditions, R 2.8.0 incorrectly echoes integer literals without the "L" suffix. R 2.7.2 is ok. To reproduce, create two files as follows: a.R containing: source("b.R", echo=TRUE) b.R containing: x <- 1L Now execute: Rterm --vanilla --silent <a.R This

...lt;- 1 > It should echo: x <- 1L > > This behaviour does not occur if you source("b.R") directly from the R command > prompt, or if you use R 2.7.2. It works fine for me. Could you try changing b.R to contain a comment, e.g. x <- # a comment 1L and let us know what you see in the two cases? I'm guessing you won't see the comment being echoed when you source a.R because for some reason your system is deparsing instead of going back to the source to read it, but I don't know what'll happen with b.R. Duncan Murdoch > >> sessionInfo...

I am new to Asterisk so can I start by apologising if this question has been asked and answered already. I'm in the UK using BT for two incoming lines, one on Wildcard TDM400P and the other on Wildcard X100P. I also have a SIP connection to voiptalk.org. Incoming calls via SIP/broadband ring on extensions immediately. However, an incoming call via PSTN is displayed on the CLI as an

On Tue, Mar 22, 2016 at 5:03 PM, David Blaikie <dblaikie at gmail.com> wrote: > Could we change the buildbot config to treat > warnings-as-errors-that-continue in the build step? (so we get the benefit > of further execution tests, while still sending fail-mail, etc for the > warning?) > > That sounds reasonable, although the buildbot implementation seems to be pretty

I am experiencing a situation where I am getting intermittent choppy audio. Here is the network layout: Termination provider -> IAX2 over the Internet -> 20Mb fiber connection -> router -> Asterisk My ATA connection goes into the router between the fiber and the Asterisk server on another interface here is the layout from me to Asterisk: Sipura ATA (SPA1001 running

New option -compat lets you configure what to do when deprecated interfaces get used. This is intended for testing users of the management interfaces. It is experimental. -compat deprecated-input=<in-policy> configures what to do when deprecated input is received. Available policies: * accept: Accept deprecated commands and argum...

I was looking at the libvorbis 1.0 SRPM of Mandrakelinux, and it contained some patches which are not included in vorbis 1.1 svn. I'm attaching these patches here, because it could maybe be interesting to include these upstream. (libvorbis-1.1-aliasing.patch is actually a rediffed patch of Mandrakesoft's one for 1.0 against 1.1 svn). The author of these patches is Gwenole Beachesne,

...y available. Yes! Actually, I had exactly this in an earlier version of this writeup, which I removed to make the (already long) RFC shorter. > I'd suggest a small change to Sanjoy's declaration. I think we should allow > additional arguments to the guard, not just the condition. What exactly > those arguments mean would be up to the runtime, but various runtimes might > want to provide additional arguments to the OSR mechanism. We'll still have to make a call on the signature of the intrinsic (or are you suggesting a varargs intrinsic)? I suppose we could also have...

...strings and type units as a sort of archival (like dsym) format. The way DWPs work, roughly (full/more details here: https://gcc.gnu.org/wiki/DebugFissionDWP ) is that all the sections are concatenated together, except the debug_str and debug_str_offsets sections which have special handling to do what you'd expect - deduplicate strings, and adjust the str_offsets to point to the right offsets in the deduplicated string section. The other thing that DWP has, is an index, or two. cu_index and tu_index. We'll just look at cu_index. A cu_index for the cab.dwp above, is: Index Signature...