search for: file_reader

I was able to run through all the C/C++ benchmarks in SPEC using LLVM. I'm on OS X 10.3.3. I did a quick comparison between LLVM (latest from CVS as of 4/27) and gcc 3.3 (Apple's build 20030304). For simplicity's sake, the only flag I used was -O3 for each compiler and I was using the C backend to generate native code for PPC. Most of the LLVM results were close to gcc

On Sun, 2 May 2004, Patrick Flanagan wrote: > Is there anything special flagwise that I would need to specify to tell > it to include symbol and debug information? I've tried specifying -g > but this information still doesn't seem to be included. A quick copy of > the build of one of the tests to make sure I've got the flags right: Nope. Right now LLVM doesn't have

Dear Jan My intention is to read a piece at time of an .ogg file (stored in and external Multimedia card) decompress it and render it on and LPC2000 DAC. Because I don't have enough RAM memory to load the complete ogg file, I must read only a piece of file at certain time, then decompress and render it, and repeat the previous process until the end of the file. The problem is that I don't

Dear Ralph Thank you for your info. My file_read() function only get a specified number (nbBytes) of bytes from the .ogg file and store it in cbits, nothing else lb = file_read(&file, nbBytes, (void *)cbits); Unfortunately I have only 32K (first section) + 8 (second section) = 40 Kbyte of RAM to do all, including the file system management (I get the FS from the EFSL project). Speex

Dear All I ported the speex decoder in LPC2000 ARM7 family. Because I fetched the .ogg file from and external MMC card, I can only red a limited memory block 1) Can I decode only a block of a speex file at time ? /*Create a new decoder state in narrowband mode*/ state = speex_decoder_init(&speex_nb_mode); /*Set the perceptual enhancement on*/ tmp=1;

> >> Just to make sure I understand how LLVM works, got a few >> clarifications: >> >> 1. The ppc code I'm generating with the -native-cbe is static, >> correct? > > Yes, it's purely static with the -native-cbe or -native options. Is there anything special flagwise that I would need to specify to tell it to include symbol and debug information?

On Tue, 4 May 2004, Patrick Flanagan wrote: > I was able to run through all the C/C++ benchmarks in SPEC using LLVM. > I'm on OS X 10.3.3. I did a quick comparison between LLVM (latest from > CVS as of 4/27) and gcc 3.3 (Apple's build 20030304). For simplicity's > sake, the only flag I used was -O3 for each compiler and I was using > the C backend to generate native

On May 6, 2004, at 12:01 AM, Chris Lattner wrote: > On Wed, 5 May 2004, Patrick Flanagan wrote: >>>> and I'm not convinced that GCC is doing a very good job (ie, without >>>> syntactic loops). >>> >>> Yup, this is EXACTLY what is going on. >> >> Interesting. Now that you mention it, I do recall thinking the loops >> that llvm

Here is some a bit more optimized version and bug fixed patch of my previous patchset. In my testing of trying to boot from a USB flash device, I have gotten anywhere from 6x-16x better performance using these patches compared to syslinux's default open/read_file data path when using mboot.c (modified to use fs->ops.open() interface). I'm loading about 50MB of source kernel/modules into

Hello everyone: After I played with Rspec for three months, I realized a weird behavior of mocking ruby classes (e.g. File). Please let me post a sample code before I point out the problems: #file_reader.rb (to be tested) class FileReader def do_read File.read(''asd.txt'') end end #file_reader_spec.rb describe FileReader, "do_read" do it "should throw File Not Found on non-existent file" do reader = FileReader.new() lambda {...

On Wed, 5 May 2004, Patrick Flanagan wrote: > >> and I'm not convinced that GCC is doing a very good job (ie, without > >> syntactic loops). > > > > Yup, this is EXACTLY what is going on. > > Interesting. Now that you mention it, I do recall thinking the loops > that llvm generated looked a bit different than the gcc loops. I'll go > back and take

These changes are based on Jason's latest hmm branch. Patch 1 was previously posted here [1] but was dropped from the orginal series. Hopefully, the tests will reduce concerns about edge conditions. I'm sure more tests could be usefully added but I thought this was a good starting point. [1] https://lore.kernel.org/linux-mm/20190726005650.2566-6-rcampbell at nvidia.com/ Ralph Campbell

This series adds new functions to the mmu interval notifier API to allow device drivers with MMUs to dynamically mirror a process' page tables based on device faults and invalidation callbacks. The Nouveau driver is updated to use the extended API and a set of stand alone self tests is added to help validate and maintain correctness. The patches are based on linux-5.5.0-rc6 and are for