Displaying 10 results from an estimated 10 matches for "insert_el".
2011 Oct 29
4
[LLVMdev] [llvm-commits] [PATCH] BasicBlock Autovectorization Pass
...; > > > registers
> > > > -bb-vectorize-no-ints -- Don't consider integer instructions
> > > > -bb-vectorize-no-floats -- Don't consider floating-point
> > > > instructions
> > > >
> > > > The vectorizor generates a lot of insert_element/extract_element
> > > > pairs;
> > > > The assumption is that other passes will turn these into shuffles
> > > > when
> > > > possible (it looks like some work is necessary here). It will
> > > > also
> > > > vectorize vec...
2011 Oct 29
0
[LLVMdev] [llvm-commits] [PATCH] BasicBlock Autovectorization Pass
...s
> > > > > -bb-vectorize-no-ints -- Don't consider integer instructions
> > > > > -bb-vectorize-no-floats -- Don't consider floating-point
> > > > > instructions
> > > > >
> > > > > The vectorizor generates a lot of insert_element/extract_element
> > > > > pairs;
> > > > > The assumption is that other passes will turn these into shuffles
> > > > > when
> > > > > possible (it looks like some work is necessary here). It will
> > > > > also
> >...
2006 Jul 23
7
"throwing out the old": does Rails really not support...
Frankly I''m losing tolerance for the MS "stack." And I''m intrigued by
Rails. But in my outfit I''m not only the web person, but also the
application person and the DBA. So when I read that Rails doesn''t want
to handle things like "compound keys" I blew right by those claims,
thinking, "no way."
But before I go deeper, I
2011 Oct 29
0
[LLVMdev] [llvm-commits] [PATCH] BasicBlock Autovectorization Pass
...-no-ints -- Don't consider integer instructions
> > > > > > > -bb-vectorize-no-floats -- Don't consider floating-point
> > > > > > > instructions
> > > > > > >
> > > > > > > The vectorizor generates a lot of insert_element/extract_element
> > > > > > > pairs;
> > > > > > > The assumption is that other passes will turn these into shuffles
> > > > > > > when
> > > > > > > possible (it looks like some work is necessary here). It wil...
2011 Oct 29
4
[LLVMdev] [llvm-commits] [PATCH] BasicBlock Autovectorization Pass
...; > -bb-vectorize-no-ints -- Don't consider integer instructions
> > > > > > -bb-vectorize-no-floats -- Don't consider floating-point
> > > > > > instructions
> > > > > >
> > > > > > The vectorizor generates a lot of insert_element/extract_element
> > > > > > pairs;
> > > > > > The assumption is that other passes will turn these into shuffles
> > > > > > when
> > > > > > possible (it looks like some work is necessary here). It will
> > > >...
2013 Apr 25
11
[LLVMdev] Proposal for new Legalization framework
In the spirit of the (long-term) intent to migrate away from the
SelectionDAG framework, it is desirable to implement legalization passes as
discrete passes. Attached is a patch which implements the beginning of a
new type legalization pass, to help motivate discussion.
Is LLVM IR the right level for this? The main alternative approach that's
been discussed is to do FastISel to a
2012 Jul 16
3
[LLVMdev] RFC: LLVM incubation, or requirements for committing new backends
...RegisterClass vec_class, int sub_idx,
> + SubRegIndex sub_reg>: Pat<
> + (sub_type (vector_extract (vec_type vec_class:$src), sub_idx)),
> + (EXTRACT_SUBREG vec_class:$src, sub_reg)
> +>;
> +
> +/* Insert element pattern */
> +class Insert_Element <ValueType elem_type, ValueType vec_type,
> + RegisterClass elem_class, RegisterClass vec_class,
> + int sub_idx, SubRegIndex sub_reg> : Pat <
> +
> + (vec_type (vector_insert (vec_type vec_class:$vec),
> +...
2009 Feb 13
44
[PATCH 0/40] ocfs2: Detach ocfs2 metadata I/O from struct inode
The following series of patches attempts to detach metadata I/O from
struct inode. They are currently tied together pretty tightly.
Metadata reads happen via the ocfs2_read_blocks() functions, writes via
both jbd2 and ocfs2_write_blocks().
- Each inode has a cache of associated metadata blocks stored on its
ip_metadata_cache member. The ocfs2_read/write_blocks() functions
take a struct
2009 Mar 27
42
[PATCH 00/42] ocfs2: Add reflink file support. V1
Hi all,
So I have finally finished the v1 of reflink for ocfs2. It has some
bugs that I am still investigating, but the schema is almost there. So
I'd like to send it out first for review. And Tristan and I will
continue to work on the stability of the code.
The general information for reflink, please see
http://oss.oracle.com/osswiki/OCFS2/DesignDocs/Reflink.
For the design doc, please
2009 Apr 03
42
[PATCH 00/42] ocfs2: Add reflink file support. V2
Hi all,
Change from v1 to v2: bug fix and metadata/credits reservation
improvement.
The general information for reflink, please see
http://oss.oracle.com/osswiki/OCFS2/DesignDocs/Reflink.
For the design doc, please see
http://oss.oracle.com/osswiki/OCFS2/DesignDocs/RefcountTrees
http://oss.oracle.com/osswiki/OCFS2/DesignDocs/ReflinkOperation