Displaying 15 results from an estimated 15 matches for "t1x".
Did you mean:
t1
2019 Apr 05
6
all.equal failure
This arose in testing [.terms and has me confused.
data(esoph)?? # use a standard data set
t0x <- terms(model.frame( ~ tobgp, data=esoph))
t1 <-? terms(model.frame(ncases ~ agegp + tobgp, data=esoph))
t1x <- (delete.response(t1))[-1]
> all.equal(t0x, t1x)
[1] TRUE
# the above is wrong, because they actually are not the same
> all.equal(attr(t0x, 'dataClasses'), attr(t1x, 'dataClasses'))
[1] "Names: 1 string mismatch"
[2] "Lengths (1, 2) differ (string com...
2019 Apr 05
0
[EXTERNAL] Re: all.equal failure
On 05/04/2019 10:19 a.m., Therneau, Terry M., Ph.D. wrote:
> Duncan,
> ? I should have included it in my original note, but
>
> ?? ? all.equal(unclass(t0x), unclass(t1x))
>
> returns TRUE as well.? I had tried that as well. ? But a further look at
> all.equal.default shows the following line right near the top:
> ??? if (is.language(target) || is.function(target))
> ??????? return(all.equal.language(target, current, ...))
>
> and that pat...
2019 Apr 05
0
[EXTERNAL] Re: Re: all.equal failure
...ry M., Ph.D. wrote:
>
>
> On 4/5/19 9:39 AM, Duncan Murdoch wrote:
>> On 05/04/2019 10:19 a.m., Therneau, Terry M., Ph.D. wrote:
>>> Duncan,
>>> ?? I should have included it in my original note, but
>>>
>>> ??? ? all.equal(unclass(t0x), unclass(t1x))
>>>
>>> returns TRUE as well.? I had tried that as well. ? But a further look at
>>> all.equal.default shows the following line right near the top:
>>> ???? if (is.language(target) || is.function(target))
>>> ???????? return(all.equal.language(target...
2019 Apr 05
0
all.equal failure
...9:03 a.m., Therneau, Terry M., Ph.D. via R-devel wrote:
> This arose in testing [.terms and has me confused.
>
> data(esoph)?? # use a standard data set
>
> t0x <- terms(model.frame( ~ tobgp, data=esoph))
> t1 <-? terms(model.frame(ncases ~ agegp + tobgp, data=esoph))
> t1x <- (delete.response(t1))[-1]
>
> > all.equal(t0x, t1x)
> [1] TRUE
>
> # the above is wrong, because they actually are not the same
>
> > all.equal(attr(t0x, 'dataClasses'), attr(t1x, 'dataClasses'))
> [1] "Names: 1 string mismatch"
&...
2019 Apr 05
3
[EXTERNAL] Re: Re: all.equal failure
...4/5/19 9:39 AM, Duncan Murdoch wrote:
>>> On 05/04/2019 10:19 a.m., Therneau, Terry M., Ph.D. wrote:
>>>> Duncan,
>>>> ?? I should have included it in my original note, but
>>>>
>>>> ??? ? all.equal(unclass(t0x), unclass(t1x))
>>>>
>>>> returns TRUE as well.? I had tried that as well. ? But a further look at
>>>> all.equal.default shows the following line right near the top:
>>>> ???? if (is.language(target) || is.function(target))
>>>> ??...
2019 Apr 05
0
[EXTERNAL] Re: Re: all.equal failure
...ch wrote:
> >>> On 05/04/2019 10:19 a.m., Therneau, Terry M., Ph.D. wrote:
> >>>> Duncan,
> >>>> ?? I should have included it in my original note, but
> >>>>
> >>>> ??? ? all.equal(unclass(t0x), unclass(t1x))
> >>>>
> >>>> returns TRUE as well.? I had tried that as well. ? But a further look at
> >>>> all.equal.default shows the following line right near the top:
> >>>> ???? if (is.language(target) || is.function(target))...
2017 Oct 11
1
[PATCH v1 01/27] x86/crypto: Adapt assembly for PIE support
...it a/arch/x86/crypto/glue_helper-asm-avx2.S b/arch/x86/crypto/glue_helper-asm-avx2.S
index a53ac11dd385..e04c80467bd2 100644
--- a/arch/x86/crypto/glue_helper-asm-avx2.S
+++ b/arch/x86/crypto/glue_helper-asm-avx2.S
@@ -67,7 +67,7 @@
vmovdqu (iv), t2x; \
vmovdqa t2x, t3x; \
inc_le128(t2x, t0x, t1x); \
- vbroadcasti128 bswap, t1; \
+ vbroadcasti128 bswap(%rip), t1; \
vinserti128 $1, t2x, t3, t2; /* ab: le0 ; cd: le1 */ \
vpshufb t1, t2, x0; \
\
@@ -124,13 +124,13 @@
tivx, t0, t0x, t1, t1x, t2, t2x, t3, \
xts_gf128mul_and_shl1_mask_0, \
xts_gf128mul_and_shl1...
2009 Nov 04
1
[PATCH] nv10/exa: Spring-cleaning
...an, vy);
- OUT_RINGf (chan, 0.f);
-}
+#define MAP(f, p, v, ...) do { \
+ int __i; \
+ for (__i = 0; __i < sizeof(v)/sizeof(*(v)); __i++) \
+ f(p, __i, v, ## __VA_ARGS__); \
+ } while (0);
-static inline void NV10MVertex(NVPtr pNv, float vx, float vy, float t0x, float t0y, float t1x, float t1y)
+#define xFixedToFloat(v) \
+ ((float)xFixedToInt((v)) + ((float)xFixedFrac(v) / 65536.0))
+
+#define OUT_RINGi(chan, v, i) \
+ OUT_RINGf(chan, xFixedToFloat((v).vector[i]))
+
+static inline void
+emit_vertex(NVPtr pNv, int i, PictVector pos[],
+ PictVector tex0[], PictVector tex...
2018 Mar 13
32
[PATCH v2 00/27] x86: PIE support and option to extend KASLR randomization
Changes:
- patch v2:
- Adapt patch to work post KPTI and compiler changes
- Redo all performance testing with latest configs and compilers
- Simplify mov macro on PIE (MOVABS now)
- Reduce GOT footprint
- patch v1:
- Simplify ftrace implementation.
- Use gcc mstack-protector-guard-reg=%gs with PIE when possible.
- rfc v3:
- Use --emit-relocs instead of -pie to reduce
2018 Mar 13
32
[PATCH v2 00/27] x86: PIE support and option to extend KASLR randomization
Changes:
- patch v2:
- Adapt patch to work post KPTI and compiler changes
- Redo all performance testing with latest configs and compilers
- Simplify mov macro on PIE (MOVABS now)
- Reduce GOT footprint
- patch v1:
- Simplify ftrace implementation.
- Use gcc mstack-protector-guard-reg=%gs with PIE when possible.
- rfc v3:
- Use --emit-relocs instead of -pie to reduce
2017 Oct 04
28
x86: PIE support and option to extend KASLR randomization
These patches make the changes necessary to build the kernel as Position
Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below
the top 2G of the virtual address space. It allows to optionally extend the
KASLR randomization range from 1G to 3G.
Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler
changes, PIE support and KASLR in general. Thanks to
2017 Oct 04
28
x86: PIE support and option to extend KASLR randomization
These patches make the changes necessary to build the kernel as Position
Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below
the top 2G of the virtual address space. It allows to optionally extend the
KASLR randomization range from 1G to 3G.
Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler
changes, PIE support and KASLR in general. Thanks to
2018 May 23
33
[PATCH v3 00/27] x86: PIE support and option to extend KASLR randomization
Changes:
- patch v3:
- Update on message to describe longer term PIE goal.
- Minor change on ftrace if condition.
- Changed code using xchgq.
- patch v2:
- Adapt patch to work post KPTI and compiler changes
- Redo all performance testing with latest configs and compilers
- Simplify mov macro on PIE (MOVABS now)
- Reduce GOT footprint
- patch v1:
- Simplify ftrace
2017 Oct 11
32
[PATCH v1 00/27] x86: PIE support and option to extend KASLR randomization
Changes:
- patch v1:
- Simplify ftrace implementation.
- Use gcc mstack-protector-guard-reg=%gs with PIE when possible.
- rfc v3:
- Use --emit-relocs instead of -pie to reduce dynamic relocation space on
mapped memory. It also simplifies the relocation process.
- Move the start the module section next to the kernel. Remove the need for
-mcmodel=large on modules. Extends
2017 Oct 11
32
[PATCH v1 00/27] x86: PIE support and option to extend KASLR randomization
Changes:
- patch v1:
- Simplify ftrace implementation.
- Use gcc mstack-protector-guard-reg=%gs with PIE when possible.
- rfc v3:
- Use --emit-relocs instead of -pie to reduce dynamic relocation space on
mapped memory. It also simplifies the relocation process.
- Move the start the module section next to the kernel. Remove the need for
-mcmodel=large on modules. Extends