Displaying 4 results from an estimated 4 matches for "hasfpuopt".
2010 Jan 30
3
[LLVMdev] [patch] MicroBlaze Backend
...]>;
>+def : Proc<"v710", []>;
What's the difference between them then? isVN00() predicates are not used.
>+ DataLayout(std::string("E-p:32:32-i8:8:8-i16:16:16-n32")),
I'm confused. What are the native types for this arch?
>+static cl::opt<bool> HasFPUOpt(
>+ "mb-has-fpu",
As Jakob already said - remove these, you should use subtarget
features (-mattr=+foo) instead.
As I understand, some features are not hooked yet, like
>+def FeaturePipe3 : SubtargetFeature<"pipe3", "HasPipe3", "true",
>...
2010 Jan 30
0
[LLVMdev] [patch] MicroBlaze Backend
On Jan 29, 2010, at 9:42 AM, Wesley Peck wrote:
> I have been working on a LLVM backend for the MicroBlaze soft-processor:
> http://www.xilinx.com/tools/microblaze.htm
> http://en.wikipedia.org/wiki/MicroBlaze
Very Cool!
> Attached is the initial MicroBlaze patch. It does the following:
> 1. Adds mblaze as a target in configure and configure.ac
> 2. Adds mblaze specific
2010 Jan 30
0
[LLVMdev] [patch] MicroBlaze Backend
...;> + DataLayout(std::string("E-p:32:32-i8:8:8-i16:16:16-n32")),
> I'm confused. What are the native types for this arch?
The microblaze has only 32-bit registers. Should this be "E-p:32:32:32-i8:8:32-i16:16:32-n32" instead?
>
>> +static cl::opt<bool> HasFPUOpt(
>> + "mb-has-fpu",
> As Jakob already said - remove these, you should use subtarget
> features (-mattr=+foo) instead.
Done.
>
> As I understand, some features are not hooked yet, like
>> +def FeaturePipe3 : SubtargetFeature<"pipe3", "...
2010 Jan 29
3
[LLVMdev] [patch] MicroBlaze Backend
I have been working on a LLVM backend for the MicroBlaze soft-processor:
http://www.xilinx.com/tools/microblaze.htm
http://en.wikipedia.org/wiki/MicroBlaze
Attached is the initial MicroBlaze patch. It does the following:
1. Adds mblaze as a target in configure and configure.ac
2. Adds mblaze specific intrinsics in include/llvm/IntrinsicsMBlaze.td and include/llvm/Intrinsics.td
3. Adds mblaze