Displaying 4 results from an estimated 4 matches for "bitcode_example".
2012 Nov 15
2
[LLVMdev] [RFC] Extend LLVM IR to express "fast-math" at a per-instruction level
...bitcode reader and writer. This patch references other local changes I have to other parts of the code (e.g. "FastMathFlags"), but shows the general idea I'm going for. When I've ironed out all the bugs, I'll attach a series of patches for all the other content.
>
> <bitcode_example.patch>
>
> Does this patch make sense, or am I still missing the main concern?
>
Michael,
Ah I see. So this just becomes a matter of interpretation of bits in the optimization flags. Shouldn't need to promote the CurVersion.
Nitpick: 80-cols in BitcodeReader.cpp
Since Instru...
2012 Nov 14
0
[LLVMdev] [RFC] Extend LLVM IR to express "fast-math" at a per-instruction level
...have to other parts of the code (e.g. "FastMathFlags"), but shows the general idea I'm going for. When I've ironed out all the bugs, I'll attach a series of patches for all the other content.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bitcode_example.patch
Type: application/octet-stream
Size: 2928 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121114/12a06609/attachment.obj>
-------------- next part --------------
Does this patch make sense, or am I still missing the main concern?
On Nov 14, 2012...
2012 Nov 14
4
[LLVMdev] [RFC] Extend LLVM IR to express "fast-math" at a per-instruction level
On Nov 14, 2012, at 12:47 PM, Chris Lattner <clattner at apple.com> wrote:
>
> On Nov 14, 2012, at 12:28 PM, Michael Ilseman <milseman at apple.com> wrote:
>
>> I think I missed what problem we're trying to solve here.
>>
>> I'm looking at implementing the bitcode now. I have code to successfully read and write out the LLVM IR textual formal
2012 Nov 15
0
[LLVMdev] [RFC] Extend LLVM IR to express "fast-math" at a per-instruction level
...reader and writer. This patch references other local changes I have to other parts of the code (e.g. "FastMathFlags"), but shows the general idea I'm going for. When I've ironed out all the bugs, I'll attach a series of patches for all the other content.
>>
>> <bitcode_example.patch>
>>
>> Does this patch make sense, or am I still missing the main concern?
>>
>
> Michael,
>
> Ah I see. So this just becomes a matter of interpretation of bits in the optimization flags. Shouldn't need to promote the CurVersion.
>
> Nitpick:...