similar to: OT: Linus Torvalds delays Linux 3.0 launch due to a subtle bug (fwd)

http://www.theinquirer.net/?article=25529 what's everyone's thoughts on this one? -- My "Foundation" verse: Isa 54:17 No weapon that is formed against thee shall prosper; and every tongue that shall rise against thee in judgment thou shalt condemn. This is the heritage of the servants of the LORD, and their righteousness is of me, saith the LORD. -- carpe ductum --

Anyone on the asterisk list have any thoughts about the new Open Moko linux mobile? http://www.theinquirer.net/default.aspx?article=35590 http://www.linuxdevices.com/news/NS2986976174.html http://linux.slashdot.org/linux/06/11/08/004230.shtml Is there any integration into Asterisk that we can look at? Anyone want to through some application ideas they'd like to see developed

Not too sure what to think about this, considering M$'s track record with OSS and other competitors. Kind Regards, Keith Roberts ---------- Forwarded message ---------- To: opensuse-offtopic <opensuse-offtopic at opensuse.org> From: Basil Chupin <blchupin at iinet.net.au> Subject: [opensuse-offtopic] Microsoft struggles to get Hyper-V drivers in Linux kernel The

After reading the following articles, it doesn''t sound very hopeful for Xen. [1] Xen vs. KVM: Verdict still out on dueling hypervisors http://searchdatacenter.techtarget.com/news/article/0,289142,sid80_gci1368664,00.html [2] Xen vs. KVM Linux virtualization hypervisors http://searchservervirtualization.techtarget.com/generic/0,295582,sid94_gci1371226,00.html [3] Xen vs. KVM: The Linux

After reading the following articles, it doesn''t sound very hopeful for Xen. [1] Xen vs. KVM: Verdict still out on dueling hypervisors http://searchdatacenter.techtarget.com/news/article/0,289142,sid80_gci1368664,00.html [2] Xen vs. KVM Linux virtualization hypervisors http://searchservervirtualization.techtarget.com/generic/0,295582,sid94_gci1371226,00.html [3] Xen vs. KVM: The Linux

The title is "Microsoft cerebrates fifteen years of poor security". But it's about more than Microsoft's security. It talks about buffer overflows, memory separation, OpenBSD's data "canary", etc. I think it's a good read for anyone interested on this kind of stuff. http://www.theinquirer.net/?article=11108 Santos

On Tue, 27 Apr 2004, Vladimir Prus wrote: > > Yeah, fishy huh? :) > > Yea, a bit. I've decided that before changing that I'd better find other > problems, if any, so I run inst_iterator via checks provided by > Boost.Iterators. > > First problem is that inst_iterator (and actually InstIterator class template) > is not Assignable, because it has a reference data

I updated my from LLVM 2.7 to 2.8/trunk tonight and was mystified as to why my GC plugin silently stopped working. The problem was that the signature of the virtual function GCMetadataPrinter::finishAssembly (and beginAssembly) changed. This change would probably be an excellent candidate for the "gotchas" section of the 2.8 release notes. Thanks! -- Ben -------------- next part

Hi Ben, > I updated my from LLVM 2.7 to 2.8/trunk tonight and was mystified as to why my > GC plugin silently stopped working. > > The problem was that the signature of the virtual function > GCMetadataPrinter::finishAssembly (and beginAssembly) changed. > > This change would probably be an excellent candidate for the "gotchas" section > of the 2.8 release notes.

Hi guys, In porting our project over to LLVM-2.8 today I ran into a change that should probably go in the 2.8 release notes. After r100485, the MemoryBuffer::getMemBuffer went from: /// getMemBuffer - Open the specified memory range as a MemoryBuffer. Note /// that EndPtr[0] must be a null byte and be accessible!

On Mon, Sep 13, 2010 at 5:17 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi Ben, > > > I updated my from LLVM 2.7 to 2.8/trunk tonight and was mystified as to > why my > > GC plugin silently stopped working. > > > > The problem was that the signature of the virtual function > > GCMetadataPrinter::finishAssembly (and beginAssembly) changed. >

On 05/17/2013 08:08 PM, Rafael Espíndola wrote: > My understanding is that with the new attribute system we should > deprecate and eventually remove the codegen command line options. How is that possible? > On 17 May 2013 06:04, reed kotler <rkotler at mips.com> wrote: >> I can't say this is a bug it is changed behavior from before the new >> attribute scheme.

I have been running the 20010112 version of wine with "Agent" in order to read all my mail and news. This seemed to work fine. In order to try and get a game (Grand Prix Legends) to work I have installed the Transgaming patch, which including patching wine to the 29th Jan version. Since that time, some subtle changes seems to have occurred. These are a) Previously wine had been

My understanding is that with the new attribute system we should deprecate and eventually remove the codegen command line options. On 17 May 2013 06:04, reed kotler <rkotler at mips.com> wrote: > I can't say this is a bug it is changed behavior from before the new > attribute scheme. > > This issue may appear with other attributes. (there are other attributes > that clang

On Fri, 23 Apr 2004, Vladimir Prus wrote: > and since result of *it is considered to be rvalue it can't be accepted by > this operator. The complete discussion is in > > http://std.dkuug.dk/jtc1/sc22/wg21/docs/papers/2002/n1385.htm > > I'd suggest to apply the following patch which makes operator* return > reference to pointer. It makes my code compile and the rest

Hello, I've been wondering why my no-optimization R-devel builds have been hanging during "building/updating package indices ...". I tracked it down with gdb to this line from do_basename in utils.c: while ( *(p = buf + strlen(buf) - 1) == fsp ) *p = '\0'; Now, imagine if your compiler places the variable fsp immediately before buf on the stack, and strlen(buf) is 0.

On Tue, Jan 17, 2017 at 04:20:49PM +0000, Rolf Neugebauer wrote: > Commits: > > fd2a0437dc33 virtio_net: introduce virtio_net_hdr_{from,to}_skb > e858fae2b0b8 virtio_net: use common code for virtio_net_hdr and skb > GSO conversion > > introduced a subtle (but unexplained) difference in how virtio_net > flags are derived from skb->ip_summed fields on transmit from the

Hello: Is there any documentation dealing with the functional differences between R 1.1 and R 1.2. I have noticed some strange behavior in what is, I guess, the namespace of libraries as well as some changes in reading in tables. In a library, I don't seem to be able to declare a global variable and then use it in that same library. e.g. > blah <<- 0 > print(blah) will

Chris Lattner wrote: > > inline IIty operator*() const { return BI; } > > inline IIty operator->() const { return operator*(); } > > > > So operator* works as if value_type is Instruction*, but operator-> works > > as if value_type is Instruction. Hmm ;-) > > Yeah, fishy huh? :) Yea, a bit. I've decided that before changing that I'd better

On Fri, 23 Apr 2004, Vladimir Prus wrote: > Yea, I've noticed that. However, it looks like inst_iterator is iterator over > pointers. Oh, wait a minite, that's the current code: > > inline IIty operator*() const { return BI; } > inline IIty operator->() const { return operator*(); } > > So operator* works as if value_type is Instruction*, but operator->