similar to: [LLVMdev] determining if the signness of a integer pointer

On 13 May 2010 05:28, Villmow, Micah <Micah.Villmow at amd.com> wrote: > Is there a way to determine via API calls whether a pointer to an int points > to a signed integer or an unsigned integer? > Since LLVM doesn't have signed or unsigned integer types, I'm not sure what you're asking. I suppose you could look for additions done with values loaded from or stored to

Since the frontend knows that a int pointer is signed or unsigned, I was hoping that this bit was set somewhere in a header file that I couldn't find when it was creating the LLVM integer. Micah -----Original Message----- From: me22 [mailto:me22.ca at gmail.com] Sent: Wednesday, May 12, 2010 8:46 PM To: Villmow, Micah Cc: LLVM Developers Mailing List Subject: Re: [LLVMdev] determining if the

I am attemping to figure out how to access the function names that are stored in a module so that I know which function I am currently in. I am attempting to write a backend that targets a language that only allows integer function names and I need to create mapping between the string and the integer. I've looked in the header files but I cannot determine how to extract the function

How do I determine what type of register(i.e. i32, f32, etc..) I am accessing from a MachineOperand? I.e. how do I get to the MVT struct, or equivalent information, from a MachineOperand object? Micah Villmow Systems Engineer Advanced Technology & Performance Advanced Micro Devices Inc. 4555 Great America Pkwy, Santa Clara, CA. 95054 P: 408-572-6219 F: 408-572-6596

A Function is a Value. See Value.h, look for getName(), etc. Evan On Sep 10, 2008, at 12:18 PM, Villmow, Micah wrote: > I am attemping to figure out how to access the function names that > are stored in a > module so that I know which function I am currently in. I am > attempting to write a > backend that targets a language that only allows integer function > names and I

You can get to the MachineInstr from a MachineOperand. Then get to its TargetInstrDesc and TargetOperandInfo which has register class information. Evan On Sep 23, 2008, at 12:44 PM, Villmow, Micah wrote: > How do I determine what type of register(i.e. i32, f32, etc..) I am > accessing from a MachineOperand? I.e. how do I get to the MVT > struct, or equivalent information, from

Are there any known inheritance graphs of all the classes? That definitely would help in trying to understand the interactions between everything. Micah ________________________________ From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Evan Cheng Sent: Wednesday, September 10, 2008 10:32 PM To: LLVM Developers Mailing List Subject: Re: [LLVMdev]

This only has the register class information, not the register type information. My register class has multiple register types and I need to know how to differentiate which register type of my register class of the current register. The information in the MVT data type is what I need, i.e. the position in the GPRVT array of each register. Something equivalent to MVT getValueType() but for

What does nsw nuw do? Micah -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Dan Gohman Sent: Tuesday, October 13, 2009 10:06 AM To: Jeffrey Yasskin Cc: LLVM Developers Mailing List Subject: Re: [LLVMdev] 65bit integer math On Oct 12, 2009, at 9:42 PM, Jeffrey Yasskin wrote: > On Mon, Oct 12, 2009 at 8:22 PM, Eli Friedman

I am running into an issue where if I have multiple functions compiled in the same compilation unit the stack offset is not starting at zero. For example: func1(...) { ... } func2(...) { ... } Say the first function uses 64 bytes of the stack and an assumed offset of 0 and the second function uses 32 bytes of the stack but an assumed offset of 64. I've found out how to get the

LGTM for this bit. On Oct 25, 2012 7:52 AM, "Villmow, Micah" <Micah.Villmow at amd.com> wrote: > Here is my patch for it: > Index: ReleaseNotes.html > =================================================================== > --- ReleaseNotes.html (revision 166627) > +++ ReleaseNotes.html (working copy) > @@ -669,6 +669,9 @@ > "TargetTransformInfo"

On Mon, Oct 12, 2009 at 8:22 PM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Mon, Oct 12, 2009 at 6:15 PM, Villmow, Micah <Micah.Villmow at amd.com> wrote: >> I have a test case(attached as fc_long.ll) that when run through the >> optimizer produces 65bit integer math(fc_long-opt.ll). >> >> >> >> Now I understand that llvm can have any

On Oct 12, 2009, at 9:42 PM, Jeffrey Yasskin wrote: > On Mon, Oct 12, 2009 at 8:22 PM, Eli Friedman > <eli.friedman at gmail.com> wrote: >> On Mon, Oct 12, 2009 at 6:15 PM, Villmow, Micah <Micah.Villmow at amd.com >> > wrote: >>> I have a test case(attached as fc_long.ll) that when run through the >>> optimizer produces 65bit integer

On Nov 19, 2013, at 10:52, Micah Villmow <micah.villmow at smachines.com> wrote: > +llvm-dev > Yes. The question then becomes, does LLVM handle the case where the cast of the value 0 to a non-void* pointer? > > Think of this case: > int *ptr = (int*)0; > > based on a strict reading of the spec, ptr itself technically is not the null pointer constant. Not true, the

Here is my patch for it: Index: ReleaseNotes.html =================================================================== --- ReleaseNotes.html (revision 166627) +++ ReleaseNotes.html (working copy) @@ -669,6 +669,9 @@ "TargetTransformInfo" provides a number of low-level interfaces. LSR and LowerInvoke already use the new interface. </p> +<p> The TargetData structure

+llvm-dev Yes. The question then becomes, does LLVM handle the case where the cast of the value 0 to a non-void* pointer? Think of this case: int *ptr = (int*)0; based on a strict reading of the spec, ptr itself technically is not the null pointer constant. If ptr points to an object in the local address space in OpenCL, or any address space where 0 is a valid address and memory exists, does

> -----Original Message----- > From: Eli Friedman [mailto:eli.friedman at gmail.com] > Sent: Wednesday, September 12, 2012 3:50 PM > To: Villmow, Micah > Cc: Richard Smith; cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu > Subject: Re: [cfe-dev] [LLVMdev] SPIR Portability Discussion > > On Wed, Sep 12, 2012 at 3:40 PM, Villmow, Micah <Micah.Villmow at amd.com> >

From: metafoo at gmail.com [mailto:metafoo at gmail.com] On Behalf Of Richard Smith Sent: Wednesday, September 12, 2012 3:30 PM To: Villmow, Micah Cc: Eli Friedman; cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu Subject: Re: [cfe-dev] [LLVMdev] SPIR Portability Discussion On Wed, Sep 12, 2012 at 3:26 PM, Villmow, Micah <Micah.Villmow at amd.com<mailto:Micah.Villmow at amd.com>> wrote:

Micah, can you document this in the release notes? On Wed, Oct 24, 2012 at 4:34 PM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Wed, Oct 24, 2012 at 4:11 PM, Ryan Taylor <ryta1203 at gmail.com> wrote: >> Has this been removed/replaced? Couldn't find anything in the release notes. > > Renamed DataLayout. > > -Eli >

On Wed, Sep 12, 2012 at 4:02 PM, Villmow, Micah <Micah.Villmow at amd.com> wrote: > > >> -----Original Message----- >> From: Eli Friedman [mailto:eli.friedman at gmail.com] >> Sent: Wednesday, September 12, 2012 3:50 PM >> To: Villmow, Micah >> Cc: Richard Smith; cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu >> Subject: Re: [cfe-dev] [LLVMdev] SPIR