similar to: Interprocedural DSE for -ftrivial-auto-var-init

Displaying 20 results from an estimated 6000 matches similar to: "Interprocedural DSE for -ftrivial-auto-var-init"

2019 May 13
2
Interprocedural DSE for -ftrivial-auto-var-init
> On May 10, 2019, at 8:59 PM, Vitaly Buka via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Sorry for delay, I was busy with other stuff. > CTMark results. > > dse is the current DSE. > dsem is my experimental module level DSE. > dsem runs after dse, so it's additionally deleted stores. > > -O3 > dse - Number of stores deleted
2019 Apr 16
2
Interprocedural DSE for -ftrivial-auto-var-init
Can you post numbers for how many stores get eliminated from CTMark? > On Apr 16, 2019, at 11:45 AM, Vitaly Buka <vitalybuka at google.com> wrote: > > I tried -Os and effect of new approach significantly increases. > I run regular DSE and immediately myDSE. With -Os myDSE removes more than 50% of DSE number. > Which is expected as -Os inlines less and regular DSE can't
2019 Apr 16
2
Interprocedural DSE for -ftrivial-auto-var-init
On Mon, Apr 15, 2019 at 11:02 PM Amara Emerson via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > > On Apr 15, 2019, at 1:51 PM, Vitaly Buka via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > > Hi JF, > > > > I've heard that you are interested DSE improvements and maybe we need to be in sync. > > So far I experimented with
2019 Aug 07
2
Dead store elimination in the backend for -ftrivial-auto-var-init
There are two problems: 1. padding after union and call to q(), without LTO we can't remove that store. 2. shortcut which I have which ignores all instructions q() . this assume that memset to acpar.match, acpar.matchinfo also useful which is not true. I should be able to improve this case. On Thu, Aug 1, 2019 at 11:29 PM Vitaly Buka <vitalybuka at google.com> wrote: > On a first
2019 Aug 01
2
Dead store elimination in the backend for -ftrivial-auto-var-init
On Thu, Aug 1, 2019 at 6:38 PM JF Bastien <jfbastien at apple.com> wrote: > > > > > On Aug 1, 2019, at 9:20 AM, Alexander Potapenko <glider at google.com> wrote: > > > > On Thu, Aug 1, 2019 at 6:09 PM JF Bastien <jfbastien at apple.com> wrote: > >> > >> Hi Alexander, > >> > >> The code doesn’t compile. Could you send
2019 Aug 01
2
Dead store elimination in the backend for -ftrivial-auto-var-init
On Thu, Aug 1, 2019 at 6:09 PM JF Bastien <jfbastien at apple.com> wrote: > > Hi Alexander, > > The code doesn’t compile. Could you send a godbolt.org link that shows the issue? Sorry about that, here's the link: https://godbolt.org/z/-PinQP Lines 4 to 8 are initializing |acpar|. If I'm understanding correctly, the store to 8(%rsp) at line 7 can be removed because of the
2019 Aug 01
2
Dead store elimination in the backend for -ftrivial-auto-var-init
Hi folks, When compiling the attached example with -ftrivial-auto-var-init=zero: $ clang -no-integrated-as -mno-sse -m64 -mstack-alignment=8 -O2 -ftrivial-auto-var-init=zero -enable-trivial-auto-var-init-zero-knowing-it-will-be-removed-from-clang -g -o ipt.ll -c ipt.i -w -S -emit-llvm , Clang generates an initialization memset() call for |acpar| in the IR: %0 = bitcast
2016 Sep 23
2
Commit zlib source code into to llvm repo
Yes, zlib build for LTO will work, but user will have to build this lib from zlib source code anyway. On Fri, Sep 23, 2016 at 4:01 PM Mehdi Amini <mehdi.amini at apple.com> wrote: > > On Sep 23, 2016, at 1:44 PM, Vitaly Buka via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > Hi all, > > Is it possible to add zlib source code into llvm repo? Any advice on how
2001 Jul 12
2
Package DSE
Hi, If I try to do this: if(is.R()) data("eg1.DSE.data.diff", package="dse1") model <- est.VARX.ls(eg1.DSE.data.diff) (Page 14 - DSE Package Manual) I obtain a Segment Violation. I use R-1.3.0 and the last dse package version Maximino Ameneiro Gomez -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read
2016 Sep 23
4
Commit zlib source code into to llvm repo
Hi all, Is it possible to add zlib source code into llvm repo? Any advice on how to do so? I'd like to setup build of symbolizer as a static library with no external dependencies except libc. Similar to https://github.com/google/sanitizers/blob/master/address-sanitizer/internal_symbolizer/howto . Then the library can be linked into sanitized program and avoid dependency on standalone
2005 Dec 23
1
dse package problems
I am having problems with the package dse. I just installed R 2.2.1 and reinstalled all packages. I am running Windows XP Pro with all updates. Below there are two examples of error messages generated when trying to execute some simple programs. The code was taken directly from the package documentation. Any help on this will be greatly appreciated. Merry Christmas Fernando
2018 May 21
0
DSE: Remove useless stores between malloc & memset
"memory accesses between the malloc and the memset without an expensive linear scan of the block/function" (1) do you mean just use "memoryIsNotModifiedBetween" function in DSE to check it? x = maloc(..); memset(x, ...) (2) GetUnderlyingObject would give me Value * (from malloc) ? Also another case: memset(s, 0, len); // len > 1 return strlen(s); // optimize to 0 (3)
2003 Apr 23
1
Bug in versioned install (was: (fwd) R-1.7.0 : Problem with Downloading "dse") (PR#2827)
The reason dse won't install is because of the new versioned install code. It assumes that it's dealing with a plain package, and doesn't handle bundles properly. Robert, could you look at that? A workaround is as follows. After the install.packages call fails with this message >Error in file(file, "r") : unable to open connection >In addition: Warning message:
1998 Feb 25
1
R-beta: Re: dse+redhat 4.2 problem
>R INSTALL dse rlibs >Installing package `dse' ... >libs >gcc -g -fpic -I/usr/local/R-0.61/include -c dsefor.c -o dsefor.o >/tmp/cca02533.i:1: numeric constant with no digits >/tmp/cca02533.i:1: numeric constant with no digits >... >is there something wrong with my gcc or is there some >option missing somewhere? >I suspect the problem might have to do with
1998 Feb 25
1
R-beta: Re: dse+redhat 4.2 problem
>R INSTALL dse rlibs >Installing package `dse' ... >libs >gcc -g -fpic -I/usr/local/R-0.61/include -c dsefor.c -o dsefor.o >/tmp/cca02533.i:1: numeric constant with no digits >/tmp/cca02533.i:1: numeric constant with no digits >... >is there something wrong with my gcc or is there some >option missing somewhere? >I suspect the problem might have to do with
2003 Jun 10
1
Fwd: dse package - load failure
Hello, Sorry a second time again, Maybe I have to add that I'm running R under Windows 2000/XP, and that the download works properly under 1.062 but not under 1.070. Diethelm >Date: Tue, 10 Jun 2003 19:25:33 +0200 >To: r-devel@stat.math.ethz.ch >From: Diethelm Wuertz <wuertz@itp.phys.ethz.ch> >Subject: dse package - load failure >Cc: pgilbert@bank-banque-canada.ca
2018 May 22
0
DSE: Remove useless stores between malloc & memset
Can you help a bit? I try to work with DSE but I got the following assert: opt: /home/xbolva00/LLVM/llvm/include/llvm/ADT/Optional.h:176: T* llvm::Optional<T>::getPointer() [with T = llvm::MemoryLocation]: Assertion `Storage.hasVal' failed. static bool eliminateStrlen(CallInst *CI, BasicBlock::iterator &BBI, AliasAnalysis *AA, MemoryDependenceResults
1999 Dec 21
1
DSE revised for R 0.90.1
A slightly revised version of my DSE package for multi-variate time series analysis is now available at <www.bank-banque-canada.ca/pgilbert>. This version works with R 0.90.1 (and not with R 90.0 or earlier versions). It can also be installed with install.packages(c("syskern", "tframe", "dse"),
1999 Dec 21
1
DSE revised for R 0.90.1
A slightly revised version of my DSE package for multi-variate time series analysis is now available at <www.bank-banque-canada.ca/pgilbert>. This version works with R 0.90.1 (and not with R 90.0 or earlier versions). It can also be installed with install.packages(c("syskern", "tframe", "dse"),
2018 May 21
2
DSE: Remove useless stores between malloc & memset
memoryIsNotModifiedBetween is precisely the sort of expensive walk we shouldn't be doing... I'm surprised it hasn't caused any serious issues yet.  Ideally, what we should be doing is using MemorySSA to find a dependency from the memset: if the closest dependency is the malloc, there aren't any stores between the memset and the malloc.  (But we aren't using MemorySSA in