Displaying 20 results from an estimated 36516 matches for "break".
2017 Aug 23
4
Possible repeat{} / break function bug in R 3.4.1
It is a bug in the byte-code compiler. I will fix
Tomas
On 08/23/2017 09:22 AM, Lionel Henry wrote:
> I don't think that's a bug. source() uses eval(), and eval() creates a
> new function-like context frame. In a way expecting `break` to work
> inside source() is like expecting `break` to cross stack frames:
>
> my_break <- function() break
> repeat(my_break())
>
> Lionel
>
>
>> On 23 ao?t 2017, at 09:17, Martin Maechler <maechler at stat.math.ethz.ch> wrote:
>>
>>>...
2020 Oct 17
0
[RFC] treewide: cleanup unreachable breaks
...early acks.
>
> clang has a number of useful, new warnings see
> https://urldefense.com/v3/__https://clang.llvm.org/docs/DiagnosticsReference.html__;!!GqivPVa7Brio!I1e3ICrqVVRM26wDg2unWSH5Oo5ddT0f-H6IkP2Hnb2dQ-YGRtaTKw7R_N1dUf3CCbU2CQ$
>
> This change cleans up -Wunreachable-code-break
> https://urldefense.com/v3/__https://clang.llvm.org/docs/DiagnosticsReference.html*wunreachable-code-break__;Iw!!GqivPVa7Brio!I1e3ICrqVVRM26wDg2unWSH5Oo5ddT0f-H6IkP2Hnb2dQ-YGRtaTKw7R_N1dUf1UUJpFjg$
> for 266 of 485 warnings in this week's linux-next, allyesconfig on x86_64.
Early acks/...
2017 Aug 23
2
Possible repeat{} / break function bug in R 3.4.1
....math.ethz.ch>
>>>>> on Wed, 23 Aug 2017 09:10:20 +0200 writes:
>>>>> Peter Bosa <Peter.Bosa at oregonmetro.gov>
>>>>> on Tue, 22 Aug 2017 14:39:50 +0000 writes:
>> Hello, I've noticed the following error using repeat{} / break in R 3.4.1 running on Windows 10 and Windows Server 2008 (both 64-bit environments).
>> When running a repeat function, the break command causes an error message if the repeat command refers to code within a file, but does not produce an error if the code is contained within the repeat{}...
2017 Aug 22
2
Possible repeat{} / break function bug in R 3.4.1
Hello, I've noticed the following error using repeat{} / break in R 3.4.1 running on Windows 10 and Windows Server 2008 (both 64-bit environments).
When running a repeat function, the break command causes an error message if the repeat command refers to code within a file, but does not produce an error if the code is contained within the repeat{} command.
Fo...
2017 Aug 23
0
Possible repeat{} / break function bug in R 3.4.1
I don't think that's a bug. source() uses eval(), and eval() creates a
new function-like context frame. In a way expecting `break` to work
inside source() is like expecting `break` to cross stack frames:
my_break <- function() break
repeat(my_break())
Lionel
> On 23 ao?t 2017, at 09:17, Martin Maechler <maechler at stat.math.ethz.ch> wrote:
>
>>>>>> Martin Maechler <maechler at...
2017 Aug 23
0
Possible repeat{} / break function bug in R 3.4.1
oops, I should have tried it:
expr <- quote(break)
repeat(eval(expr))
So eval() has hybrid semantics where `break` has more reach than
return(), weird.
expr <- quote(return())
repeat(eval(expr)) # infloop
Lionel
> On 23 ao?t 2017, at 09:24, Tomas Kalibera <tomas.kalibera at gmail.com> wrote:
>
> It is a bug in...
2012 Dec 12
2
[PATCH v7 1/2] xen: unify domain locking in domctl code
These two patches were originally part of the XSM series that I have
posted, and remain prerequisites for that series. However, they are
independent of the XSM changes and are a useful simplification
regardless of the use of XSM.
The Acked-bys on these patches were provided before rebasing them over
the copyback changes in 26268:1b72138bddda, which had minor conflicts
that I resolved.
[PATCH
2020 Oct 17
10
[RFC] treewide: cleanup unreachable breaks
...re half way by collecting
early acks.
clang has a number of useful, new warnings see
https://urldefense.com/v3/__https://clang.llvm.org/docs/DiagnosticsReference.html__;!!GqivPVa7Brio!Krxz78O3RKcB9JBMVo_F98FupVhj_jxX60ddN6tKGEbv_cnooXc1nnBmchm-e_O9ieGnyQ$
This change cleans up -Wunreachable-code-break
https://urldefense.com/v3/__https://clang.llvm.org/docs/DiagnosticsReference.html*wunreachable-code-break__;Iw!!GqivPVa7Brio!Krxz78O3RKcB9JBMVo_F98FupVhj_jxX60ddN6tKGEbv_cnooXc1nnBmchm-e_MlpqYEJQ$
for 266 of 485 warnings in this week's linux-next, allyesconfig on x86_64.
The method of fixing...
2020 Oct 17
10
[RFC] treewide: cleanup unreachable breaks
...re half way by collecting
early acks.
clang has a number of useful, new warnings see
https://urldefense.com/v3/__https://clang.llvm.org/docs/DiagnosticsReference.html__;!!GqivPVa7Brio!Krxz78O3RKcB9JBMVo_F98FupVhj_jxX60ddN6tKGEbv_cnooXc1nnBmchm-e_O9ieGnyQ$
This change cleans up -Wunreachable-code-break
https://urldefense.com/v3/__https://clang.llvm.org/docs/DiagnosticsReference.html*wunreachable-code-break__;Iw!!GqivPVa7Brio!Krxz78O3RKcB9JBMVo_F98FupVhj_jxX60ddN6tKGEbv_cnooXc1nnBmchm-e_MlpqYEJQ$
for 266 of 485 warnings in this week's linux-next, allyesconfig on x86_64.
The method of fixing...
2017 Apr 03
2
[PATCH 1/2] drm: virtio: add virtio_gpu_translate_format
...tatic int virtio_gpufb_create(struct drm_fb_helper *helper,
mode_cmd.pitches[0] = mode_cmd.width * 4;
mode_cmd.pixel_format = drm_mode_legacy_fb_format(32, 24);
- switch (mode_cmd.pixel_format) {
-#ifdef __BIG_ENDIAN
- case DRM_FORMAT_XRGB8888:
- format = VIRTIO_GPU_FORMAT_X8R8G8B8_UNORM;
- break;
- case DRM_FORMAT_ARGB8888:
- format = VIRTIO_GPU_FORMAT_A8R8G8B8_UNORM;
- break;
- case DRM_FORMAT_BGRX8888:
- format = VIRTIO_GPU_FORMAT_B8G8R8X8_UNORM;
- break;
- case DRM_FORMAT_BGRA8888:
- format = VIRTIO_GPU_FORMAT_B8G8R8A8_UNORM;
- break;
- case DRM_FORMAT_RGBX8888:
- format = VIRTIO...
2017 Apr 03
2
[PATCH 1/2] drm: virtio: add virtio_gpu_translate_format
...tatic int virtio_gpufb_create(struct drm_fb_helper *helper,
mode_cmd.pitches[0] = mode_cmd.width * 4;
mode_cmd.pixel_format = drm_mode_legacy_fb_format(32, 24);
- switch (mode_cmd.pixel_format) {
-#ifdef __BIG_ENDIAN
- case DRM_FORMAT_XRGB8888:
- format = VIRTIO_GPU_FORMAT_X8R8G8B8_UNORM;
- break;
- case DRM_FORMAT_ARGB8888:
- format = VIRTIO_GPU_FORMAT_A8R8G8B8_UNORM;
- break;
- case DRM_FORMAT_BGRX8888:
- format = VIRTIO_GPU_FORMAT_B8G8R8X8_UNORM;
- break;
- case DRM_FORMAT_BGRA8888:
- format = VIRTIO_GPU_FORMAT_B8G8R8A8_UNORM;
- break;
- case DRM_FORMAT_RGBX8888:
- format = VIRTIO...
2014 Mar 11
2
[PATCH] nv50/ir/gk110: fix some instruction emission
...>srcExists(0) && i->src(0).getFile() == FILE_MEMORY_CONST)
- // code[0] |= 0x4000;
+ code[1] = f->absolute ? 0x11000000 : 0x12000000;
+ if (i->srcExists(0) && i->src(0).getFile() == FILE_MEMORY_CONST)
+ code[0] |= 0x80;
mask = 3;
break;
case OP_CALL:
- code[1] = f->absolute ? 0x00000 : 0x13000000; // XXX
- // if (i->srcExists(0) && i->src(0).getFile() == FILE_MEMORY_CONST)
- // code[0] |= 0x4000;
+ code[1] = f->absolute ? 0x11000000 : 0x13000000;
+ if (i->srcExists(0) &&am...
2017 Aug 23
0
Possible repeat{} / break function bug in R 3.4.1
...:24 AM, Tomas Kalibera wrote:
> It is a bug in the byte-code compiler. I will fix
> Tomas
>
> On 08/23/2017 09:22 AM, Lionel Henry wrote:
>> I don't think that's a bug. source() uses eval(), and eval() creates a
>> new function-like context frame. In a way expecting `break` to work
>> inside source() is like expecting `break` to cross stack frames:
>>
>> my_break <- function() break
>> repeat(my_break())
>>
>> Lionel
>>
>>
>>> On 23 ao?t 2017, at 09:17, Martin Maechler
>>> <maechler at...
2020 Sep 09
17
[trivial PATCH] treewide: Convert switch/case fallthrough; to break;
fallthrough to a separate case/default label break; isn't very readable.
Convert pseudo-keyword fallthrough; statements to a simple break; when
the next label is case or default and the only statement in the next
label block is break;
Found using:
$ grep-2.5.4 -rP --include=*.[ch] -n "fallthrough;(\s*(case\s+\w+|default)\s*:\s*){1,7}bre...
2009 Dec 17
2
Which hist cell each value falls in?
Hi, all. I'm using hist() to obtain a vector of break values in an interval.
I then want to be able to identify which cell any value from another vector
falls in.
E.g. applying
> breaks
[1] -3.5 -3.0 -2.5 -2.0 -1.5 -1.0 -0.5 0.0 0.5 1.0 1.5 2.0
to
> x
[1] -3.74519666 -0.38183630 -1.22884247 -0.20971824 -0.30533939 -0.36271207
[7] -2.2...
2008 May 20
2
hist clarification
Can someone help me with a misunderstanding I'm having with hist? I
expected, from the example below, that the number of bins would always be 10
and the length of the counts array the same. According to the help section
'breaks' can be a integer indicating the number of bins. From the example
below, the number of bins (length of the counts array) varies. Am I wrong in
expecting the same number of bins every time from my hist() call (am I doing
something wrong)?
> hist(rnorm(1000),breaks=10)$counts;
[1] 2 10...
2010 Sep 19
1
help interpreting a model summary
...39;ve just build up a piecewise linear model to fit some data,
including some interaction and i am not sure of how to interpret the
summary:.
here it is:
--------------------------------------------------------------------------------
Call:
lm(formula = weightedDiff ~ angleNoise + (reflection < Break[xMin]) *
reflection + (reflection >= Break[xMin]) * reflection +
angleNoise:(reflection <
Break[xMin]) * reflection + angleNoise:(reflection >= Break[xMin]) *
reflection)
Residuals:
Min 1Q Median 3Q Max
-1.073e-03 -1.749e-04 -5.913e-06 1.650e-...
2023 Jul 14
2
[PATCH] drm/nouveau/fifo:Fix Nineteen occurrences of the gk104.c error: ERROR: : trailing statements should be on next line
...pu/drm/nouveau/nvkm/engine/fifo/gk104.c
@@ -137,15 +137,29 @@ gk104_ectx_bind(struct nvkm_engn *engn, struct
nvkm_cctx *cctx, struct nvkm_chan
u64 addr = 0ULL;
switch (engn->engine->subdev.type) {
- case NVKM_ENGINE_SW : return;
- case NVKM_ENGINE_GR : ptr0 = 0x0210; break;
- case NVKM_ENGINE_SEC : ptr0 = 0x0220; break;
- case NVKM_ENGINE_MSPDEC: ptr0 = 0x0250; break;
- case NVKM_ENGINE_MSPPP : ptr0 = 0x0260; break;
- case NVKM_ENGINE_MSVLD : ptr0 = 0x0270; break;
- case NVKM_ENGINE_VIC : ptr0 = 0x0280; break;
- case NVKM_ENGINE_MSENC : ptr0 = 0...
2017 Apr 06
1
[bug] in cut.POSIXt(..., breaks = <numeric>)
The exact error was reported before in *Bug 14288*
<https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=14288> *- **bug in
cut.POSIXt(..., breaks = <numeric>) and cut.Date. *But the fix in that bug
report only covered the simplest case.
This is the error I met
-----------------------------
x <- structure(c(1057067700, 1057215720, 1060597800, 1061470800,
1061911680,
1062048000, 1062137880, 1064479440, 1064926380, 1064995140, 10668...
2023 Jul 14
1
[PATCH] drm/nouveau/fifo:Fix Nineteen occurrences of the gk104.c error: ERROR: space prohibited before that ':' (ctx:WxW) ERROR: trailing statements should be on next line ERROR: space prohibited before that ':' (ctx:WxW) ERROR: trailing statements should
...pu/drm/nouveau/nvkm/engine/fifo/gk104.c
@@ -137,15 +137,29 @@ gk104_ectx_bind(struct nvkm_engn *engn, struct
nvkm_cctx *cctx, struct nvkm_chan
u64 addr = 0ULL;
switch (engn->engine->subdev.type) {
- case NVKM_ENGINE_SW : return;
- case NVKM_ENGINE_GR : ptr0 = 0x0210; break;
- case NVKM_ENGINE_SEC : ptr0 = 0x0220; break;
- case NVKM_ENGINE_MSPDEC: ptr0 = 0x0250; break;
- case NVKM_ENGINE_MSPPP : ptr0 = 0x0260; break;
- case NVKM_ENGINE_MSVLD : ptr0 = 0x0270; break;
- case NVKM_ENGINE_VIC : ptr0 = 0x0280; break;
- case NVKM_ENGINE_MSENC : ptr0 = 0...