similar to: [LLVMdev] annotate a value

Hello, The interface is named Annotation and it allows any Annotable object to be annotated. Note that the Value class is an Annotable. HOWEVER, if the annotation information is something that might be useful to other developers or to other analysis/transformation passes, you're strongly encouraged to create an Analysis instead. See the various analyses in include/llvm/Analysis for examples.

On Tue, 14 Jun 2005, Reid Spencer wrote: > Hello, > > The interface is named Annotation and it allows any Annotable object to > be annotated. This is correct. > Note that the Value class is an Annotable. This is not. Shuhan, you have two options: 1. You can store the information you want in an std::map somewhere on the side. 2. You can add the fields you want to the LLVM

Hi: I want to pass some message of instructions from LLVM Internal representation to backend code. For example, I make a flag for some certain operands of certain instructions. How can it be passed to the backend instructions? Which programs I should look into? Would someone give me some idea? Thank you ! -- Shuhan

Hi: I have extended the IR for adding flag. But I just want this flag to pass through the backend machine code. I know there're several passes like register relocation, schedualing, etc. But I think I just miss the part which is used to "parser" the LLVM IR to machine code instructions. Would you give me some help? Thank you ! > On Sun, 10 Jul 2005 shding at mtu.edu wrote:

Hi, Where can I find the main function of llvm compiler in the source file? Thanks! -- Shuhan

Hi, I'm changing bytecode format a little bit, i.e. for 2 operands Instructions, the original is like this: 01-00:Opcode type 07-02:Opcode 15-08: Instruction type 23-16: Operand#1 31-24: Operand#2 My change is like this: 01-00:Opcode type 07-02:Opcode 15-08: Instruction type 16: myflag1 17: myflag2 24-18: Operand#1 31-25: Operand#2 I do

Hi, I have some problems when I use this command: gcc hello.s -o hello.native(for example) to assembly the native language to a program. I always got a error message like this : "gccas: hello.s:3: parse error, unexpected $undefined. hello.s:3: while reading token: '.' " I don't know what's wrong here. By the way, when I learned llvm at the first time, I followed

I'm a new guy for llvm. I'm doing a project in which some instructions should be moved from one block into another. Those instructions may be data-dependent. When I tried to delete them one by one, it cause the error message like, " use stuck around after a def is destroyed" even if I deleted the use befor the def. When I tried to add them to another block, errors occurred like

Hi, In the directory of lib/CodeGen/SelectionDAG, I cann't find SelectionDAGISel.cpp. I only have DAGBuilder.cpp and SelectionDAG.cpp. I don't know why. My edtion is 1.4. Is it because of the edtion difference? Thanks! > On Mon, 11 Jul 2005 shding at mtu.edu wrote: >> I have extended the IR for adding flag. But I just want this flag to >> pass through the backend

Hello. It would be very useful for my project being able to annotate Value's. An int would do fine. I found an old message with this same subject talking about the Annotation interface and Annotable object, but the doxygen graphs says that only Function is annotable. Could I use the ValueName for the job? It would be enough, although quite clumsy. Seems that Value's of type void

As the title. Thank! -- Shuhan

Hi: For some reason, I changed the files /ByteCode/Writer/Writer.cpp and /ByteCode/Reader/Reader.cpp and I introduced an new version number 6. Now I replaced these two changed files with the original ones that are version 5. And I rebuild the llvm compiler. What make me mad is that the bytecode produced now is still version 6! Of course the reader cannot recognize it because the current reader

On Mon, 11 Jul 2005 shding at mtu.edu wrote: > I have extended the IR for adding flag. But I just want this flag to > pass through the backend machine code. I know there're several passes > like register relocation, schedualing, etc. But I think I just miss the > part which is used to "parser" the LLVM IR to machine code > instructions. The part of the code

Thank you. I'm only consider about how the compiler comiles c program to LLVM IR. I know there should be a scanner, parser, and IR generator. But where is the main entrance and how about the flow of the process, especially about the IR generator? > shding at mtu.edu wrote: >> Hi, >> Where can I find the main function of llvm compiler in the source >> file? >>

On Sun, 10 Jul 2005 shding at mtu.edu wrote: > Hi: > I want to pass some message of instructions from LLVM Internal > representation to backend code. For example, I make a flag for some > certain operands of certain instructions. How can it be passed to the > backend instructions? Which programs I should look into? Would someone > give me some idea? Thank you ! The easiest

shding at mtu.edu wrote: > Hi, > Where can I find the main function of llvm compiler in the source file? > Thanks! Well, there's a loaded question. :) It depends on "which" compiler you mean. If you're talking about the llvm-gcc and llvm-g++ compilers (C/C++ to LLVM) then they are in the downloadable tarballs available here: http://llvm.cs.uiuc.edu/releases/. You

Hi: When I tried to use llc -march=sparcv9 to compile some llvm .bc to SparcV9, I got such error: llc: /llvm/lib/Target/SparcV9/SparcV9RegInfo.h:62: virtual void llvm::TargetRegClassInfo::markColorsUsed(unsigned int, int, int, std::vector<bool, std::allocator<bool> >&) const: Assertion `UserRegType == RegTypeWanted && "Default method is probably incorrect for

Hi: In the file of SparcV9BurgISel.cpp, you said you didn't implement the "Switch" instruction and I also can't find how the "Select" instruction is implemented. So do you do some work to handle these two kind of instructions in other parts? Where can I find it? Thank you! -- Shuhan

On Fri, 22 Sep 2023 10:32:05 -0700, Kees Cook wrote: > This is a batch of patches touching drm for preparing for the coming > implementation by GCC and Clang of the __counted_by attribute. Flexible > array members annotated with __counted_by can have their accesses > bounds-checked at run-time checking via CONFIG_UBSAN_BOUNDS (for array > indexing) and CONFIG_FORTIFY_SOURCE (for

On Fri, 22 Sep 2023 10:32:05 -0700, Kees Cook wrote: > This is a batch of patches touching drm for preparing for the coming > implementation by GCC and Clang of the __counted_by attribute. Flexible > array members annotated with __counted_by can have their accesses > bounds-checked at run-time checking via CONFIG_UBSAN_BOUNDS (for array > indexing) and CONFIG_FORTIFY_SOURCE (for