similar to: [LLVMdev] LLVM Backwards-Compatability

Author: ahrens Repository: /hg/zfs-crypto/gate Revision: 0fdac67554fe0f4938120fb4f0cb35cbbcd38c0b Log message: 6389368 fat zap should use 16k blocks (with backwards compatability) Files: update: usr/src/uts/common/fs/zfs/dbuf.c update: usr/src/uts/common/fs/zfs/dmu_tx.c update: usr/src/uts/common/fs/zfs/dnode.c update: usr/src/uts/common/fs/zfs/sys/zap_impl.h update:

In doing my testing I''m wondering if maintaining backwards compatability for existing applications is important. The question boils down to this: Are there sufficient applications that are using wxRuby (pre swig) that we should expect to have to support all/most without changes or should we expect that most applications will need to learn the ''new'' ways things

Hello, running windows vista, R2.9. Installed the following libraries: (*latticist*, *playwith* and *Cairo*) Wanted then to run, to evaluate the visualization features: >data(iris) >library(latticist) >latticist(iris) However, i tested my desktop and laptop and get the following error after typing latticist(iris): latticist(iris) Loading required package: playwith Loading

The xlsReadWrite[Pro] packages allow to natively read/write Excel files (.xls) on the Win 32-bit platform. About a week ago new package versions have been released: * xlsReadWrite 1.5.3 is available at CRAN (for R2.11/2.12) and from www.swissr.org/download (binary builds for R2.9 - R2.12) * xlsReadWritePro 1.6.3 is available from www.swissr.org/download (binary builds for R2.9 - R2.12) * (the

Hi, I'm trying to generate some SPARCv8 assembly for a sparc target that doesn't have an FPU. I'm unable to get the flow to generate calls to a soft-float library. Since I wasn't able to find a definitive answer, I was hoping someone might be able to offer some pointers or shed some light. Running "clang -c -emit-llvm -msoft-float test.c -o test.bc" doesn't generate

Hello all, I saw on the Release notes that 2.6.0 is using protocol version 27 which is different than 2.5.7 and 2.5.6. I did a quick peak through the rest of the release notes and quickly browsed the archives on the list and I didn't see any notes on how well 2.6.0 works with older versions of rsync. At our site, we do have 2.5.7 and 2.5.6 installed. Are there any documented problems when

Hi, I’ve noted some change in wording on the current (4.0) developer policy[1], compared to the 3.9 developer policy[2]. Specifically the part about IR Backwards Compatibility. The change from 3.9 to 4.0 is the following: - The textual format is not backwards compatible. We don’t change it too often, but there are no specific promises. - Additions and changes to the IR should be reflected

Hi all, I've been developing a little project for the past few months on R2.9. The project utilises RServe to access R over at tcp/ip connection. One feature of the project is to take R-Help and display it to the user through my own UI. In 2.9 this worked well as all the html help was pre-generated - I could ask R to find the help (e.g. help(plot) would return the rd file), and then I could

Hello. Until today I've been using R2.9 and since today R2.10 (on a PC). In both of them it takes about 20 sec for the prompt to appear IN R console after I start R. And every time it says: "Previous saved work space restored" - even if I have not saved any workspace or, in case of R2.10 - even though I have not used it once. In the older versions - R would start within 2-3 sec. Is

Hi, I'm considering to use MC disassembler for ARM target in a binary translation project. However after trying some ARM binary and I find that there are a lot of instructions that the disassembler fails to to decoding. Could anyone give me some information about the maturity of ARM disassembler? Thanks! David -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Jun 5, 2012, at 7:44 PM, Fan Dawei <fandawei.s at gmail.com> wrote: > Hi, > > I'm considering to use MC disassembler for ARM target in a binary translation project. However after trying some ARM binary and I find that there are a lot of instructions that the disassembler fails to to decoding. > > Could anyone give me some information about the maturity of ARM

Full_Name: Neil Hepburn Version: 2.81 and 2.90 OS: OS-X 10.5.6 Submission from: (NULL) (142.244.28.93) When I create graphs using Rcmdr and then close the quartz display, R blows up and tells me of a segmentation fault. It then gives me *** caught segfault *** address 0xc0000023, cause 'memory not mapped' Possible actions: 1: abort (with core dump, if enabled) 2: normal R exit 3: exit

Hi all, a quick question I couldn't find the answer to in the usual places: Is there a way to turn off line-wrapping in the R console? Or set the line width-before-wrapping manually? Currently it looks like the console linewraps after about 70 characters, this occurs even if I increase the window size. (I want to output some simple tables to screen for students in a computer lab

Hi Evan, Thanks for the information! I've try to use llvm-objdump to disassemble some ARM binary, such as busybox in android. ./llvm-objdump -arch=arm -d busybox There are many instructions cannot decode, :./llvm-objdump: warning: invalid instruction encoding Did I use llvm-objdump in a correct way? I think that one possible reason is that llvm-objdump encounter pc relative data.

> On Oct 8, 2016, at 10:41 AM, Eric Christopher via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > > On Fri, Oct 7, 2016 at 11:57 PM Moritz Angermann via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > Hi, > > I’ve noted some change in wording on the current (4.0) developer policy[1], > compared to the 3.9

Hi, Two days ago, the test suite started failing. Initially there were hundreds of failing tests; now only seven remain. They appear to be related to SystemZ. Here's the last failed test: ******************** FAIL: LLVM :: MC/Disassembler/SystemZ/unmapped.txt (11484 of 14435) ******************** TEST 'LLVM :: MC/Disassembler/SystemZ/unmapped.txt' FAILED ******************** Script:

It is r195843 and fixed in r195905, FYI. 2013/11/29 Reed Kotler <rkotler at mips.com>: > I"m getting build errors I think from one of your patches O tjoml. > > You need to have a build area that builds with clang and does warnings as > errors to avoid these issues on putback. > > here is my configure step for example: > /home/rkotler/llvm_trunk/configure

I'm still seeing this problem. On 11/28/2013 09:37 AM, NAKAMURA Takumi wrote: > It is r195843 and fixed in r195905, FYI. > > 2013/11/29 Reed Kotler <rkotler at mips.com>: >> I"m getting build errors I think from one of your patches O tjoml. >> >> You need to have a build area that builds with clang and does warnings as >> errors to avoid these

I"m getting build errors I think from one of your patches O tjoml. You need to have a build area that builds with clang and does warnings as errors to avoid these issues on putback. here is my configure step for example: /home/rkotler/llvm_trunk/configure --enable-werror --prefix=/home/rkotler/ll vm/install CC=/home/rkotler/llvm_3_2/install/bin/clang CXX=/home/rkotler/llvm_3_

Hi there! In the x86 disassembler I noticed an if-statement with a duplicated branch. Are these intended to be identical? Best regards, Nicolas Kaiser -- diff -ur llvm-2.8.orig/lib/Target/X86/Disassembler/X86DisassemblerDecoder.c llvm-2.8/lib/Target/X86/Disassembler/X86DisassemblerDecoder.c --- llvm-2.8.orig/lib/Target/X86/Disassembler/X86DisassemblerDecoder.c 2010-05-06 22:59:00.000000000 +0200