Displaying 6 results from an estimated 6 matches for "l619".
Did you mean:
619
2016 Dec 16
2
Upgrading a package to which other packages are LinkingTo
...4], just like the warning when packages are built against a
different version of R.
Thanks.
Best regards
Kirill
[1] https://github.com/hadley/dplyr/issues/2308#issuecomment-267495075
[2] https://travis-ci.org/krlmlr/pkg.upgrade.test#L589-L593
[3] https://travis-ci.org/krlmlr/pkg.upgrade.test#L619-L645
[4] https://travis-ci.org/krlmlr/pkg.upgrade.test#L671-L703
2003 Aug 06
1
Reg. openssh-3.51p1/packet.c (function packet_send2())
...n2 = padding_length
byte[m] mac (message authentication code); m = mac_length
However, since i wanted to verify this, I put some debugging code in
openssh-3.51p1/packet.c (function packet_send2()), which can be accessed
at http://mia.ece.uic.edu/cgi-bin/lxr/http/source/packet.c?v=openssh-3.5p1#L619.
I conducted some tests by sending PPP packets and found out that the
tranport layer (i think) just appends an extra 14 bytes to the begining of
the PPP frame. The first 4 bytes of these are used to put in the
packet_length and the next 1 byte is used to put in the padding_length.
However the r...
2016 Dec 16
0
Upgrading a package to which other packages are LinkingTo
...y more."
Duncan Murdoch
>
> Thanks.
>
>
> Best regards
>
> Kirill
>
>
> [1] https://github.com/hadley/dplyr/issues/2308#issuecomment-267495075
> [2] https://travis-ci.org/krlmlr/pkg.upgrade.test#L589-L593
> [3] https://travis-ci.org/krlmlr/pkg.upgrade.test#L619-L645
> [4] https://travis-ci.org/krlmlr/pkg.upgrade.test#L671-L703
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>
2016 Dec 16
2
Upgrading a package to which other packages are LinkingTo
...och
|
| >
| > Thanks.
| >
| >
| > Best regards
| >
| > Kirill
| >
| >
| > [1] https://github.com/hadley/dplyr/issues/2308#issuecomment-267495075
| > [2] https://travis-ci.org/krlmlr/pkg.upgrade.test#L589-L593
| > [3] https://travis-ci.org/krlmlr/pkg.upgrade.test#L619-L645
| > [4] https://travis-ci.org/krlmlr/pkg.upgrade.test#L671-L703
| >
| > ______________________________________________
| > R-devel at r-project.org mailing list
| > https://stat.ethz.ch/mailman/listinfo/r-devel
| >
|
| ______________________________________________
| R-devel...
2019 Jun 05
2
llvm-ir: TBAA and struct copies
...struct path tbaa.
With the 'new struct path tbaa', as it also tracks the access size, I do see a possible solution:
in TypeBasedAliasAnalysis.cpp, in function bool mayBeAccessToSubobjectOf(...):
https://github.com/llvm/llvm-project/blob/master/llvm/lib/Analysis/TypeBasedAliasAnalysis.cpp#L619
if (BaseType.getNode() == SubobjectTag.getBaseType()) {
bool SameMemberAccess = OffsetInBase == SubobjectTag.getOffset(); // **** HERE
if (GenericTag) {
*GenericTag = SameMemberAccess ? SubobjectTag.getNode() :
createAccessTag(...
2019 Jun 04
2
llvm-ir: TBAA and struct copies
Hi,
I have a question about the current definition of TBAA (See [1]).
In the LLVM-IR code that we produce, we generate load/stores of struct types. (See [2] and [3] for a godbolt example showing the issue)
For following c-alike code:
struct S { int dummy; short e, f; } x,y;
struct S* p = &x;
int foobar() {
x.f=42;
*p=y; //**** struct copy
return x.f;
}
We produce: