Displaying 4 results from an estimated 4 matches for "getmemlevel".
2011 Feb 23
2
[LLVMdev] CodeGenOpt
...ry hierarchy optimization.
I would like to replace the existing CodeGenOpt::Level enum with a more
general CodeGenOpt class that can track different sets of optimization
level. Initially it would look something like this:
class CodeGenOpt {
...
public
getOptLevel() ...;
getFPLevel() ...;
getMemLevel() ...;
};
Does this sound reasonable?
-Dave
2011 Feb 24
0
[LLVMdev] CodeGenOpt
...to replace the existing CodeGenOpt::Level enum with a more
> general CodeGenOpt class that can track different sets of optimization
> level. Initially it would look something like this:
>
> class CodeGenOpt {
> ...
> public
> getOptLevel() ...;
> getFPLevel() ...;
> getMemLevel() ...;
> };
>
> Does this sound reasonable?
I don't think that this is the right way to go. Higher level decisions like that should affect your choice of passes to schedule.
-Chris
2011 Feb 24
2
[LLVMdev] CodeGenOpt
Chris Lattner <clattner at apple.com> writes:
>> class CodeGenOpt {
>> ...
>> public
>> getOptLevel() ...;
>> getFPLevel() ...;
>> getMemLevel() ...;
>> };
>>
>> Does this sound reasonable?
>
> I don't think that this is the right way to go. Higher level
> decisions like that should affect your choice of passes to schedule.
But there's no way to do that at the codegen level. LLVMTargetMachine
keys of...
2011 Feb 24
0
[LLVMdev] CodeGenOpt
On Feb 24, 2011, at 8:14 AM, David A. Greene wrote:
> Chris Lattner <clattner at apple.com> writes:
>
>>> class CodeGenOpt {
>>> ...
>>> public
>>> getOptLevel() ...;
>>> getFPLevel() ...;
>>> getMemLevel() ...;
>>> };
>>>
>>> Does this sound reasonable?
>>
>> I don't think that this is the right way to go. Higher level
>> decisions like that should affect your choice of passes to schedule.
>
> But there's no way to do that at the codege...