similar to: vorbis-tools-1.1.1 build fails during linking

Hello, I am trying build vorbis-tools-1.1.1 in the framework of my tool (see signature). The essence of the tools is that it builds and install everything locally, and, of course, it uses the available mechanisms to specify search paths for both headers and libraries; the tool first builds dependencies abd then the target itself. So, for example, 'configure' for vorbis-tools-1.1.1 is

Anybody ? Note: forwarded message attached. Applications From Scratch: http://appsfromscratch.berlios.de/ ____________________________________________________________________________________ Need a quick answer? Get one in minutes from people who know. Ask your question on www.Answers.yahoo.com -------------- next part -------------- An embedded message was scrubbed... From: Sergei

Hello, curl-7.16.0 breaks compilation of vorbis-tools-1.1.1 - please see http://curl.haxx.se/mail/archive-2006-11/0046.html for details. According to Daniel Stenberg, CURLOPT_MUTE is deprecated. Could you please update vorbis-tools code so it won't use deprecated features of 'curl' ? Should I file a bug report regarding this issue ? Thanks, Sergei. Applications From Scratch:

I compared quicktime aac and vorbis,i think quicktime aac is better than vorbis at 80Kbps. please tell me if i'm wrong. using command: qtaacenc.exe --tvbr 31 --highest --samplerate keep test.wav qt.m4a oggenc2.exe --raw -q 1.6 test.wav -o vorbis.ogg the version: qtaacenc version 20100725 with QuickTime 7.6.7 OggEnc v2.87 (libvorbis 1.3.1) links:

What is the best practice for seeking to a specific (arbitrary) PCM sample in an Ogg file that contains vorbis, using libvorbis? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/vorbis/attachments/20150518/1d3bb0ae/attachment.htm

Hi! Sorry, I know the rules for comparing objective subjective listening impressions, but I'd like to know whether from the algorithmic or implementer's point of view the following personal impressions can be confirmed: Comparing MP3 with Vorbis at rather high bitrates, I had the impression the Vorbis sounded more crispy, while MP3 sounded somewhat softened. I preferred Vorbis for that

Current Version: 0.3.3 (latest devel 0.3.4-cvs) License: GPL Author: Timo Schulz <twoaday@freakmail.de> Available from: http://www.winpt.org/opencdk.html Hi, this is the first public announcement for OpenCDK. It is a library to provide some basic parts of the OpenPGP Message Format (RFC2440). First the library was planned for key conversation in GnuTLS and other applications which

Hello. Attached are some patches that some Debian users of vorbis-tools have sent to our BTS over the years (numbers refer to Debian bugs). It'd be nice to see them integrated. They apply cleanly to SVN as of today. The largefile_support one is a bit bigger than just the configure.ac since the submitter adviced that config.h got included in all C source files before the standard includes,

Hello. Attached are some patches that some Debian users of vorbis-tools have sent to our BTS over the years (numbers refer to Debian bugs). It'd be nice to see them integrated. They apply cleanly to SVN as of today. The largefile_support one is a bit bigger than just the configure.ac since the submitter adviced that config.h got included in all C source files before the standard includes,

Andy, Thank you for the extended and prompt answer. Let me try to summaries my current position so you (and everyone interested) would have a better view of the world through my eyes ;) 1) LLVM first robust VLIW target is currently in review. It needs for scheduling strategy/quality are rather different than what current scheduler(schedulers) can provide. 2) My first attempt in porting

Hi Sergei, I just fixed the broken test case for PR13719 with r163107, but from the debugging output you've posted it suspect it won't fix your test case. Your analysis looks good - findLastUseBefore(..) doesn't appear to be handling physregs. I'm surprised that isn't causing more failures. I'll see if I can find a failing case in the LLVM test-suite (it's been a

This patch cleans up the vorbis-tools Makefile.am files so they work with both automake 1.4 and 1.6. Some changes to configure.in were also needed in order to get things to work (and to fix some ac 2.50 issues). Please remove config.h from cvs as it is a generated file and empty anyway. automake 1.6 isn't really incompatable with 1.4, it's just more picky about you sticking to the rules:

Is there a test case that you can share ? On Jan 29, 2013, at 9:24 AM, Sergei Larin <slarin at codeaurora.org> wrote: > Nadav, > > Thanks for the quick response. By now I am convinced that the given loop > ends up vectorized with enough difference to cause bad things later on, but > I have not found the exact cause yet. To continue with my work I'll have to >

Eric, Let me clarify it a bit... without type uniqueing for LTO + debug will I have a highly inefficient IR representation or incorrect debug info? If debug info for LTO is known to be non-useful or ambiguous or flat wrong - there is no point in fixing its emission... or will it still be practical and if I manage to improve it somewhat the customer will still have some value-add by using it?

Tom, I do not have your call stack, but packetizer calls ScheduleDAGInstrs::buildSchedGraph to create dependency model. If this is the first time you use the new MI sched infrastructure (like your target has not implemented misched yet) there might be some work needed to implement couple target hooks. isSchedulingBoundary is one of them. Also try to disable that assert and see what happens. It

Nadav, Thanks for the quick response. By now I am convinced that the given loop ends up vectorized with enough difference to cause bad things later on, but I have not found the exact cause yet. To continue with my work I'll have to simply turn off vectorization for now, but I will come back and investigate. Again, there is some indeterminism in order of PHIs processing somewhere. I'll

Andy, Yes, this is what Arnold has suggested also, and from this point it looks like it should work, but it will require parsing the bundle every time we care to know whether this is a real use or a conditional def. This might become awkward... but I guess I should provide a better use case to prove my point. Sergei -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum. >

Lang, I think I am getting closer to understanding this. The findLastUseBefore() should probably look something like this: // Return the last use of reg between NewIdx and OldIdx. SlotIndex findLastUseBefore(unsigned Reg, SlotIndex OldIdx) { SlotIndex LastUse = NewIdx; if (TargetRegisterInfo::isPhysicalRegister(Reg)) { for (MCRegUnitRootIterator Roots(Reg,

We observed exact same problem, and I did put in place a mechanism to recognize and break such false dependencies right before pre-RA scheduler (in DAG->DAG lowering), but the immediate observed effect for our back end was performance reduction, since none of the current schedulers were capable of dealing with newly presented parallelism in BB (resulted in high reg pressure and

Arnold, It is not my code per say - this is what is done in LiveIntervalAnalysis.cpp collectRanges(), it wants to iterate over "units" of D1 (whatever they are assumed to be), but right there it associates them with actual physical register live ranges (see the tread below), and it does it wrongly. I was trying to pinpoint exactly to where the issue is, but there are too many