similar to: [debug support] Why do constant SD nodes not set the IROrder?

Specifically I would like to understand why ConstantSDNode and ConstantFPSDNode do not set the IR ordering like most other SDNode-s. These constant SD nodes also previously did not set the debugloc, but that got enabled (here: http://llvm.org/viewvc/llvm-project?view=revision&revision=237237). These constant SD nodes hard-code the order to 0. Is this intentional, or just something that has

I'm trying to match a ConstantFPSDNode == 0 in dag pattern for tablegen but am having some issues. So LLVM doesn't seem to accept a floating point constant literal match like: %v = call <4 x float> @foo(i32 15, float %s, float 0.0, <8 x i32> %rsrc, <4 x i32> %samp, i1 0, i32 0, i32 0) ret <4 x float> %v def : XXXPat<(v4f32 (int_foo i32:$mask, f32:$s, 0,

Hi All, I'm trying to compile the attached code(gdb11531.c) with latest clang with -O0 on ARM. Clang seems to be reordering the instructions in case of constant nodes(for ARM) even when O0 is specified resulting in few wrong information when debugging through GDB. I had few queries,would be great if someone could clarify the same - In the given assembly code, the instructions where constant

The Identifiers section in the LLVM language manual states: "The "\01" prefix can be used on global variables to suppress mangling." Is this for global variables only, or global values in general, such as functions also? In implementation LLVM seems to have this behavior of suppressing mangling even for functions and aliases. Thanks, Gautam

On Tue, Apr 30, 2013 at 12:48 AM, Guo, Xiaoyi <Xiaoyi.Guo at amd.com> wrote: > Hi,**** > > ** ** > > We’ve recently encountered a problem in our compiler where the line number > in debug info jumps back and force even at O0. This is caused by DAG node > ordering not being properly kept during legalization and instruction > selection. There are still uncaught cases

On Apr 30, 2013, at 11:00 AM, "Guo, Xiaoyi" <Xiaoyi.Guo at amd.com> wrote: > Hi Eric, > > Sorry I wasn’t clear. The problem happened in the “source” pre-RA scheduler, which relies on DAG node ordering to schedule the nodes. In your case, Eric's suggestion was effectively "start implementing fast-isel". Which is not a bad idea if you want to reduce compile

Gautam Sewani wrote: > On Fri, Mar 13, 2009 at 2:38 PM, Duncan Sands <baldrick at free.fr> wrote: > >> Hi, the versions of llvm-gcc and llvm you are using are >> not synchronized. Probably one is from subversion while >> the other is not. >> I've run into this, too. The problem is that the inliner pass uses a 30 bit integer to store the inline

On Fri, Mar 13, 2009 at 2:38 PM, Duncan Sands <baldrick at free.fr> wrote: > Hi, the versions of llvm-gcc and llvm you are using are > not synchronized. Probably one is from subversion while > the other is not. > > Ciao, > > Duncan. > Ok, I 'synchronized' both of them, but now I am getting a different error. On running make, the output ends with the

Hi, Regarding my gsoc proposal (xen in a box), I have developed a set of scripts to create a custom CentOS ISO which delivers Xen 4.4 stack on CentOS 6.6 with libvirt and fully bridge network settings. I have used xen scripts for networking settings. Waiting for feedback. scripts: https://github.com/gautammaloo/centos-xen proposal:

Hi Eric, Sorry I wasn't clear. The problem happened in the "source" pre-RA scheduler, which relies on DAG node ordering to schedule the nodes. Xiaoyi From: Eric Christopher [mailto:echristo at gmail.com] Sent: Tuesday, April 30, 2013 12:54 AM To: Guo, Xiaoyi Cc: LLVM Developers Mailing List Subject: Re: [LLVMdev] [PATCH] Propagate DAG node ordering during legalization and

Hi, We've recently encountered a problem in our compiler where the line number in debug info jumps back and force even at O0. This is caused by DAG node ordering not being properly kept during legalization and instruction selection. There are still uncaught cases after applying the patch mentioned here. So I have decided to implement the approach suggested by Andy as below. i.e. maintain the

Thanks Jon, it worked, I was able to build all the packages for xenserver on CentOS 6.6 final version. Here is the package list: https://gist.github.com/gautammaloo/7616cccbe8f5c85c196e I was wondering what packages would be necessary to use Xen with xapi, I already have xen with xl installed. Could we have a package like http://packages.ubuntu.com/precise/xcp-xe with which we can have

Hello All, the patch below adds a target lowering hook to state that the target supports (or not) floating point exception behavior. The patch is small and contains one possible use for the hook (folding potentially exception raising fp operations). Any comments? Thanks Pedro -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: opensource1.txt

I assume you meant to ask for ports that *don’t* support floating point exceptions. To my knowledge, neither R600 nor NVPTX support floating point exceptions. —Owen > On Aug 8, 2014, at 2:41 PM, Eric Christopher <echristo at gmail.com> wrote: > > There's a lot of cut and paste in those routines. Can you do something > to unify it a bit? Also, do we have any ports that

On Mar 13, 2009, at 10:45 PM, Gautam Sewani wrote: > On Fri, Mar 13, 2009 at 8:09 PM, John Criswell > <criswell at cs.uiuc.edu> wrote: >> Gautam Sewani wrote: >>> On Fri, Mar 13, 2009 at 2:38 PM, Duncan Sands <baldrick at free.fr> >>> wrote: >>> >>>> Hi, the versions of llvm-gcc and llvm you are using are >>>> not

On Sun, Mar 22, 2015 at 1:08 AM, Gautam Malu <gautam.malu at research.iiit.ac.in> wrote: > Hi, > > I am Masters student at IIIT Hyderabad, India. I have made a set of scripts > to make a customized installer ISO which installs Xen4.4 + CentOS 6.6. I > have tested it on a Xen HVM VM. I would be great if anyone can test it out. > > https://github.com/gautammaloo/centos-xen

Hi, I would like to add a new directive to FileCheck called CHECK-FOO (where FOO is a name under discussion right now) which is used to improve error messages. The idea is that you would use CHECK-FOO on any line that contains a unique identifier (typically labels, function definitions, etc.) that is guaranteed to only occur once in the file; FileCheck will then conceptually break the break the

This code lives in DAGCombiner.cpp: ------------- // Turn 'store float 1.0, Ptr' -> 'store int 0x12345678, Ptr' if (ConstantFPSDNode *CFP = dyn_cast<ConstantFPSDNode>(Value)) { // NOTE: If the original store is volatile, this transform must not increase // the number of stores. For example, on x86-32 an f64 can be stored in one // processor operation but

dear experts, i am a novice and have been trying to use the anderson-darling test on a simple text file with one column of data. i have followed the example in the manual to read from a file into a vector(mm). i am able to see the summary stats with >summary(mm) however, when i try to use the ad.test package, it keeps coming up with the following error messages, > ad.test(mm) Error in

On Fri, Mar 13, 2009 at 8:09 PM, John Criswell <criswell at cs.uiuc.edu> wrote: > Gautam Sewani wrote: >> On Fri, Mar 13, 2009 at 2:38 PM, Duncan Sands <baldrick at free.fr> wrote: >> >>> Hi, the versions of llvm-gcc and llvm you are using are >>> not synchronized. Probably one is from subversion while >>> the other is not. >>> >