Displaying 20 results from an estimated 321 matches for "subtlety".
2014 Oct 19
14
[LLVMdev] RFC: Are we ready to completely move away from the optionality of a DataLayout?
I've just wasted a day chasing my tail because of subtleties introduced to
handle the optionality of the DataLayout. I would like to never do this
again. =]
We now have this attached to the Module with just a flimsy faked-up pass to
keep APIs consistent. So, is there any problem with beginning down the path
of:
1) Synthesizing a "default" boring DataLayout for all modules that
2011 Jun 24
9
[PATCH] xen_disk: cope with missing xenstore "params" node
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
When disk is a cdrom and the drive is empty the "params" node in
xenstore might be missing completely: cope with it instead of
segfaulting.
Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
---
hw/xen_disk.c | 16 +++++++++++-----
1 files changed, 11 insertions(+), 5 deletions(-)
diff --git
2006 Mar 21
1
build R on windows
...the command just hung trying to load the library.
Here is the content of the description file,
Package: nws
Title: R functions for NetWorkSpaces and Sleigh
Version: 1.3.0
License: GPL Version 2 or later
Depends: R (>=2.1), methods
SaveImage: true
URL: http://nws-r.sourceforge.net
Is there any subtlety between building R packages in Linux and Windows?
I can build and load this package under Linux. But can't figure out
what's causing the hang on Windows and how to debug the problem. Has
anyone ran into similar problem before, and steps you took to debug the
problem?
I very much apprec...
2018 Oct 06
2
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
...tter or for worse, I'm trying to understand this code. So far,
> I've come up with this patch:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/commit/?h=x86/vdso-tglx&id=14fd71e12b1c4492a06f368f75041f263e6862bf
>
> Is it correct, or am I missing some subtlety?
The master clock, when initialized, has a pair
masterclockvalues=(TSC value, time-of-day data).
When updating the guest clock, we only update relative to (TSC value)
that was read on masterclock initialization.
See the following comment on x86.c:
/*
*
* Assuming a stable TSC across physical...
2018 Oct 06
2
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
...tter or for worse, I'm trying to understand this code. So far,
> I've come up with this patch:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/commit/?h=x86/vdso-tglx&id=14fd71e12b1c4492a06f368f75041f263e6862bf
>
> Is it correct, or am I missing some subtlety?
The master clock, when initialized, has a pair
masterclockvalues=(TSC value, time-of-day data).
When updating the guest clock, we only update relative to (TSC value)
that was read on masterclock initialization.
See the following comment on x86.c:
/*
*
* Assuming a stable TSC across physical...
2014 Mar 12
3
[LLVMdev] [ARM] [PIC] optimizing the loading of hidden global variable
Hi,
When Im compiling a code with fvisibility=hidden fPIC for ARM, I find
that LLVM generates less optimized code than GCC.
For example:
test.cpp:
void init(void *);
int g0[100];
int g1[100];
int g2[100];
void foo() {
init(&g0);
init(&g1);
init(&g2);
}
Clang will emit 1 GOT entry for each GV and 2 instructions to get the
address:
ldr
2016 Nov 29
2
RFC: Constructing StringRefs at compile time
...> >>
> >> #define LIT(x) x_string_ref_literal
> >> constexpr StringRef Strings[] = {LIT("a"), LIT("b"), LIT("c")};
> >
> > Why bother with the UDL?
> > #define LIT(x) StringRef((x), sizeof(x)-1)
> >
>
> There is subtlety though, it changes the result for: LIT(“hello\0world”).
>
> —
> Mehdi
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161129/5a923756/attachment.html>
2017 Jun 13
3
RFC: Dynamic dominators
On Mon, Jun 12, 2017 at 11:24 PM, Tobias Grosser via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hi Jakub,
>
> thanks for the update. I was already eagerly waiting to hear what your
> internship on dominance brings. I think the numbers are already very
> encouraging and I believe moving incrementally over to the new algorithm
> is exactly the right approach.
>
>
2009 Sep 09
4
usdt probes vs pid$target
I added a couple of static probes to Firefox to measure actual work
done. I could have used a pid$target probe with a function name but
work is done within an if statement, which is where I placed the
static probes.
I''m wondering about my use, though. Is the following significantly
more efficient than pid$target::FunName:entry and return?
I heard somewhere that $target does not
2014 Aug 20
2
[LLVMdev] llvm::Triple support for haswell-enabled x86_64
> On Aug 20, 2014, at 9:37 AM, Reid Kleckner <rnk at google.com> wrote:
>
> On Tue, Aug 19, 2014 at 10:37 PM, Chandler Carruth <chandlerc at google.com> wrote:
>
> On Tue, Aug 19, 2014 at 5:05 PM, Jim Grosbach <grosbach at apple.com> wrote:
> Note that it’s not exactly equivalent to enabling -march=core-avx2. It’s really close, but not 100% the same.
>
2015 Oct 20
2
[compiler-rt] Undefined negation in float emulation functions
...called with INT_MIN, though I don't immediately see anything to indicate this. Indeed there is a later
comment in this function that indicates INT_MIN is an anticipated input, but the negation has already occurred by this
point.
I am not a floating point expert, so perhaps I am missing some subtlety here. If so, apologies for the noise. The above
refers to r218935 and similar code is present in __floatsisf.
Thanks,
Matthew
2018 Oct 04
3
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
> On Oct 4, 2018, at 12:31 PM, Peter Zijlstra <peterz at infradead.org> wrote:
>
> On Thu, Oct 04, 2018 at 07:00:45AM -0700, Andy Lutomirski wrote:
>>> On Oct 4, 2018, at 1:11 AM, Peter Zijlstra <peterz at infradead.org> wrote:
>>>
>>>> On Thu, Oct 04, 2018 at 09:54:45AM +0200, Vitaly Kuznetsov wrote:
>>>> I was hoping to hear this
2018 Oct 04
3
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
> On Oct 4, 2018, at 12:31 PM, Peter Zijlstra <peterz at infradead.org> wrote:
>
> On Thu, Oct 04, 2018 at 07:00:45AM -0700, Andy Lutomirski wrote:
>>> On Oct 4, 2018, at 1:11 AM, Peter Zijlstra <peterz at infradead.org> wrote:
>>>
>>>> On Thu, Oct 04, 2018 at 09:54:45AM +0200, Vitaly Kuznetsov wrote:
>>>> I was hoping to hear this
2018 Oct 08
2
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
...this code. So far,
> > > I've come up with this patch:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/commit/?h=x86/vdso-tglx&id=14fd71e12b1c4492a06f368f75041f263e6862bf
> > >
> > > Is it correct, or am I missing some subtlety?
> >
> > The master clock, when initialized, has a pair
> >
> > masterclockvalues=(TSC value, time-of-day data).
> >
> > When updating the guest clock, we only update relative to (TSC value)
> > that was read on masterclock initialization.
>
> I don&...
2018 Oct 08
2
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
...this code. So far,
> > > I've come up with this patch:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/commit/?h=x86/vdso-tglx&id=14fd71e12b1c4492a06f368f75041f263e6862bf
> > >
> > > Is it correct, or am I missing some subtlety?
> >
> > The master clock, when initialized, has a pair
> >
> > masterclockvalues=(TSC value, time-of-day data).
> >
> > When updating the guest clock, we only update relative to (TSC value)
> > that was read on masterclock initialization.
>
> I don&...
2015 Aug 31
2
SMBx differences re Win10 in Samba4 NT4 DC
...ke authentication via other resources that no longer support
NT1, so am I correct in inferring that the only option at this point to get
Win10 domain logins with a later version of SMB (greater than NT1) is by
upgrading the domain to a full Samba AD DC?
Lastly, could someone help me understand the subtlety between the dialect of
SMB2/SMB3 Samba supports versus the variety Win10 is trying to negotiate,
and why there is the disconnect? Put a different way, I don't understand
exactly why Win10/Samba can't negotiate down to an SMB level both can use
(well, one greater than NT1, I guess)
--
Vi...
2014 Sep 05
2
[LLVMdev] '___ltsf2' could not be resolved - iOS/ARM cross compile
Hi there,
I’m building llvm for my iOS devices, and all seems to work well, until I try to execute the results:
LLVM ERROR: Program used external function '___ltsf2' which could not be resolved!
This appears to be part of compiler-rt which as far as I can see should be built / linked automatically when installed correctly? Am I missing something obvious?
Thanks,
.m
2017 Jan 11
2
16-bit bytes support
Hi.
I'm working on a backend for the
[DCPU16](https://github.com/techcompliant/TC-Specs/blob/master/CPU/DCPU.md),
a fictional CPU. The main subtlety is that the bytes are 16 bits instead
of 8. There is already a [working
backend](https://github.com/krasin/llvm-dcpu16), but it does a lot of
source modification to support 16 bit words. I try to update it to
latest llvm, but it obviously fails since the new code assumes 1 word ==
8 bits. Any...
2019 Jul 22
1
Re: [libnbd] More thoughts on callbacks and more
This has an annoying subtlety around the fact that we can pass a
single user_data and multiple closures in one function call.
The LIBNBD_CALLBACK_FREE function would be called several times with
the same user_data in this case, which means the callback must do some
kind of reference counting before the user_data can be freed....
2009 Jun 19
1
Fancy Ticks in Plots
Dear All,
I am pretty satisfied with R for my plotting, but there are a few
subtleties which I cannot figure out.
Consider figure 1 in the paper at the link below
http://cxnets.googlepages.com/univ_citations.pdf
Can I have the same kind of ticks in an R-generated figure (that is to
say: ticks along the 4 axis, and in a log-log plot I'd like a larger
tick for any power of 10).
I did a bit