search for: l106

Oops, I neglected to reply-all…. The current stable branch at github still has it: https://github.com/apple/swift-llvm/blob/stable/include/llvm/Support/ARMTargetParser.def#L106 <https://github.com/apple/swift-llvm/blob/stable/include/llvm/Support/ARMTargetParser.def#L106> Should I get the head of the non-swift repository and generate a new diff? Also, I suspect that it’s not a good idea to have armv6l map to armv6k, because that seems like quite an assumption to m...

> You assume triples make sense. That's the first mistake everyone does > when thinking about triples. :) I know they don't make sense in many corner cases, but I think discarding logic where it *does* exist is a mistake. > AFAIK, "ARMv7B" is only used by HighBank, which is no more. But that, > too, was "ARMv7A big endian". I believe it's what any

...contain positional information. This makes the internal query code reset the AND-context, which in effect frees its postlist. One of the postlist entries is still pointed at by the `hint` field of QueryOptimiser from a previous submatch, and the next call to `get_hint_postlist` in queryoptimiser.h#L106 references the bogus address. A fix to avoid this is simple: just reset the QueryOptimiser hint field when free'ing the context postlist. I've written a one-liner for this here [3]. But I'm not yet convinced that's all there is: could the hint field be used already somewhere else?...

...lon.com <mailto:william at housedillon.com>> wrote: >>> Oops, I neglected to reply-all…. >>> >>> The current stable branch at github still has it: >>> >>> https://github.com/apple/swift-llvm/blob/stable/include/llvm/Support/ARMTargetParser.def#L106 <https://github.com/apple/swift-llvm/blob/stable/include/llvm/Support/ARMTargetParser.def#L106> >>> >>> Should I get the head of the non-swift repository and generate a new diff? >>> >>> Also, I suspect that it’s not a good idea to have armv6l map to armv...

...`size` argument is very small. For example qnbinom(0.5, mu = 3, size = 1e-10) takes ~30 seconds on my computer. I used gdb to step through the qnbinom.c implementation and noticed that in line 106 (https://github.com/wch/r-source/blob/f8d4d7d48051860cc695b99db9be9cf439aee743/src/nmath/qnbinom.c#L106) `y` becomes a very large negative number. Later in the function `y` is (as far as I can see) only used as input for `pnbinom()` which is why I would assume that it should be a non-negative integer. I was wondering if this behavior could be considered a bug and should be reported on the bugzilla?...

Taking the suggestions of the group under consideration, I’ve generated a new diff. The thing to note is that armv6l is now treated identically to armv6hl. I’ve also added a unit test. This seems to me to be the least invasive method, and holds to existing conventions as closely as possible. Thoughts? -------------- next part -------------- A non-text attachment was scrubbed... Name:

...For example > qnbinom(0.5, mu = 3, size = 1e-10) > takes ~30 seconds on my computer. > > I used gdb to step through the qnbinom.c implementation and noticed > that in line 106 > (https://github.com/wch/r-source/blob/f8d4d7d48051860cc695b99db9be9cf439aee743/src/nmath/qnbinom.c#L106) > `y` becomes a very large negative number. Later in the function `y` is > (as far as I can see) only used as input for `pnbinom()` which is why > I would assume that it should be a non-negative integer. > > I was wondering if this behavior could be considered a bug and should >...

...explicitly checked for like the `int` == 32bits assumption. [1]: https://github.com/wch/r-source/blob/tags/R-3-6-3/src/main/valid_utf8.h#L61 [2]: https://github.com/wch/r-source/blob/tags/R-3-6-3/src/main/character.c#L148 [3]: https://github.com/wch/r-source/blob/tags/R-3-6-3/src/main/valid_utf8.h#L106 [4]: https://github.com/wch/r-source/blob/tags/R-3-6-3/src/main/valid_utf8.h#L84 [5]: https://github.com/wch/r-source/blob/tags/R-3-6-3/src/main/valid_utf8.h#L69 [6]: https://github.com/wch/r-source/blob/tags/R-3-6-3/src/main/connections.c#L3935 [7]: https://github.com/wch/r-source/blob/tags/R-3-6-...

...inom(0.5, mu = 3, size = 1e-10) > > takes ~30 seconds on my computer. > > > > I used gdb to step through the qnbinom.c implementation and noticed > > that in line 106 > > (https://github.com/wch/r-source/blob/f8d4d7d48051860cc695b99db9be9cf439aee743/src/nmath/qnbinom.c#L106) > > `y` becomes a very large negative number. Later in the function `y` is > > (as far as I can see) only used as input for `pnbinom()` which is why > > I would assume that it should be a non-negative integer. > > > > I was wondering if this behavior could be consider...

Hi, everyone, I've recently bought a UPS from Mecer. This is a South African brand that basically resells Mustek hardware, and this UPS is no exception; it's a Mustek product. It does come with software for Linux, but that is terrible (the background process that monitors the UPS is written in Java and needs a terminal to start properly, so you can't run it from a startup script...

Hi, everyone, I've recently bought a UPS from Mecer. This is a South African brand that basically resells Mustek hardware, and this UPS is no exception; it's a Mustek product. It does come with software for Linux, but that is terrible (the background process that monitors the UPS is written in Java and needs a terminal to start properly, so you can't run it from a startup script...