[llvm-commits] CVS: llvm/lib/Support/MemoryBuffer.cpp

2007-05-10 Thread Chris Lattner
Changes in directory llvm/lib/Support: MemoryBuffer.cpp updated: 1.6 -> 1.7 --- Log message: fix a memory leak --- Diffs of the changes: (+1 -1) MemoryBuffer.cpp |2 +- 1 files changed, 1 insertion(+), 1 deletion(-) Index: llvm/lib/Support/MemoryBuffer.cpp diff -u llvm/lib/Support/Me

[llvm-commits] CVS: llvm/lib/Support/MemoryBuffer.cpp

2007-05-07 Thread Jeff Cohen
Changes in directory llvm/lib/Support: MemoryBuffer.cpp updated: 1.5 -> 1.6 --- Log message: Unbreak VC++ build. --- Diffs of the changes: (+2 -0) MemoryBuffer.cpp |2 ++ 1 files changed, 2 insertions(+) Index: llvm/lib/Support/MemoryBuffer.cpp diff -u llvm/lib/Support/MemoryBuffer.cp

[llvm-commits] CVS: llvm/lib/Support/MemoryBuffer.cpp

2007-05-06 Thread Chris Lattner
Changes in directory llvm/lib/Support: MemoryBuffer.cpp updated: 1.4 -> 1.5 --- Log message: Enhance MemoryBuffer to return error messages in strings if they occur. --- Diffs of the changes: (+11 -7) MemoryBuffer.cpp | 18 +++--- 1 files changed, 11 insertions(+), 7 deletions

Re: [llvm-commits] CVS: llvm/lib/Support/MemoryBuffer.cpp

2007-05-06 Thread Chris Lattner
On May 6, 2007, at 12:50 AM, Reid Spencer wrote: > On Sun, 2007-05-06 at 00:43 -0700, Chris Lattner wrote: + MemoryBufferMMapFile() {} + + bool open(const sys::Path &Filename); >>> >>> Shouldn't this have a parameter to receive the error message ? >> >> No, because membuffer does

Re: [llvm-commits] CVS: llvm/lib/Support/MemoryBuffer.cpp

2007-05-06 Thread Reid Spencer
On Sun, 2007-05-06 at 00:43 -0700, Chris Lattner wrote: > >> + MemoryBufferMMapFile() {} > >> + > >> + bool open(const sys::Path &Filename); > > > > Shouldn't this have a parameter to receive the error message ? > > No, because membuffer doesn't know why the open failed. It would > always ret

Re: [llvm-commits] CVS: llvm/lib/Support/MemoryBuffer.cpp

2007-05-06 Thread Chris Lattner
>> + MemoryBufferMMapFile() {} >> + >> + bool open(const sys::Path &Filename); > > Shouldn't this have a parameter to receive the error message ? No, because membuffer doesn't know why the open failed. It would always return the same thing. -Chris

Re: [llvm-commits] CVS: llvm/lib/Support/MemoryBuffer.cpp

2007-05-06 Thread Reid Spencer
On Sun, 2007-05-06 at 02:25 -0500, Chris Lattner wrote: > > Changes in directory llvm/lib/Support: > > MemoryBuffer.cpp updated: 1.3 -> 1.4 > --- > Log message: > > Fix MemoryBuffer::getFile to return null if it has an error opening the > file instead of aborting. > > > --- > Diffs of the chan

[llvm-commits] CVS: llvm/lib/Support/MemoryBuffer.cpp

2007-05-06 Thread Chris Lattner
Changes in directory llvm/lib/Support: MemoryBuffer.cpp updated: 1.3 -> 1.4 --- Log message: Fix MemoryBuffer::getFile to return null if it has an error opening the file instead of aborting. --- Diffs of the changes: (+20 -8) MemoryBuffer.cpp | 28 1 files ch

[llvm-commits] CVS: llvm/lib/Support/MemoryBuffer.cpp

2007-04-29 Thread Jeff Cohen
Changes in directory llvm/lib/Support: MemoryBuffer.cpp updated: 1.2 -> 1.3 --- Log message: Fix MemoryBuffer breakage correctly. --- Diffs of the changes: (+1 -1) MemoryBuffer.cpp |2 +- 1 files changed, 1 insertion(+), 1 deletion(-) Index: llvm/lib/Support/MemoryBuffer.cpp diff -u l

[llvm-commits] CVS: llvm/lib/Support/MemoryBuffer.cpp

2007-04-29 Thread Jeff Cohen
Changes in directory llvm/lib/Support: MemoryBuffer.cpp updated: 1.1 -> 1.2 --- Log message: Unbreak build. --- Diffs of the changes: (+2 -1) MemoryBuffer.cpp |3 ++- 1 files changed, 2 insertions(+), 1 deletion(-) Index: llvm/lib/Support/MemoryBuffer.cpp diff -u llvm/lib/Support/Memo

[llvm-commits] CVS: llvm/lib/Support/MemoryBuffer.cpp

2007-04-28 Thread Chris Lattner
Changes in directory llvm/lib/Support: MemoryBuffer.cpp added (r1.1) --- Log message: Add a new memorybuffer class, to unify all the file reading code in the system --- Diffs of the changes: (+239 -0) MemoryBuffer.cpp | 239 +++ 1 files