search for: r165739

...code, Android NDK, Chromium, and Linux build process. The problem we face is that bitcode changes, and when it does… future versions can read it, but past versions are left in the lurch. For instance LLVM 3.2svn can BitcodeReader from LLVM 3.1, but LLVM 3.1 can't BitcodeReader LLVM 3.2 (after r165739.) There was an element of this patch which would have helped enable bitcode compatibility (use-abs-operands), but alas it was not committed. This patch is essentially those missing lines, but with a new purpose of providing a vehicle for bitcode compatibility. With this patch, I aim to enable c...

...process. >> >> The problem we face is that bitcode changes, and when it does… future versions >> can read it, but past versions are left in the lurch. For instance LLVM 3.2svn >> can BitcodeReader from LLVM 3.1, but LLVM 3.1 can't BitcodeReader LLVM 3.2 >> (after r165739.) There was an element of this patch which would have helped >> enable bitcode compatibility (use-abs-operands), but alas it was not committed. > > can't you use a combination of llvm-dis (from LLVM 3.2) and llvm-as (from LLVM > 3.1) to convert the bitcode? > > Ciao, Du...

...ium, and Linux build process. > > The problem we face is that bitcode changes, and when it does… future versions > can read it, but past versions are left in the lurch. For instance LLVM 3.2svn > can BitcodeReader from LLVM 3.1, but LLVM 3.1 can't BitcodeReader LLVM 3.2 > (after r165739.) There was an element of this patch which would have helped > enable bitcode compatibility (use-abs-operands), but alas it was not committed. can't you use a combination of llvm-dis (from LLVM 3.2) and llvm-as (from LLVM 3.1) to convert the bitcode? Ciao, Duncan. > > This patch i...

...e: >>> The problem we face is that bitcode changes, and when it does… future versions >>> can read it, but past versions are left in the lurch. For instance LLVM 3.2svn >>> can BitcodeReader from LLVM 3.1, but LLVM 3.1 can't BitcodeReader LLVM 3.2 >>> (after r165739.) There was an element of this patch which would have helped >>> enable bitcode compatibility (use-abs-operands), but alas it was not committed. >> >> can't you use a combination of llvm-dis (from LLVM 3.2) and llvm-as (from LLVM >> 3.1) to convert the bitcode? &gt...

...gt; The problem we face is that bitcode changes, and when it does… future versions >>>> can read it, but past versions are left in the lurch. For instance LLVM 3.2svn >>>> can BitcodeReader from LLVM 3.1, but LLVM 3.1 can't BitcodeReader LLVM 3.2 >>>> (after r165739.) There was an element of this patch which would have helped >>>> enable bitcode compatibility (use-abs-operands), but alas it was not committed. >>> >>> can't you use a combination of llvm-dis (from LLVM 3.2) and llvm-as (from LLVM >>> 3.1) to convert...