search for: 20130218

...gt; *100*,1,AGI(never_reached.pl) ... A "normal dialplan reload command" would echo no warning or something similair. Best regards -Thorsten- -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20130218/bb3947bf/attachment.htm>

...E4). Please correct me if I'm wrong in this assumptions. My attempts to utilize this feature fail (I generate LLVM IR directly, I'm not using clang) and this looks very similar to the one described by Benjamin in this mail thread: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20130218/166710.html So the question - what is the state of supporting fat binaries. Is it expected to work on x86? Thanks in advance, Dmitry. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131003/ef082432/attachme...

https://bugs.freedesktop.org/show_bug.cgi?id=60772 Priority: medium Bug ID: 60772 Assignee: nouveau at lists.freedesktop.org Summary: xf86-video-nouveau fails to modprobe nouveau: KMS not enabled QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All)

...e. But I've not thought about this deeply, I just find the idea of having the backend be responsible for matching up the function names somewhat distasteful. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130218/e577857f/attachment.html>

...the source line number from a metadata field. PS: for Allocas, it seems that I have to use findDbgDeclare method from DbgInfoPrinter.cpp. Thank you in advance ! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130218/e9c7b4a1/attachment.html>

...e correct me if I'm wrong in this assumptions. > > My attempts to utilize this feature fail (I generate LLVM IR directly, I'm not using clang) and this looks very similar to the one described by Benjamin in this mail thread: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20130218/166710.html > > So the question - what is the state of supporting fat binaries. Is it expected to work on x86? > Hi Dmitry, I did it not so much to support fat binaries, but to support correct code generation in LTO. The problem was that it wasn't implemented correctly. Many of the...

...without problem. Therefore i assume a problem in the "nouveau" driver. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20130218/a393226a/attachment.html>

...'s used during IR modification and not code generation. -bw -------------- next part -------------- A non-text attachment was scrubbed... Name: clang.nobuiltin.diff Type: application/octet-stream Size: 587 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130218/b329ab5d/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: nobuiltin.diff Type: application/octet-stream Size: 7487 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130218/b329ab5d/attachment-0001.obj>...

...ins = acl quota stats mail_log notify imap_acl imap_quota imap_stats } -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: <http://dovecot.org/pipermail/dovecot/attachments/20130218/a91f58ef/attachment-0003.bin>

On Feb 18, 2013, at 4:45 PM, Chris Lattner <clattner at apple.com> wrote: > > On Feb 18, 2013, at 1:54 PM, Bill Wendling <wendling at apple.com> wrote: > >> Hi LLVMites! >> >> This patch adds the 'nobuiltin' attribute to to LLVM. This is needed during LTO, which right now ignores this attribute and command line flag. I want to make this an

...failed to find anything specific. Has anyone else run into a problem like this, or have insight about what might be causing it or how to avoid it? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130218/d2daa165/attachment.html>

Just a reminder, the Cambridge LLVM Social is this week on the Kingston Arms. http://www.kingston-arms.co.uk/ cheers, --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130218/bf47bf37/attachment.html>

...r /tags I tried svn checkout http://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx at 165095, but that also doen't work for either /trunk or /tags Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130218/a25e0874/attachment.html>

...sting, have a few hours before going live with this platform and was under a fair amount of pressure. All good now!! :) Regards, Gavin > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20130218/529f605b/attachment.html>

Un texte encapsul? et encod? dans un jeu de caract?res inconnu a ?t? nettoy?... Nom : non disponible URL : <https://stat.ethz.ch/pipermail/r-help/attachments/20130218/1ef898cb/attachment.pl>

...be considered calls to builtin functions? How does this work? If I build with -fno-builtin-fputs, why would an attribute be added to a call to printf? -Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130218/372556b0/attachment.html>

On Feb 13, 2013, at 2:32 PM, Justin Holewinski <justin.holewinski at gmail.com> wrote: > > This is a very interesting one that is orthogonal to Bill's work. The preferred approach for this sort of thing is to change the LoopUnroll pass to take the unroll threshold as a constructor argument or a struct that wraps up all of the configuration settings. When the pass is *default*

...a Maffra. *Ciência da Computação Universidade Federal de Minas Gerais (31) 8615-3077* "Don't count the days, make the days count." -- Muhammad Ali -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130218/7e11a1fd/attachment.html>

...f I'm wrong in this assumptions. > > My attempts to utilize this feature fail (I generate LLVM IR directly, I'm > not using clang) and this looks very similar to the one described by > Benjamin in this mail thread: > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20130218/166710.html > > So the question - what is the state of supporting fat binaries. Is it > expected to work on x86? > > Hi Dmitry, > > I did it not so much to support fat binaries, but to support correct code > generation in LTO. The problem was that it wasn't implemented c...

...not want to worry about the alu's, but it is fine as long as there are any FU of the first row (BITS) available. What is missing? Thanks, Jonas Paulsson -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130218/6a57cecf/attachment.html>