similar to: include/share/alloc.h

--- Erik de Castro Lopo <erikd-flac@mega-nerd.com> wrote: > Josh, > > I noticed the recent addition of the above file. In that file you > have > things like: > > static void *safe_malloc_(size_t size) > { > /* malloc(0) is undefined; FLAC src convention is to always > allocate */ > if(!size) > size++; >

--- include/share/alloc.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/share/alloc.h b/include/share/alloc.h index 914de9ba..63878db0 100644 --- a/include/share/alloc.h +++ b/include/share/alloc.h @@ -168,7 +168,7 @@ static inline void *safe_realloc_add_2op_(void *ptr, size_t size1, size_t size2) free(ptr); return 0; } - return realloc(ptr, size2); + return

Hello, I had some difficulties compiling the current git ( http://git.xiph.org/?p=flac.git;a=commit;h=a7e3705d051bafd1cae90f6605287cc1d9f2a18d ) using the Ubuntu 12.04 supplied MinGW32 cross compiler: I configured the FLAC build with --host=i586-mingw32msvc --target=i586-mingw32msvc --build=i586-linux but ran into several linker problems. Are these options somehow wrong? It worked fine when

I'm looking at an issue reported by the Coverity static analyzer. In iconvert() in src/share/utf8/iconvert.c on line 152 there is newbuf = safe_realloc_add_2op_(utfbuf, ...); If the request size is not valid, the function will free utfbuf and return 0. This is followed by goto fail and utfbuf is freed for the second time. A simply fix would be to set utfbuf to 0 if newbuf is 0. However, this

Hi all, Are there any plans to add more functionality to command-line editing and history editing on the command line? In MATLAB (I know, comparisons are odious ...), you can type "p" and up-arrow on the command line and scroll through the recently entered commands beginning with "p". This is a very useful feature and something that I believe is not replicated in R. Please

In Centos 5.3, a bad problem has surfaced in user land. We want to use either Evince or Adobe acroread as the pdf view, but the update of kdegraphics has somehow screwed up these systems so that the odious, horrible, awful pdf viewer kghostview is used. It is what you get when you doubleclick on pdf files, it is what programs get when they try to use xdg-open framework. This happens even though

Hi, I obtain the following error messages when trying to compile flac 1.2.1 under MinGW : gcc -DHAVE_CONFIG_H -I. -I. -I../.. -DFLaC__INLINE=__inline__ -DNDEBUG -I../.. -I./include -I../../include -O3 -funroll-loops -finline-functions -Wall -W -Winl ine -g -O2 -MT stream_decoder.lo -MD -MP -MF .deps/stream_decoder.Tpo -c stream_ decoder.c -DDLL_EXPORT -DPIC -o .libs/stream_decoder.o

I understand these objections. They ends up being a problem at the limit (ie the example of the 64k store or 1Mb+ aggregate). These probably require their own fix or probably just shouldn't be supported. That being said, there is a vast space between what is done now and aggregate so big that it causes real hard problems like the ones you mention. reducing that gap seems like a win to me.

I have several orders that are being updated in an internal data entry app. I start by going from an order to pop-up form that allows a user to select items to add to a field in the order. The pop-up form contains 2 partials for drag and drop functionality from AWD. The user starts by selecting a category in a drop down list. Then on select, the first partial is filled with the list of

2015-08-16 22:10 GMT-07:00 David Majnemer <david.majnemer at gmail.com>: > > > I would argue that a fix in the wrong direction is worse than the status > quo. > How is proposed change worse than status quo ? > > >> >> The argument that target are relying on InstCombine to mitigate IR >> requiring legalization seems dubious to me. First, because both

Package: logcheck-database Version: 1.2.69 Severity: normal on systems without configured global locale, i get lines like this in the logcheck filtered logs: Jun 10 21:12:13 ... sshd[9729]: pam_env(sshd:setcred): Unable to open env file: /etc/default/locale: No such file or directory this looks like a warning that is perfectly ok but does not do any harm and occurs because when no global locale

Good day everyone, A Solution now exists for those of you still looking for the first model of Quad T1/E1 Interface Cards - the T400P and E400P. The T400P and E400P were manufactured by Digium until a few months ago, and were designed and released under the GNU Public License as the Tormenta II by Zapata Telephony. Varion, Inc. is now in full production manufacturing these boards. With the

Hi Alp, A clear place that smart pointers *shouldn't* be used are 'create' > functions. > > There's already a strong convention in the thousands of 'create' functions > across the codebase and they have the clear, well-defined behaviour of > returning a new pointer. > > We all know what to expect from these functions, much like new/delete in > C++

2015-08-16 23:21 GMT-07:00 David Majnemer <david.majnemer at gmail.com>: > > > Because a solution which doesn't generalize is not a very powerful > solution. What happens when somebody says that they want to use atomics + > large aggregate loads and stores? Give them yet another, different answer? > That would mean our earlier, less general answer, approach was either

This has the advantage of being more efficient than the included routines and allows distros to centralize crypto mainteniance on a few libraries. --- configure.ac | 4 +- m4/ax_check_openssl.m4 | 124 +++++++++++++++++++++++++++++++++++++ src/libFLAC/Makefile.am | 2 +- src/libFLAC/include/private/md5.h | 8 ++- src/libFLAC/md5.c

There seems to be some uncertainty about the use of smart pointers (previously OwningPtr, now std::unique_ptr and std::shared_ptr predominantly) in the LLVM project as a whole, so here's a thread to discuss/clarify/etc the project preferences/direction with regard to smart pointer usage. For some context, see discussions in LLVM r212403 and Clang r213307. The basic question here seems to be

emigrate tough sprightly torque tallyho alizarin dispersible chipmunk hypertensive rhine tincture creating cryptanalyze conjoint odious also downstream brew footage