2003-05-08 05:33:54 +02:00
|
|
|
//===-- llvm/Instrinsics.h - LLVM Intrinsic Function Handling ---*- C++ -*-===//
|
2005-04-21 22:19:05 +02:00
|
|
|
//
|
2003-10-20 22:19:47 +02:00
|
|
|
// The LLVM Compiler Infrastructure
|
|
|
|
//
|
|
|
|
// This file was developed by the LLVM research group and is distributed under
|
|
|
|
// the University of Illinois Open Source License. See LICENSE.TXT for details.
|
2005-04-21 22:19:05 +02:00
|
|
|
//
|
2003-10-20 22:19:47 +02:00
|
|
|
//===----------------------------------------------------------------------===//
|
2003-05-08 05:33:54 +02:00
|
|
|
//
|
|
|
|
// This file defines a set of enums which allow processing of intrinsic
|
|
|
|
// functions. Values of these enum types are returned by
|
|
|
|
// Function::getIntrinsicID.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
|
|
|
#ifndef LLVM_INTRINSICS_H
|
|
|
|
#define LLVM_INTRINSICS_H
|
|
|
|
|
2003-11-11 23:41:34 +01:00
|
|
|
namespace llvm {
|
|
|
|
|
|
|
|
/// Intrinsic Namespace - This namespace contains an enum with a value for
|
2003-06-03 17:30:13 +02:00
|
|
|
/// every intrinsic/builtin function known by LLVM. These enum values are
|
|
|
|
/// returned by Function::getIntrinsicID().
|
|
|
|
///
|
2003-11-11 23:41:34 +01:00
|
|
|
namespace Intrinsic {
|
2003-05-08 05:33:54 +02:00
|
|
|
enum ID {
|
|
|
|
not_intrinsic = 0, // Must be zero
|
2003-05-18 00:26:33 +02:00
|
|
|
|
2004-05-23 23:16:33 +02:00
|
|
|
// Varargs handling intrinsics.
|
2004-03-13 01:24:00 +01:00
|
|
|
vastart, // Used to implement the va_start macro in C
|
|
|
|
vaend, // Used to implement the va_end macro in C
|
|
|
|
vacopy, // Used to implement the va_copy macro in C
|
2003-05-18 00:26:33 +02:00
|
|
|
|
2004-05-23 23:16:33 +02:00
|
|
|
// Code generator intrinsics.
|
Add support for a cycle counter intrinsic. As basically all processors have
this and have it in about the same form, I think this makes sense.
on X86, you do a RDTSC (64bit result, from any ring since the P5MMX)
on Alpha, you do a RDCC
on PPC, there is a sequence which may or may not work depending on how things
are setup by the OS. Or something like that. Maybe someone who knows PPC
can add support. Something about the time base register.
on Sparc, you read %tick, which in some solaris versions (>=8) is readable by
userspace
on IA64 read ar.itc
So I think the ulong is justified since all of those are 64bit.
Support is slighly flaky on old chips (P5 and lower) and sometimes
depends on OS (PPC, Sparc). But for modern OS/Hardware (aka this decade),
we should be ok.
I am still not sure what to do about lowering. I can either see a lower to 0, to
gettimeofday (or the target os equivalent), or loudly complaining and refusing to
continue.
I am commiting an Alpha implementation. I will add the X86 implementation if I
have to (I have use of it in the near future), but if someone who knows that
backend (and the funky multi-register results) better wants to add it, it would
take them a lot less time ;)
TODO: better lowering and legalizing, and support more platforms
llvm-svn: 24299
2005-11-11 17:45:18 +01:00
|
|
|
returnaddress, // Yields the return address of a dynamic call frame
|
|
|
|
frameaddress, // Yields the frame address of a dynamic call frame
|
2006-01-13 03:15:02 +01:00
|
|
|
stacksave, // Save the stack pointer
|
|
|
|
stackrestore, // Restore the stack pointer
|
Add support for a cycle counter intrinsic. As basically all processors have
this and have it in about the same form, I think this makes sense.
on X86, you do a RDTSC (64bit result, from any ring since the P5MMX)
on Alpha, you do a RDCC
on PPC, there is a sequence which may or may not work depending on how things
are setup by the OS. Or something like that. Maybe someone who knows PPC
can add support. Something about the time base register.
on Sparc, you read %tick, which in some solaris versions (>=8) is readable by
userspace
on IA64 read ar.itc
So I think the ulong is justified since all of those are 64bit.
Support is slighly flaky on old chips (P5 and lower) and sometimes
depends on OS (PPC, Sparc). But for modern OS/Hardware (aka this decade),
we should be ok.
I am still not sure what to do about lowering. I can either see a lower to 0, to
gettimeofday (or the target os equivalent), or loudly complaining and refusing to
continue.
I am commiting an Alpha implementation. I will add the X86 implementation if I
have to (I have use of it in the near future), but if someone who knows that
backend (and the funky multi-register results) better wants to add it, it would
take them a lot less time ;)
TODO: better lowering and legalizing, and support more platforms
llvm-svn: 24299
2005-11-11 17:45:18 +01:00
|
|
|
prefetch, // Prefetch a value into the cache
|
|
|
|
pcmarker, // Export a PC from near the marker
|
|
|
|
readcyclecounter, // Read cycle counter register
|
2004-02-14 03:47:17 +01:00
|
|
|
|
2004-05-23 23:16:33 +02:00
|
|
|
// setjmp/longjmp intrinsics.
|
2003-07-28 23:18:21 +02:00
|
|
|
setjmp, // Used to represent a setjmp call in C
|
|
|
|
longjmp, // Used to represent a longjmp call in C
|
2003-08-18 17:41:24 +02:00
|
|
|
sigsetjmp, // Used to represent a sigsetjmp call in C
|
|
|
|
siglongjmp, // Used to represent a siglongjmp call in C
|
2003-07-28 23:18:21 +02:00
|
|
|
|
2004-05-23 23:16:33 +02:00
|
|
|
// Garbage Collection intrinsics.
|
|
|
|
gcroot, // Defines a new GC root on the stack
|
|
|
|
gcread, // Defines a read of a heap object (for read barriers)
|
|
|
|
gcwrite, // Defines a write to a heap object (for write barriers)
|
|
|
|
|
|
|
|
// Debugging intrinsics.
|
2004-01-05 06:35:34 +01:00
|
|
|
dbg_stoppoint, // Represents source lines and breakpointable places
|
|
|
|
dbg_region_start, // Start of a region
|
|
|
|
dbg_region_end, // End of a region
|
|
|
|
dbg_func_start, // Start of a function
|
2004-01-06 06:32:17 +01:00
|
|
|
dbg_declare, // Declare a local object
|
2004-01-05 06:35:34 +01:00
|
|
|
|
2004-02-12 18:57:11 +01:00
|
|
|
|
2004-05-23 23:16:33 +02:00
|
|
|
// Standard libc functions.
|
|
|
|
memcpy, // Copy non-overlapping memory blocks
|
|
|
|
memmove, // Copy potentially overlapping memory blocks
|
|
|
|
memset, // Fill memory with a byte value
|
|
|
|
|
2004-06-11 04:29:43 +02:00
|
|
|
// libm related functions.
|
2004-06-15 23:52:58 +02:00
|
|
|
isunordered, // Return true if either argument is a NaN
|
2005-05-03 19:19:30 +02:00
|
|
|
ctpop, //count population
|
|
|
|
ctlz, //count leading zeros
|
|
|
|
cttz, //count trailing zeros
|
|
|
|
sqrt, //square root
|
2004-02-12 18:57:11 +01:00
|
|
|
|
2004-05-23 23:16:33 +02:00
|
|
|
// Input/Output intrinsics.
|
2004-04-08 22:26:21 +02:00
|
|
|
readport,
|
|
|
|
writeport,
|
2004-04-14 04:22:54 +02:00
|
|
|
readio,
|
2004-10-29 20:43:43 +02:00
|
|
|
writeio
|
2005-05-03 19:19:30 +02:00
|
|
|
|
2003-05-08 05:33:54 +02:00
|
|
|
};
|
2003-11-11 23:41:34 +01:00
|
|
|
|
|
|
|
} // End Intrinsic namespace
|
|
|
|
|
|
|
|
} // End llvm namespace
|
2003-05-08 05:33:54 +02:00
|
|
|
|
|
|
|
#endif
|