search for: 20111021

...tain, and because they were much better suited to offer reasonable diagnostics. Any plan to reverse that decisions is likely to meet a lot of resistance. --Owen -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111021/7f11d0c9/attachment.html>

...s and not have lots of problems. This is compounded over time as things change. Hopefully what I do will meet with acceptance. I'll take that chance. Reed -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111021/5fa2fee3/attachment.html>

...fixed) to make the echo cancellation works with an USB microphone ? If it's not, do you now another good library which can handle this configuration ? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/speex-dev/attachments/20111021/e9c961ce/attachment.htm

...more -- but $7.99 is the _right_ introductory price. word-of-mouth will be what sells this pup, so you want it to flow copiously right now. -bowerbird -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://six.pairlist.net/pipermail/markdown-discuss/attachments/20111021/f9a6075f/attachment.html>

...lopers mailing list LLVMdev at cs.uiuc.edu<mailto:LLVMdev at cs.uiuc.edu> http://llvm.cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111021/61d34246/attachment.html>

...ntegers of various sizes to double. Is it possible to detect which instruction should be  used ("uitofp" or "sitofp" )? Thank you, Alexandra -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111021/a3ce4164/attachment.html>

...v. A Testing BoF should seek to better describe the issues, identify any interest or actual work in addressing the issues, and foster potential collaboration. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111021/597fd900/attachment.html>

...(SlotNum)s on the fly in that file (AsmWriter.cpp), so is there any way at all to get this information from the operation itself, via Instruction, Value or Type? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111021/55f4887c/attachment.html>

...t;B # How can I deal with this mailbox (using mdbox here)? Thanks! -- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://dovecot.org/pipermail/dovecot/attachments/20111021/1ed48d80/attachment-0004.bin>

On 10/20/2011 07:42 AM, Duncan Sands wrote: >> For the level of specificity you're looking for, just the source code itself. The LLVM IR language documentation is not, and isn't intended to be, a true language standard document in the same way that the C or C++ standards are. For any given case, check the docs first, and if your question isn't answered there, check the source

> For the level of specificity you're looking for, just the source code itself. The LLVM IR language documentation is not, and isn't intended to be, a true language standard document in the same way that the C or C++ standards are. For any given case, check the docs first, and if your question isn't answered there, check the source code of the target(s) you're interested in.

Not yet. That is, I don't think any have been filed at all for 3.0. I don't know whether to be happy or worried. :-) Any that are regressions should be marked with the 'regression' keyword and be a release blocker. -bw On Oct 20, 2011, at 8:40 AM, Jim Grosbach wrote: > Hi Bill, > > Do we have a list of which PRs have been filed that are considered release blockers?

Hi guys, we have a rebalance running on eight bricks since July and this is what the status looks like right now: ===Tue Oct 18 13:45:01 CST 2011 ==== rebalance step 1: layout fix in progress: fixed layout 223623 There are roughly 8T photos in the storage,so how long should this rebalance take? What does the number (in this case) 22362 represent? Our gluster infomation: Repository

This is http://llvm.org/pr10514 Unfortunately the fix did not make it into that version of clang. On Oct 20, 2011, at 7:47 AM, Somorjai, Akos wrote: > Here's a code generated with -Os on darwin/x86_64 with clang from the Xcode 4.2 GM toolset on Mac OSX 10.7.2 (Apple clang version 3.0 (tags/Apple/clang-211.10.1) (based on LLVM 3.0svn), Target: x86_64-apple-darwin11.2.0) > >

Here's a code generated with -Os on darwin/x86_64 with clang from the Xcode 4.2 GM toolset on Mac OSX 10.7.2 (Apple clang version 3.0 (tags/Apple/clang-211.10.1) (based on LLVM 3.0svn), Target: x86_64-apple-darwin11.2.0) 0x000000010277d281 <+2102> lea 0x1d43bd0(%rip),%rax # 0x1044c0e58 <gFloorPlanCutData> 0x000000010277d288 <+2109> movaps 0x80(%rax),%xmm0

Hi gang - Love CentOS - you guys to a fabulous job. It has been a while since I saw any update... I went to twitter.com/centos nothing there, twitter.com/centos6 nothing there, went to the qa calendar stuff nothing there. Last I saw was something in September saying all RPM's are built and doing ISO's. Then nothing. I know the whole story about its ready when its ready and I'm all

...might be useful to gather these stats as late as possible to take into consideration the final impact of layout, including the effect on any later passes. -Andy -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111021/302813af/attachment.html>

On Thu, Oct 20, 2011 at 10:53 AM, Jakob Stoklund Olesen <stoklund at 2pi.dk>wrote: > > On Oct 20, 2011, at 9:56 AM, Chandler Carruth wrote: > > > A new patch is attached that is *much* less of a rough draft. Sorry for > any confusion due to the early state of the patch. > > Thanks, Chandler. This is great stuff. > > > Still, I never intended this to be