Displaying 6 results from an estimated 6 matches for "inst_".
Did you mean:
inst
2012 Oct 10
2
[LLVMdev] [PATCH / PROPOSAL] bitcode encoding that is ~15% smaller for large bitcode files...
Yes, I had about 133K hits for INST_PHI with a negative value, out of 136K
hits of any "INST_.*" with a negative valued operand.
Overall there were 474K INST_PHI and 12 million "INST_.*" in my tests.
- Jan
On Wed, Oct 10, 2012 at 11:23 AM, Rafael Espíndola <
rafael.espindola at gmail.com> wrote:
> Thi...
2012 Oct 10
0
[LLVMdev] [PATCH / PROPOSAL] bitcode encoding that is ~15% smaller for large bitcode files...
On 10 October 2012 15:15, Jan Voung <jvoung at chromium.org> wrote:
> Yes, I had about 133K hits for INST_PHI with a negative value, out of 136K
> hits of any "INST_.*" with a negative valued operand.
>
> Overall there were 474K INST_PHI and 12 million "INST_.*" in my tests.
Cool!
Thanks again for working on this!
> - Jan
Cheers,
Rafael
2012 Oct 08
2
[LLVMdev] [PATCH / PROPOSAL] bitcode encoding that is ~15% smaller for large bitcode files...
On Sat, Oct 6, 2012 at 8:32 AM, Rafael Espíndola <rafael.espindola at gmail.com
> wrote:
>
> +static void EmitSignedInt64(SmallVectorImpl<uint64_t> &Vals, uint64_t V) {
>
> Please start function names with a lower case letter.
>
>
Done -- changed this function and most of the "pushValue" functions. I
left PushValueAndType alone since that is an
2012 Oct 10
0
[LLVMdev] [PATCH / PROPOSAL] bitcode encoding that is ~15% smaller for large bitcode files...
This looks good to me.
Just one question, you found that forward references are only common
with phi operands, so it is not profitable to use a signed
representation for other operands, right?
Cheers,
Rafael
2012 Oct 11
2
[LLVMdev] [PATCH / PROPOSAL] bitcode encoding that is ~15% smaller for large bitcode files...
...ew Rafael!
Chris, did you want to take a look at the patch too?
Thanks,
- Jan
On Wed, Oct 10, 2012 at 12:39 PM, Rafael Espíndola <
rafael.espindola at gmail.com> wrote:
> On 10 October 2012 15:15, Jan Voung <jvoung at chromium.org> wrote:
> > Yes, I had about 133K hits for INST_PHI with a negative value, out of
> 136K
> > hits of any "INST_.*" with a negative valued operand.
> >
> > Overall there were 474K INST_PHI and 12 million "INST_.*" in my tests.
>
> Cool!
>
> Thanks again for working on this!
>
> > - Jan...
2013 May 28
2
hivex: revert much of " Build and test Perl bindings out-of-tree." (887466794a40f57b84ce32524e1a650d6674c7e6)?
...ould not get it
quite right:
- EU::MM expects Makefile.PL to be in the same directory as the generated
Makefile (We work around that using sed.)
- In principle, there seem to be two ways to do things:
1. Call make -f builddir/Makefile-pl from srcdir (that's what we do
now), override INST_*. Problems with this:
- XS is still built in srcdir.
- there is actually code in ExtUtils::Install which is used from the
generated Makefile-pl that bases its decisions where to install
*.pm files on whether there are any files within ./blib/arch/
(hard-coded)! I have...