weird issue with target intrinsics

I’m wondering if anyone has seen this issue before and if so, how was it fixed?

I have a file with multitude of target intrinsic in my code generator. It has worked great so far, but now I am running into this weird issue. If I add two new intrinsics such as:

def int_AMDIL_dummy_intr 1: GCCBuiltin<”__amdil_dummy_intr1”>,

Intrinsic<[], [llvm_ptr_ty]>;

def int_AMDIL_dummy_intr2 : GCCBuiltin<”__amdil_dummy_intr2”>,

Intrinsic<[], [llvm_ptr_ty]>;

Once I do this, I get an error that a completely unrelated intrinsic can no longer be selected. If I comment out these intrinsic, the other intrinsic is selected correctly.

Any ideas on how to debug this?

Thanks,

Micah

Hi Micah

def int_AMDIL_dummy_intr 1: GCCBuiltin<”__amdil_dummy_intr1”>,

is there really a space between "intr" and "1"?

Ciao, Duncan.

From: llvmdev-bounces@cs.uiuc.edu [mailto:llvmdev-bounces@cs.uiuc.edu]
On Behalf Of Duncan Sands
Sent: Thursday, April 14, 2011 12:37 AM
To: llvmdev@cs.uiuc.edu
Subject: Re: [LLVMdev] weird issue with target intrinsics

Hi Micah

> def int_AMDIL_dummy_intr 1: GCCBuiltin<"__amdil_dummy_intr1">,

is there really a space between "intr" and "1"?

[Villmow, Micah] No, that looks like a type on my part.