search for: outputbuff

For the reasons listed in my 03-May-2012 email, I am proposing a new llvm/Support class for using in writing binary files: /// OutputBuffer - This interface provides simple way to create an in-memory /// buffer which when done will be written to a file. During the lifetime of /// these objects, the content or existence of the specified file is undefined. /// That is, creating an OutputBuffer for a file may immediately remove the...

...1.765.889.4756 gkeiser at arxan.com www.arxan.com<http://www.arxan.com/> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Nick Kledzik Sent: Monday, May 07, 2012 3:57 PM To: LLVM Developers Mailing List Subject: [LLVMdev] [RFC] llvm/include/Support/OutputBuffer.h For the reasons listed in my 03-May-2012 email, I am proposing a new llvm/Support class for using in writing binary files: /// OutputBuffer - This interface provides simple way to create an in-memory /// buffer which when done will be written to a file. During the lifetime of /// these objec...

...e sense to implement on top of Windows APIs? -Nick > > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Nick Kledzik > Sent: Monday, May 07, 2012 3:57 PM > To: LLVM Developers Mailing List > Subject: [LLVMdev] [RFC] llvm/include/Support/OutputBuffer.h > > For the reasons listed in my 03-May-2012 email, I am proposing a new llvm/Support class for using in writing binary files: > > /// OutputBuffer - This interface provides simple way to create an in-memory > /// buffer which when done will be written to a file. During the l...

On Mon, May 7, 2012 at 12:56 PM, Nick Kledzik <kledzik at apple.com> wrote: > For the reasons listed in my 03-May-2012 email, I am proposing a new > llvm/Support class for using in writing binary files: > > /// OutputBuffer - This interface provides simple way to create an in-memory > /// buffer which when done will be written to a file. During the lifetime > of > /// these  objects, the content or existence of the specified file is > undefined. > /// That is, creating an OutputBuffer for a file may i...

...May 8, 2012, at 3:41 PM, Michael Spencer wrote: > On Mon, May 7, 2012 at 12:56 PM, Nick Kledzik <kledzik at apple.com> wrote: >> For the reasons listed in my 03-May-2012 email, I am proposing a new >> llvm/Support class for using in writing binary files: >> >> /// OutputBuffer - This interface provides simple way to create an in-memory >> /// buffer which when done will be written to a file. During the lifetime >> of >> /// these objects, the content or existence of the specified file is >> undefined. >> /// That is, creating an OutputBuf...

...Michael Spencer wrote: > >> On Mon, May 7, 2012 at 12:56 PM, Nick Kledzik <kledzik at apple.com> wrote: >>> For the reasons listed in my 03-May-2012 email, I am proposing a new >>> llvm/Support class for using in writing binary files: >>> >>> /// OutputBuffer - This interface provides simple way to create an in-memory >>> /// buffer which when done will be written to a file. During the lifetime >>> of >>> /// these objects, the content or existence of the specified file is >>> undefined. >>> /// That is, c...

On May 3, 2012, at 6:10 PM, Nick Kledzik wrote: > Existing llvm code tends to use raw_ostream for writing files. But raw_ostream is not a good match for a linker for a couple of reasons: > > 1) When the linker creates an executable, the file needs the 'x' bit set. Currently raw_fd_ostream has no way to set that. If this were the only problem, I'd suggest just generalizing

Existing llvm code tends to use raw_ostream for writing files. But raw_ostream is not a good match for a linker for a couple of reasons: 1) When the linker creates an executable, the file needs the 'x' bit set. Currently raw_fd_ostream has no way to set that. 2) The Unix conformance suite actually has some test cases where the linker is run and the output file does exists but is not

Any idea what might be wrong? ActionView::Template::Error (undefined method `+@'' for #<ActionView::OutputBuffer:0x00000002e51580>): -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsub...

...quot;Thin", "tmp.o", TempFD, TempFilename); if (EC) { errs() << "Error: " << EC.message() << "\n"; report_fatal_error("ThinLTO: Can't get a temporary file"); } { raw_fd_ostream OS(TempFD, /* ShouldClose */ true); OS << OutputBuffer.getBuffer(); } // Rename to final destination (hopefully race condition won't matter here) EC = sys::fs::rename(TempFilename, EntryPath); Compared to a race-prone direct write of a buffer to a file, this code avoids a data race by first writing a buffer to a temp file and then renaming that...

...t; > * errs() << "Error: " << EC.message() << "\n";* > > * report_fatal_error("ThinLTO: Can't get a temporary file");* > > *}* > > *{* > > * raw_fd_ostream OS(TempFD, /* ShouldClose */ true);* > > * OS << OutputBuffer.getBuffer();* > > *}* > > *// Rename to final destination (hopefully race condition won't matter > here)* > > *EC = sys::fs::rename(TempFilename, EntryPath); * > > > > Compared to a race-prone direct write of a buffer to a file, this code > avoids a data...

...nd its crystal clear. Where am I going wrong here? Anyone got any suggestions? My code is as follows #define AUDIO_QUALITY 10 #define FRAME_SIZE 160 #define COMP_FRAME_SIZE 62 char *encodeSpeexWithBuffer(spx_int16_t *buffer, int *insize) { SpeexBits bits; void *enc_state; char *outputBuffer = (char *)malloc(COMP_FRAME_SIZE); speex_bits_init(&bits); enc_state = speex_encoder_init(&speex_nb_mode); int quality = AUDIO_QUALITY; speex_encoder_ctl(enc_state, SPEEX_SET_QUALITY, &quality); speex_bits_reset(&bits);...

Hi, I''m working to patch actionpack/lib/action_view/helpers/ cache_helper.rb so that it doesn''t throw when ouput_buffer isn''t ActionView::OutputBuffer but is still html_safe. In 3-0-stable the function contains the following if: if output_buffer.is_a?(ActionView::OutputBuffer) safe_output_buffer = output_buffer.to_str fragment = safe_output_buffer.slice!(pos..-1) self.output_buffer = ActionView::Ou...

...quot;Thin", "tmp.o", TempFD, TempFilename); if (EC) { errs() << "Error: " << EC.message() << "\n"; report_fatal_error("ThinLTO: Can't get a temporary file"); } { raw_fd_ostream OS(TempFD, /* ShouldClose */ true); OS << OutputBuffer.getBuffer(); } // Rename to final destination (hopefully race condition won't matter here) EC = sys::fs::rename(TempFilename, EntryPath); Compared to a race-prone direct write of a buffer to a file, this code avoids a data race by first writing a buffer to a temp file and then renaming that...

...TempFD, TempFilename); > if (EC) { > errs() << "Error: " << EC.message() << "\n"; > report_fatal_error("ThinLTO: Can't get a temporary file"); > } > { > raw_fd_ostream OS(TempFD, /* ShouldClose */ true); > OS << OutputBuffer.getBuffer(); > } > // Rename to final destination (hopefully race condition won't matter here) > EC = sys::fs::rename(TempFilename, EntryPath); > > Compared to a race-prone direct write of a buffer to a file, this code avoids a data race by first writing a buffer to a tem...

...t; > * errs() << "Error: " << EC.message() << "\n";* > > * report_fatal_error("ThinLTO: Can't get a temporary file");* > > *}* > > *{* > > * raw_fd_ostream OS(TempFD, /* ShouldClose */ true);* > > * OS << OutputBuffer.getBuffer();* > > *}* > > *// Rename to final destination (hopefully race condition won't matter > here)* > > *EC = sys::fs::rename(TempFilename, EntryPath); * > > > > Compared to a race-prone direct write of a buffer to a file, this code > avoids a data...

...quot;Thin", "tmp.o", TempFD, TempFilename); if (EC) { errs() << "Error: " << EC.message() << "\n"; report_fatal_error("ThinLTO: Can't get a temporary file"); } { raw_fd_ostream OS(TempFD, /* ShouldClose */ true); OS << OutputBuffer.getBuffer(); } // Rename to final destination (hopefully race condition won't matter here) EC = sys::fs::rename(TempFilename, EntryPath); Compared to a race-prone direct write of a buffer to a file, this code avoids a data race by first writing a buffer to a temp file and then renaming that...

...;); } catch (...) { fprintf(stderr, "An unknown error occurred\n"); } } my speex encode & decode function : #define FRAME_SIZE 160 #define COMP_FRAME_SIZE 62 char* encodeSpeex(spx_int16_t *buffer, UInt32 inSize, int *encodedSize) { char *outputBuffer = (char *)malloc(COMP_FRAME_SIZE); speex_bits_reset(&bits_in); speex_encode_int(enc_state, buffer, &bits_in); *encodedSize = speex_bits_write(&bits_in, outputBuffer, FRAME_SIZE * 2); return outputBuffer; } short* decodeSpeex(char* buff...

...TempFD, TempFilename); > if (EC) { > errs() << "Error: " << EC.message() << "\n"; > report_fatal_error("ThinLTO: Can't get a temporary file"); > } > { > raw_fd_ostream OS(TempFD, /* ShouldClose */ true); > OS << OutputBuffer.getBuffer(); > } > // Rename to final destination (hopefully race condition won't matter here) > EC = sys::fs::rename(TempFilename, EntryPath); > > Compared to a race-prone direct write of a buffer to a file, this code avoids a data race by first writing a buffer to a tem...

...owever, I feel this is the only place where I can get some help with my problem. BOOL CALLBACK RecordProc(HRECORD hRecord, void *buffer, DWORD length, DWORD user) { try { long sent = 0; long inputOffset = 0; long outputOffset = 0; long nbBytes = 0; char *outputBuffer = NULL; outputBuffer = (char*)malloc(65535); memset(speexBuffer, 0, 65536); while (inputOffset < length) { (float*)buffer = (float*)buffer + (frameSize); speex_bits_reset(&bits); speex_encode(enc_state, (float*)buffer, &bits...