similar to: [LLVMdev] Instruction lowering pass

Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] Instruction lowering pass"

2006 May 03
1
[LLVMdev] Patch for transform dependencies
Hi, A number of transforms are actually independent, so here's a partial fix. I updated the dependencies in a cluster of transforms: LowerSwitch, Mem2Reg, LowerSelect, LowerAllocations, UnifyFunctionExitNodes. The patch has been tested, but not extensively. PassManager doesn't complain, and the result of a test pass that requires all these (except for LowerAllocations) together works
2016 Dec 13
1
Lowering the metadata attached to an instruction down to Pattern Instruction Selection pass
Hello devlopers, I request your guidance on how to lower the metadata attached with an instruction. Following is given the IR dump before Module verifier pass, and there is a string "Tile3" attached as metadata with instruction "%x = alloca i32, align 4, !Tile3 !1". My target is to transmit/propagate the string down to post RA-Scheduling pass. Is it possible? If yes, how
2016 May 27
0
[LLVM LTO]internalize pass
> On May 27, 2016, at 9:57 AM, Duncan P. N. Exon Smith via llvm-dev <llvm-dev at lists.llvm.org> wrote: > >> >> On 2016-May-27, at 05:55, Teresa Johnson via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> >> >> On Fri, May 27, 2016 at 3:43 AM, Umesh Kalappa via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> Hi All ,
2009 Aug 08
2
[LLVMdev] Initial cut at a instruction raising patch
Chris Lattner wrote: > On Aug 8, 2009, at 8:37 AM, Richard Pennington wrote: > >> Hi, >> >> This patch raises selected instructions to function calls. I've dome >> some preliminary testing and I works: > > Out of curiosity, why do you want this? > I do bitcode linking of a whole program, including the soft-float and other support routines that a
2016 May 27
1
[LLVM LTO]internalize pass
> On 2016-May-27, at 10:47, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> >> On May 27, 2016, at 9:57 AM, Duncan P. N. Exon Smith via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >>> >>> On 2016-May-27, at 05:55, Teresa Johnson via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> >>> >>>
2016 May 27
2
[LLVM LTO]internalize pass
> On 2016-May-27, at 05:55, Teresa Johnson via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > > On Fri, May 27, 2016 at 3:43 AM, Umesh Kalappa via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Hi All , > > We are in process of exploring the LTO and found that internalize > pass is the replacement for whole program optimisation > (-fwhole-program
2007 Sep 30
1
[LLVMdev] noinline
Hi, I was interested in telling the compiler not to inline a given function, and discovered that the __attribute__((noinline)) implements this using a global variable @llvm.noinline. It did not work for me initially. I noticed that @ llvm.noinline was being internalized by -internalize, dead-code-eliminated by -constmerge, causing this information not to reach the -inline pass. I am not sure if
2006 Aug 01
0
Unobtrusive Javascript for Rails 0.2
Dan Webb (http://www.vivabit.com) and I are happy to announce the latest release of the Unobtrusive Javascript plugin for Rails. This release packs in lots of cool new features, a few changes to old ones and some performance enhancements. Now you can write your behaviours in Ruby, attach behaviours directly to elements using content_tag and apply behaviours to elements without HTML IDs.
2004 Jun 25
0
[LLVMdev] ConstantExpr lowering pass for code generators
Following up on the '[LLVMdev] Getelementptr woes' thread: http://mail.cs.uiuc.edu/pipermail/llvmdev/2004-June/001252.html I'm happy to say that Vladimir Prus contributed a constant expression lowering pass for instruction selectors to use. This pass makes instruction selection both easier and less error prone. Thanks Vladimir, and sorry for being such a butthead about it earlier on
2006 Jun 05
1
Unobtrusive javascript...what if?
What if...you could produce accessible, unobtrusive javascript, using Rails built-in javascript/prototype helpers, with just one extra line of code in your layout, a plugin, and one small enhancement to the helpers. Something like this: [php] <% form_remote_tag :controller => ''foo'', :action => ''bar'', :unobtrusive => true %> # which produces
2016 May 27
0
[LLVM LTO]internalize pass
On Fri, May 27, 2016 at 3:43 AM, Umesh Kalappa via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi All , > > We are in process of exploring the LTO and found that internalize > pass is the replacement for whole program optimisation > (-fwhole-program in gcc) in clang and in the below case > > define i32 @test() #0 { > > entry: > > ret i32 0 >
2009 Feb 19
2
[LLVMdev] -fPIC warning on every compile on Cygwin
On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Aaron Gray wrote: > > On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca > > <mailto:nicholas at mxc.ca>> wrote: > > > > Aaron Gray wrote: > > > Hi, > > > > > > I partly built LLVM on Cygwin yesterday and it was fine
2009 Feb 21
0
[LLVMdev] -fPIC warning on every compile on Cygwin
Aaron Gray wrote: > On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Aaron Gray wrote: > > On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca> > > <mailto:nicholas at mxc.ca <mailto:nicholas at mxc.ca>>> wrote:
2009 Feb 19
0
[LLVMdev] -fPIC warning on every compile on Cygwin
Aaron Gray wrote: > On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Aaron Gray wrote: > > Hi, > > > > I partly built LLVM on Cygwin yesterday and it was fine as far as it > > went. But after doing a svn update today I am getting the following > > warning
2009 Aug 08
0
[LLVMdev] Initial cut at a instruction raising patch
On Aug 8, 2009, at 11:48 AM, Richard Pennington wrote: > Chris Lattner wrote: >> On Aug 8, 2009, at 8:37 AM, Richard Pennington wrote: >> >>> Hi, >>> >>> This patch raises selected instructions to function calls. I've dome >>> some preliminary testing and I works: >> >> Out of curiosity, why do you want this? >> > > I
2016 Jun 22
2
x86: How to Force 2-byte `jmp` instruction in lowering
I have a bit of a riddle: In http://reviews.llvm.org/D19904 I'm trying to spell the following assembly: .palign 2, 0x90 jmp +0x9 nopw 512(%rax,%rax,1) // rest of the code I try the following snippet to accomplish this: OutStreamer->EmitLabel(CurSled); OutStreamer->EmitCodeAlignment(4); auto Target = OutContext.createLinkerPrivateTempSymbol(); // Use a two-byte `jmp`.
2006 May 01
0
[LLVMdev] Regarding exceptions (new to this list)
On Sun, 30 Apr 2006, Aristid Breitkreuz wrote: > I am, as said in the subject, new to this list. I have not actually used > LLVM, I tried with an older version but failed. Recently I noticed that > 1.7 came out and looked at the release notes. And there was something > that stroke me: llvm-g++ adheres to the IA64 ABI but _not for > exceptions_. I was not able to find information why
2010 Dec 20
2
The Rails3 way for in-place editing
Currently I want to implement in-place editing directly on the index-page (for the sake of learning just xx products with a name to be edited). These are my favorite links from yesterday''s research (for the archives): *On the spot is a Rails3 compliant unobtrusive javascript in-place-editing plugin: http://rubygems.org/gems/on_the_spot
2009 Feb 25
3
[LLVMdev] -fPIC warning on every compile on Cygwin
On Sat, Feb 21, 2009 at 7:14 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Aaron Gray wrote: > > On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca > > <mailto:nicholas at mxc.ca>> wrote: > > > > Aaron Gray wrote: > > > On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca > >
2009 Feb 27
0
[LLVMdev] -fPIC warning on every compile on Cygwin
Aaron Gray wrote: > On Sat, Feb 21, 2009 at 7:14 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Aaron Gray wrote: > > On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca> > > <mailto:nicholas at mxc.ca <mailto:nicholas at mxc.ca>>> wrote: