search for: haberman

...y going to give away copies for free to their competitors? Still, using a more restrictive license for companies who wish to keep their modifications private achieves the same goals without the risk of letting a BSD-licensed copy go into the wild (assuming you wish to keep it GPL). Josh -- Josh Haberman <joshua@haberman.com>

...olution be to allocate an APPLICATION metadata block id for comments? If so, what format would be best for storing this kind of information? A series of null-terminated strings seems the simplest, say: ARTIST=Some Artist\000ALBUM=Some Album\000 Comments? (no pun intended :-) Joshua -- Joshua Haberman <joshua@haberman.com>

Hi Matt, thanks for the reply. * Matt Zimmerman (mdz@debian.org) wrote: > On Tue, Oct 30, 2001 at 11:39:11PM -0800, Joshua Haberman wrote: > > > So I was wondering if flac could be incorporated into the filesystem > > driver so that any file ending in .wav would be transparently encoded > > into flac. I don't know if this could be done at the vfs level so that > > it could be done to all filesyst...

...between the RuntimeDyld component and the memory manager to facilitate setting permissions when that is desired. -Andy -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Chris Lattner Sent: Tuesday, July 17, 2012 10:02 PM To: Josh Haberman Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] rwx pages dangerous? On Jul 17, 2012, at 8:07 PM, Josh Haberman wrote: > I noticed that JITMemoryManager allocates its slabs as rwx. Isn't it a security problem to have memory mapped as both writable and executable? I think JITs often av...

...original message in the archive to refresh your memory, but geocrawler is down for nightly maintenance. Joshua [0] I made that claim up, but I hope it's true. In any case, the reduced I/O should at least help compensate for the overhead of having to decompress on-the-fly. -- Joshua Haberman <joshua@haberman.com>

I'm kind of swamped today so I'll answer what I can get away with until tonight: --- Joshua Haberman <joshua@haberman.com> wrote: > The most interesting questions to me are ones you didn't address: > > 1. Will Ogg FLAC become the default manifestation of the FLAC codec? > If not, why not? What does Ogg not offer that makes it worth having > two different file formats of...

...ead-only data sections. These are minor problems, of course, but I think it's a place where there's room for improvement. -Andy -----Original Message----- From: Jim Grosbach [mailto:grosbach at apple.com] Sent: Wednesday, July 18, 2012 2:22 PM To: Kaylor, Andrew Cc: Chris Lattner; Josh Haberman; llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] rwx pages dangerous? In the world of the MCJIT, memory allocation, including permissioning, is the responsibility of the client application. The MCJIT only directly touches memory in the address space of the host. Once the old JIT is removed, all of t...

...hen FLAC already works so well. The Ogg people would be much better off adopting FLAC and working on Tarkin. I think you would benefit greatly from the publicity of being an official Ogg codec. Many people know about Vorbis, but FLAC is not well known. Sorry if this is a FAQ. Joshua -- Joshua Haberman <joshua@haberman.com>

--- Joshua Haberman <joshua@haberman.com> wrote: > 2. I was hoping that the new metadata API would mean that an encoder > could be written without having to know *anything* about the bitwise > layout of the stream format, but that seems not to be the case. From > src/flac/encode.c: > > ( void...

...e memory manager to facilitate setting permissions when that is desired. > > -Andy > > > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Chris Lattner > Sent: Tuesday, July 17, 2012 10:02 PM > To: Josh Haberman > Cc: llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] rwx pages dangerous? > > > On Jul 17, 2012, at 8:07 PM, Josh Haberman wrote: > >> I noticed that JITMemoryManager allocates its slabs as rwx. Isn't it a security problem to have memory mapped as both writable and...

...TREAMINFO block (and any seek tables as well). What do you think? Joshua P.S. I don't think I've ever read any code that so shamelessly refuses to break at 80 chars. :-) Do you have certain settings in your editor that makes code formatted this way more readable? -- Joshua Haberman <joshua@haberman.com>

...e that information to the memory manager, which should be responsible for actually setting the permissions. -Andy -----Original Message----- From: Jim Grosbach [mailto:grosbach at apple.com] Sent: Wednesday, July 18, 2012 4:05 PM To: Kaylor, Andrew Cc: llvmdev at cs.uiuc.edu; Chris Lattner; Josh Haberman Subject: Re: [LLVMdev] rwx pages dangerous? Somewhat, yes. The MCJIT currently doesn't support lazy compilation in general, and things like notifications back (via the memory manager) when new sections have been produced and such needs to be part of that. Your'e right that, for now, the un...

...lems, of course, but I think it's a place where there's room for improvement. > > -Andy > > > -----Original Message----- > From: Jim Grosbach [mailto:grosbach at apple.com] > Sent: Wednesday, July 18, 2012 2:22 PM > To: Kaylor, Andrew > Cc: Chris Lattner; Josh Haberman; llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] rwx pages dangerous? > > In the world of the MCJIT, memory allocation, including permissioning, is the responsibility of the client application. The MCJIT only directly touches memory in the address space of the host. Once the old JIT is re...

I noticed that JITMemoryManager allocates its slabs as rwx. Isn't it a security problem to have memory mapped as both writable and executable? I think JITs often avoid this by mapping their memory as rw, then switching it to rx once the data has been written. I was facing a similar problem in a JIT of my own and was curious to see how LLVM addresses this issue. Thanks, Josh --------------

--- Joshua Haberman <joshua@haberman.com> wrote: > * Josh Coalson (xflac@yahoo.com) wrote: > > I'm kind of swamped today so I'll answer what I can get > > away with until tonight: > > > > --- Joshua Haberman <joshua@haberman.com> wrote: > > > The most interestin...

On Jul 17, 2012, at 8:07 PM, Josh Haberman wrote: > I noticed that JITMemoryManager allocates its slabs as rwx. Isn't it a security problem to have memory mapped as both writable and executable? I think JITs often avoid this by mapping their memory as rw, then switching it to rx once the data has been written. I was facing a simi...

...in C++. Would it be possible to make these small changes for C++ compatibility? It would also be nice if you would include: #ifdef __cplusplus extern "C" { #endif at the beginning and one to match at the end, but this can always be done by the host program. Thanks, Joshua -- Joshua Haberman <joshua@haberman.com>

...and FLAC. Instead I'm stuck writing and maintaining separate code for libsndfile, libvorbis, libmad, lame, and libFLAC. I also don't foresee all of the windows audio jukebox programs that my friends use linking with this universal audio format library anytime soon. :-( Joshua -- Joshua Haberman <joshua@haberman.com>

It's official: http://xiph.org/ogg/flac.html It's OK to keep submitting patches but I'm going to hold off on integrating anything until CVS is moved over. Note that codec code (libFLAC, libFLAC++, libOggFLAC, libOggFLAC++) will be covered under Xiph's BSD-like license from here on out. Josh __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus -

Are there any plans to add stack switching to LLVM? I've seen a few proposals for it floating around (some even implemented): http://ulir.ul.ie/handle/10344/2927 (implemented in: https://github.com/stedolan/llvm) https://code.google.com/p/llvm-stack-switch/ But I couldn't find any discussion of whether there was a plan to integrate one of these. Any plans to add this feature? Thanks,