similar to: [LLVMdev] General modular and multiprecision arithmetic

I suggest that LLVM needs intrinsics for add/sub with carry, e.g. declare {T, i1} @llvm.addc.T(T %a, T %b, i1 c) The current multiprecision clang intrinsics example: void foo(unsigned *x, unsigned *y, unsigned *z) { unsigned carryin = 0; unsigned carryout; z[0] = __builtin_addc(x[0], y[0], carryin, &carryout); carryin = carryout; z[1] = __builtin_addc(x[1], y[1],

It takes two "llvm.uadd.with.overflow" instances to model the add-with-carry when there is a carry-in. Look at the IR generated by the example. I figured that the optimization of this would bedifficult (else it would have already been done :-)). And would this optimization have to be done for every architecture? On 02/15/2017 04:28 PM, Stephen Canon wrote: > > Why do you think

Stephen Canon via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Why do you think this requires new intrinsics instead of teaching the optimizer what to do with the existing intrinsics? IMO, as a multiprecision math library maker, the "teaching the optimizer what to do with the existing intrinsics" approach is much better as long as it can be made to work. If one is

On 02/16/2017 12:08 PM, Stephen Canon wrote: >> On Feb 16, 2017, at 9:12 AM, Bagel <bagel99 at gmail.com >> <mailto:bagel99 at gmail.com>> wrote: >> >> I figured that the optimization of this would bedifficult (else it would >> have already been done :-)) > > Don’t make this assumption. There’s lots of opportunities for optimization > scattered

Chris Lattner wrote: >On Mon, 18 Jun 2007, Sandro Magi wrote: > > >>Generated code. So the memory used for the integer at program runtime >>is inlined into the allocation point then? So if I define a local >>variable of type 'i1024', it will allocate a block of 1024 bits on the >>stack, if I define a struct with an i1024, it will be in the struct

On 6/18/07, Chris Lattner <sabre at nondot.org> wrote: > On Mon, 18 Jun 2007, Sandro Magi wrote: > > Ok, so if I needed very precise control over the allocation of memory, > > then I should avoid using integers with bit widths larger than 64 bits > > (or perhaps 128)? Is there a hard rule for an integer being stack > > allocated, ie. one that doesn't depend on

Adding llvm-dev to this thread as this is probably worth wider discussion. See the original patch email below. If you're sending just code-related comments, consider dropping llvm-dev. On Mon, Aug 20, 2012 at 3:37 AM, Chandler Carruth <chandlerc at gmail.com>wrote: > Hello all! I've been busy working on a somewhat larger patch than usual, > and Duncan indicated I should get

> On Feb 21, 2017, at 9:54 PM, Nemanja Ivanovic via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I believe that providing additional intrinsics that would directly produce the ISD::ADDC/ISD::SUBC nodes would provide the additional advantage of being able to directly produce these nodes for code that doesn't have anything to do with multiprecision addition/subtraction. I am

On Mon, 18 Jun 2007, Sandro Magi wrote: > Generated code. So the memory used for the integer at program runtime > is inlined into the allocation point then? So if I define a local > variable of type 'i1024', it will allocate a block of 1024 bits on the > stack, if I define a struct with an i1024, it will be in the struct > itself, etc. Yes, exactly. > Is there anyone

On Sat, October 11, 2008 3:13 pm, Chris Lattner wrote: > [...] Sending invalid > code into the backend is violating a very important invariant in the > API. I don't see how it would be any different then passing in a null > pointer or garbage pointer into an API that would then bus error. Besides invalid IR, codegen also uses abort and assert when it encounters valid and

On Oct 13, 2008, at 10:05 AM, Dan Gohman wrote: > On Sat, October 11, 2008 3:13 pm, Chris Lattner wrote: >> [...] Sending invalid >> code into the backend is violating a very important invariant in the >> API. I don't see how it would be any different then passing in a >> null >> pointer or garbage pointer into an API that would then bus error. > >

Do you have plans to add other intrinsics? I'm curious as to why there is an llvm.sin intrinsic and an llvm.cos intrinsic, but no llvm.atan intrinsic. Why is there an llvm.pow intrinsic but no llvm.log intrinsic? Also, have you thought about integer intrinsics like multiprecision multiply (u32xu32->u64) and multiprecision divide (u64/u32->(dividend:u32,remainder:u32))? Regards,

On Wed, Mar 10, 2004 at 11:31:40PM -0800, Andrew Morton wrote: >... > ext3-journalled-quotas-2.patch > ext3: journalled quota >... This patch broke modular quota: WARNING: /lib/modules/2.6.4-mm1/kernel/fs/quota_v2.ko needs unknown symbol mark_info_dirty cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There

Subject says it all. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I am developing a CMS using act_as_tree for the pages and act_as _list to order them (as shown on Railscasts). Each page can load a custom ERB template, for instance I have one to display a standard article and one to display a group of articles (so acting as a category of underling articles). If I want to develop a forum, let''s say that I have a page with id 5, with name forum, how can

Hi Keir: It has been brought to my attention that modular oprofile is broken because it now calls get_vm_area which is not an exported function. This appears to be the result of the changeset that removed vm_map_xen_pages which was only used by oprofile. So we either need to export get_vm_area in Xen, or put that function back. What do you think about this? Thanks, -- Visit Openswan at

Hello everybody, I''ve just started studying Rails and I love it already for its simple, pragmatic spirit and the effectiveness and productivity that its approach brings. I''m thinking about building new applications on top of it and about rebuilding existing J2EE applications in Rails as well, but I''ve come across an architectural problem: we need to structure

The virtio configuration options are inconsistent. According to this, every options that needs virtio will select it: # Virtio always gets selected by whoever wants it. config VIRTIO tristate Note that it's not user-selectable, so any config file that tries to set it will be ignored when kconfig loads those options. And yet we have a whole set of options that depend on VIRTIO, like

The virtio configuration options are inconsistent. According to this, every options that needs virtio will select it: # Virtio always gets selected by whoever wants it. config VIRTIO tristate Note that it's not user-selectable, so any config file that tries to set it will be ignored when kconfig loads those options. And yet we have a whole set of options that depend on VIRTIO, like

Hi all, I'm Agust?n Benito, community Manager of ModularIT. Following the advices of the CENTOS crew that I met at FOSDEM a few days ago, I introduce ModularIT in this mailing list so the Centos community can take a look at it, since it is strongly related to this project. ModularIT is a SOA architecture based on virtualised services. Our goal is to save time in tedious activities allowing