search for: archaic

> I'm a bit confused by this concept. For the term byte, I use the "archaic" definition in the C (and C++) standard (section 3.6): addressable unit of data storage large enough to hold any member of the basic character set of the execution environment /Patrik Hägglund -----Original Message----- From: Jakob Stoklund Olesen [mailto:stoklund at 2pi.dk] Sent: den...

On Oct 19, 2012, at 2:24 AM, Patrik Hägglund H <patrik.h.hagglund at ericsson.com> wrote: >> non-8-bit byte I'm a bit confused by this concept. I'm aware of the archaic meaning of the word byte, but it has meant 8 bits for the last 30 years. There's even an ISO/IEC standard. I know of architectures like Texas' C55x DSPs that address 16 bits at a time, but even their data sheets state: • 256K Bytes Zero-Wait State On-Chip RAM, Composed of: • – 64K Byte...

...No matter what I change one of them two, the other two follow. I've tried moving the Digium card to the other PCI slot and the IRQ problem still exists. I talked to Dell technical support and they said "oh all our new machines share IRQs like that, the way you are trying to do it is archaic". What?!?! The Dell tech guy kept saying that I can define an IRQ in Linux, and I kept telling him that I need two unique (not virtual) IRQs.. one for the NIC and one for the Digium card. He said "yeah we've had other calls about Digium cards in these servers not working". AR...

On Oct 19, 2012, at 11:43 AM, Patrik Hägglund H <patrik.h.hagglund at ericsson.com> wrote: >> I'm a bit confused by this concept. > > For the term byte, I use the "archaic" definition in the C (and C++) standard (section 3.6): > > addressable unit of data storage large enough to hold any member of the basic character > set of the execution environment That definition isn't really relevant to LLVM, though. You can define char to be (say) 16 bits...

...a more concise reference for common Asterisk configurations and setups. I currently have a non-profit client to which I am donating work. They are looking to allow callers to listen in to public speaking sessions. They currently have a single phone line with call waiting and are using an archaic one-person switch to then allow folks to call- chain via 3-way calling. What they want is basically a "switchboard" that allows multiple people (5 to 10) to call in at a time of their choosing and begin listening to the "in-progress" session. My first question would be:...

On Fri, Oct 19, 2012 at 9:27 AM, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote: > > On Oct 19, 2012, at 2:24 AM, Patrik Hägglund H <patrik.h.hagglund at ericsson.com> wrote: > >>> non-8-bit byte > > I'm a bit confused by this concept. I'm aware of the archaic meaning of the word byte, but it has meant 8 bits for the last 30 years. There's even an ISO/IEC standard. > > I know of architectures like Texas' C55x DSPs that address 16 bits at a time, but even their data sheets state: > > • 256K Bytes Zero-Wait State On-Chip RAM, Composed o...

...I wanted to rewrite them in C, but a colleague keeps suggesting that I learn Fortran, so maybe this is the time to do it... I like to learn new languages and do it fairly quickly. I would appreciate the advice of others about these questions: 1) I hear bad things about Fortran. Sure, F77 looks archaic, but F90/95 seems nicer. Is it worth learning, especially when I plan to use it mainly from R? Dusting off my C knowledge would take a bit of time too, and I never liked C that much. 2) Does it interface well with R? Is F90/95 supported, or only F77? Thanks, Tamas

...aving resource constraint issues. Before it was fine to run any number of clients against samba, but now the ldap clients are limited. My server quickly ran out of memory! 1) Is there any solution exept adding more RAM? 2) One process should be able to handle more than 1 connection! This is an archaic server side model .... Actually the same issue also happens with the RPC Server which under certain conditions was started up to 50 000 times on 4.5 (not sure that is fixed). BR Thomas

....uiuc.edu/~vadve http://llvm.cs.uiuc.edu/ On Apr 13, 2007, at 9:49 AM, Reid Spencer wrote: > Thanks for the generous offer, but this is already happening at > UIUC. I > was just venting some frustration at the manual process of hacking > HTML > files and committing them (seems archaic for 21st century web site) > and > throwing a little fun Vikram's way. I just asked him for the wiki a > couple days ago :)

> Please start a thread on llvmdev about this functionality, and outline what other intrinsics will have to change to add non-8-bit byte support. Well, memset is the only we have seen so far (our back-end is ~50% finished for an initial release). We have our own front-end as well (we are currently not using the clang front-end), and currently don't use many llvm intrinsics (only

I am having some network connectivity issues that manifest itself through ping, wget, dnf, etc. The symptoms are intermittent ability to ping, was wget, or connect to repositories. Where this inquiry is going is: If your internal network is using 192.168.1 or 10..50.10, what should be in /etc/networks. My current file contains: default 0.0.0.0 loopback 127.0.0.0 link-local 169.254.0.0 And

Hi my 12 year old, WIX, is an amazing auto deductive computer whiz. I have to keep up... He is an excellent VB programmer and knows JAVA. I have been told ROR is the future. I want to guide WIX so he can build up a good methodical working knowledge but don''t want him to waste his time on archaic languages that will not be around soon...Should his next step be ROR or would you recommend something else? Thnx! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this g...

Hi Joe, thanks for working on this. My honest opinion on it is that time would be better spent improving the documentation, as the current documentation is archaic. I think this has come up on the list before, but to rehash: * Start out by saying "LLVM can be built with make or CMake, and checked out with svn or git", and have "make", "CMake", "svn", and "git" be links to their own section talking about the r...

...ng. I continue to think that 3.10 is the least defensible option out there. We have a time based release process with no mechanism or attempt to align behind “big” releases that could bring is to a 4.x number. You might as well call the release “10” at this point, since the "3.” will become archaic legacy that we can’t shed. Trust me, I’ve seen this happen several times in the past in multiple different products (both open source and proprietary), and have had success leading one to a more predictable release number pattern like I’m advocating for. This is a problem that we are simply walki...

...lock() to measure time, it would automatically ignore stolen time, and therefore only report when the guest itself locked up. When running native, sched_clock() returns real-time nanoseconds, so the behaviour would be unchanged. Does this seem sound? Also, softlockup.c's use of jiffies seems archaic now. Should it be converted to use timers? Mightn't it report lockups just because there was no timer event? Signed-off-by: Jeremy Fitzhardinge <jeremy@xensource.com> diff -r b41fb9e70d72 kernel/softlockup.c --- a/kernel/softlockup.c Thu Mar 22 16:25:15 2007 -0700 +++ b/kernel/softloc...

...lock() to measure time, it would automatically ignore stolen time, and therefore only report when the guest itself locked up. When running native, sched_clock() returns real-time nanoseconds, so the behaviour would be unchanged. Does this seem sound? Also, softlockup.c's use of jiffies seems archaic now. Should it be converted to use timers? Mightn't it report lockups just because there was no timer event? Signed-off-by: Jeremy Fitzhardinge <jeremy@xensource.com> diff -r b41fb9e70d72 kernel/softlockup.c --- a/kernel/softlockup.c Thu Mar 22 16:25:15 2007 -0700 +++ b/kernel/softloc...

...Peter predicted, syslinux.efi NBP boots the RHEL7 install media. (It's a new enough kernel). So -- if we ignore this problem long enough (syslinux.efi can't EFI PXE boot ancient kernels) -- the problem will go away. In the meantime, the grub2 bootx64.efi bootloader will EFI PXE boot these archaic kernels. I'm curious how grub2's bootx64.efi bootstraps these older kernels. Spike

> We're now keeping track of the naming process, ideas, etc. on this page: > > http://llvm.org/Name.html > > (would someone PLEASE get us a wiki!!!) ;) I can do a Media Wiki on our datacomms.net server for LLVM thats if :- a) You can not host one at UIUC b) Someone with prior Wiki experience cannot host one. Otherwise I would be willing to do the learning to host

...meone with prior Wiki experience cannot host one. > > Otherwise I would be willing to do the learning to host one. Thanks for the generous offer, but this is already happening at UIUC. I was just venting some frustration at the manual process of hacking HTML files and committing them (seems archaic for 21st century web site) and throwing a little fun Vikram's way. I just asked him for the wiki a couple days ago :) Reid. > > Aaron > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.ed...

...27 AM, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote: >> >> On Oct 19, 2012, at 2:24 AM, Patrik Hägglund H <patrik.h.hagglund at ericsson.com> wrote: >> >>>> non-8-bit byte >> >> I'm a bit confused by this concept. I'm aware of the archaic meaning of the word byte, but it has meant 8 bits for the last 30 years. There's even an ISO/IEC standard. >> >> I know of architectures like Texas' C55x DSPs that address 16 bits at a time, but even their data sheets state: >> >> • 256K Bytes Zero-Wait State On-Ch...