search for: concreteness

Hi, I would like to implement a fix to how LLVM handles/creates debug info for entities declared inside a basic block. Below you will find 5 parts: 1. Motivation for this fix. 2. Background explaining the cases that need to be fixed. 3. An example for each case. 4. Proposal on how to represent each case in dwarf. 5. Secondary (workaround) proposal which might be

On Mon, Dec 14, 2015 at 7:01 AM, Aboud, Amjad via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > I verified that GDB 7.10 does support “DW_AT_abstract_origin” attribute on > “DW_TAG_lexical_block”. > I take it you mean that it does the right thing, finding the direct children of the abstract block when stepping into the inlined subroutine, etc? & this was a

Hi all, I''ve more than one rails based applications on my machine. When I upgrade my gems (including rails), I usually have to upgrade each application to be able to continue developing/using it... But some of these web applications don''t need to be up to date. I would be happy enough with older version of rails for these applications (, or I don''t have time to fix

As a concrete question, I understand 'Value' class is the parent of many concrete sub-classes. Let's say I retrieve a Value* value = store_inst->getValueOperand(). Unless I know what the sub-type is, how can I further use this object? I tried something like this: ================================================= Value* value = store_inst->getValueOperand()

*From: *JF Bastien via llvm-dev <llvm-dev at lists.llvm.org> *Date: *Thu, May 9, 2019 at 1:30 PM *To: *Jesper Antonsson *Cc: *dag at cray.com, llvm-dev at lists.llvm.org I don’t think you have consensus to move forward at this point in time. My > expectation, which I think represents LLVM’s historical approach, is that a > path to full support be planned out before this effort starts.

Hi all, I'm giving a talk in a few days to a group of psychology faculty and grad students re the R statistical language. Most people in my dept. use SAS or SPSS. It occurred to me that it would be nice to have a few concrete examples of things that are fairly straightforward to do in R but that are difficult or impossible to do in SAS or SPSS. However, it has been so long since I have used

I posted something about this a week ago wihtout response, but have made some progress since. However, I''m still not getting exactly what I want. OK, three core tables: create_table :reference_items do |t| t.column :title, :string, :limit => 255 t.column :year, :integer, :limit => 4 t.column :type, :string t.column

Very interesting topic. "What I want to know is *WHY* people are doing this?" Here goes my view - I've used many for loops, and each time I realize how stupid that is... AFTER I learned how to avoid it. But it's difficult to avoid them without knowing how to do it. (Monsieur de LaPalice wouldn't have puted it better...) For loops are conceptually very easy to understand.

Hi All- As we all know, the C++14 discussion is flaring up again. Chandler brought up that he would like a concrete plan to switch. In my opinion, this is insufficient, as it will result in us simply having this discussion AGAIN next release. Instead, I would prefer us to have a concrete Policy on our host compilers. That way, changes like this are unsurprising to our users, and advance our

Hey, I have a situation where in I need to intercept a call to a particular function and return a pointer to a separate implementation of that function using JIT. The scenario is like this: 1. A test code or client code calls a function A() for which a dummy implementation is provided in a library which the test code/client links with during compilation. 2. I create the .bc using -emit-llvm and

This patch implements a local buffer reference type for kernel virtual address space and a remote buffer reference type for buffers up to 16 pages based on grant tables. These types are used by the USB driver for bulk data transfer. Signed-off-by: Harry Butterworth <butterwo@uk.ibm.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi all, We did some benchmarks on code size with clang, gcc 4.5, and open64. Clang performed second in the test. The benchmark is CSiBE. Clang can't compile the linux kernel (some inline asm not supported) and replaypc (error: use of unknown builtin '__builtin_next_arg'). The concrete results are attached. -------------- next part -------------- An HTML attachment was scrubbed... URL:

> > > Not sure about this last part. It is really going to require work by us to > rewrite things. :-) In the mean time, I think we should go ahead with this. > FWIW: My problem is, when put in this framework, we will repeatedly make this same decision, this same way, again and again, and never actually get even started on fixing it :) IE "it's just another small

> If there was a concrete need to move to a newer Python version in order to > make lit Python 3 compatible, I would view that as a good reason to move > forward. The concrete need is that users on platforms which ship with Python 3 by default have to put in a workaround (install python2 and patch their $PATH) just to run the test suite. Off the top of my head I know this includes Ubuntu

On Feb 28, 2011, at 9:47 AM, Andrew Clinton wrote: > This looks like a good extension to the type system. One thing that I > expected to work (when I first tried using opaque types) was for the > optimization passes and verification to operate correctly when using > opaque types, while the type could be made concrete later on - after > optimization. This turned out to be

On 07/14/2017 11:46 AM, Hal Finkel via llvm-dev wrote: > > > On 07/14/2017 01:38 PM, Daniel Berlin wrote: >> >> >> Not sure about this last part. It is really going to require work >> by us to rewrite things. :-) In the mean time, I think we should >> go ahead with this. >> >> >> FWIW: My problem is, when put in this framework,

Hi Jakub, On Tue, Jul 7, 2020 at 6:25 AM Jakub (Kuba) Kuderski <kubakuderski at gmail.com> wrote: > There's a lot of heavily templated code in generic DomTee construction/updater, MemSSA updater, and GraphDiff that has become really hard to modify. For the context, Alina (cc'd) was recently looking into making the domtree code work with 'CFG views'; the basic idea is to

On 9 June 2017 at 15:29, Jajoo, Malhar via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Thanks for that , I have read the documentation on this , but I would like to know > if it would be the right thing to do , ie , changing the enum within llvm::Type Well, I find the idea of a non-canonical DummyType slightly disturbing (I don't think it's something we'd ever support

I have been using SMS_fu but it seems too good to be true for production. I''m wondering, is there any sort of limit on email to sms depending on the carrier that you can send in a given amount of time? I remember reading somewhere that there is a limit to the number of free email to sms that you can send through AT&T in a given month. Does anyone know anything aobut this? I guess I

Hello sir, I'm having some problems understading how llvm works. I'm following a concrete example and visualizing the DAG and the .s output and some stuff doesn´t seem to match. I sorry to bother you but I don´t know where I can expose my doubts and I wonder if you could redirect me to some discussion place where someone might help me. Thanks, Patosga