search for: indivisibilities

Hi all, Saw on the net the wip5000 SIP wireless phone from Hitachi, a suprising rig. As anyone successfull in making it work with Asterisk? If so, how do you like it? Regards, Francois Random Thought: --------------- Molecule, n.: The ultimate, indivisible unit of matter. It is distinguished from the corpuscle, also the ultimate, indivisible unit of matter, by a closer resemblance to

On Fri, May 29, 2015 at 1:14 AM, Rui Ueyama <ruiu at google.com> wrote: > I want to make it clear that I didn't (at least intend to) compromise > flexibility or beauty of design with short-term performance gain. I was > trying to do simple things in a simple way for both humans and computers, > and I believe I did that fairly well. I'd even argue that the new design

I want to make it clear that I didn't (at least intend to) compromise flexibility or beauty of design with short-term performance gain. I was trying to do simple things in a simple way for both humans and computers, and I believe I did that fairly well. I'd even argue that the new design is cleaner and more expressive than before, because the "atom" model is in some part too

On Fri, May 29, 2015 at 6:01 PM, Sean Silva <chisophugis at gmail.com> wrote: > > > On Fri, May 29, 2015 at 1:14 AM, Rui Ueyama <ruiu at google.com> wrote: > >> I want to make it clear that I didn't (at least intend to) compromise >> flexibility or beauty of design with short-term performance gain. I was >> trying to do simple things in a simple way

On Fri, May 29, 2015 at 7:08 PM, Rui Ueyama <ruiu at google.com> wrote: > On Fri, May 29, 2015 at 6:01 PM, Sean Silva <chisophugis at gmail.com> wrote: > >> >> >> On Fri, May 29, 2015 at 1:14 AM, Rui Ueyama <ruiu at google.com> wrote: >> >>> I want to make it clear that I didn't (at least intend to) compromise >>> flexibility

On Jul 30, 2013, at 4:28 PM, Eric Christopher wrote: > On Mon, Jul 29, 2013 at 9:24 AM, Nick Kledzik <kledzik at apple.com> wrote: >> >> On Jul 25, 2013, at 2:10 PM, Rui Ueyama wrote: >>> Is there any reason -ffunction-sections and -fdata-sections wouldn't work? If it'll work, it may be be better to say "if you want to get a better linker output use

> > > One of the standard reasons to prefer refactoring, even though it appears > to take longer or be more difficult, is that it allows you to always keep > all tests green. It is very easy for things to slip through the cracks and > not promptly return to being green on a "from-scratch" version. This > ultimately turns into bug reports later and the feature needs

On Tue, Jul 30, 2013 at 5:36 PM, Nick Kledzik <kledzik at apple.com> wrote: > > On Jul 30, 2013, at 4:28 PM, Eric Christopher wrote: >> On Mon, Jul 29, 2013 at 9:24 AM, Nick Kledzik <kledzik at apple.com> wrote: >>> >>> On Jul 25, 2013, at 2:10 PM, Rui Ueyama wrote: >>>> Is there any reason -ffunction-sections and -fdata-sections wouldn't

On Nov 1, 2011, at 6:26 PM, Michael Spencer wrote: > A major feature of the linker design I have been working on is the > object file IR it is based on. It takes the concept of an atom (a > named range of data) and formalizes it into a graph based data > structure where edges represent the relations between atoms such as > relocations, groupings, and layout constraints. This

On 7/30/2013 7:50 PM, Eric Christopher wrote: > On Tue, Jul 30, 2013 at 5:36 PM, Nick Kledzik <kledzik at apple.com> wrote: >> On Jul 30, 2013, at 4:28 PM, Eric Christopher wrote: >>> On Mon, Jul 29, 2013 at 9:24 AM, Nick Kledzik <kledzik at apple.com> wrote: >>>> On Jul 25, 2013, at 2:10 PM, Rui Ueyama wrote: >>>>> Is there any reason

Hi, I have kept working on this and found the following (as llvm 3.5): 1) In the function MCObjectStreamer::EmitInstruction there is a check for the instruction being relaxable or not: if (!Assembler.getBackend().mayNeedRelaxation(Inst)) { EmitInstToData(Inst, STI); return; } At this stage, the instruction as been already selected to be ARM::ADR. The call to mayNeed 2015-07-07 18:06

I have created a small ll file to reproduce the problem. I used the intrinsic function llvm.arm.space to introduce space between the beginning of the code and the jump table. If the first argument of llvm.arm.space is higher than INT_MAX ( *2147483647)*, then the bug is hit. Lower or equal to that value, it passes. It looks like a precision issue. Does this sound familiar to someone? ; ModuleID =

> And now we're against the Atom model? I'm quite new to the llvm community, and basically unfamiliar with LLD, so maybe I'm simply uninformed. If so, I will now proceed to demonstrate that to an entire list of people. :) I've read the doc on http://lld.llvm.org/design.html, but the list of features it says that you get with LLD/Atoms and don't get with the "old

I think I get it now, thanks for explaining! >> On Jan 12, 2020, at 11:44 AM, David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: >  > > >> On Fri, Jan 10, 2020 at 12:57 PM Vedant Kumar <vedant_kumar at apple.com> wrote: >> I don't totally follow the proposed encoding change & would appreciate a small example. >> >> Is the

On Thu, May 28, 2015 at 6:25 PM, Nick Kledzik <kledzik at apple.com> wrote: > > On May 28, 2015, at 5:42 PM, Sean Silva <chisophugis at gmail.com> wrote: > > I guess, looking back at Nick's comment: > > "The atom model is a good fit for the llvm compiler model for all > architectures. There is a one-to-one mapping between llvm::GlobalObject > (e.g.

On Mon, Jul 29, 2013 at 9:24 AM, Nick Kledzik <kledzik at apple.com> wrote: > > On Jul 25, 2013, at 2:10 PM, Rui Ueyama wrote: >> Is there any reason -ffunction-sections and -fdata-sections wouldn't work? If it'll work, it may be be better to say "if you want to get a better linker output use these options", rather than defining new ELF section. > > From

If you try hist(rnorm(100),lwd=2) with a recent snapshot, you get the exact opposite effect of what was earlier argued to be desirable in plots: you get fat axes and thin bar outlines. The cause is plain to see, at the end of 'hist': title(main = main, xlab = xlab, ylab = ylab, ...) if (axes) { axis(1, ...) axis(2, ...) }

Do the Digium cards have a built in CSU? Is a CSU an FCC requirement? or just a carrier requirement? TIA

I stupidly decided to save my last workspace (a large dataset) and every time I open R it loads it back in. Can I stop this? Also how do you clear variables. Thanks, Sachin --- Please consider the environment before printing this email --- Allianz - General Insurance Company of the Year 2009+ + Australia and New Zealand Insurance Industry Awards This email and any attachments has been sent by

On May 28, 2015, at 5:42 PM, Sean Silva <chisophugis at gmail.com> wrote: > I guess, looking back at Nick's comment: > > "The atom model is a good fit for the llvm compiler model for all architectures. There is a one-to-one mapping between llvm::GlobalObject (e.g. function or global variable) and lld:DefinedAtom." > > it seems that the primary issue on the