Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Some thoughts on metadata, debug info, TBAA, annotations etc"
2008 Oct 31
2
[LLVMdev] Optimizations and debug info
[Moving discussion to LLVMdev]
On 2008-10-31 21:55, Dan Gohman wrote:
> Hi Török,
>
> @llvm.dbg.stoppoint actually does read and write memory, in a
> sense. It's a point where a user could stop in a debugger, and
> use the debugger to both read and write memory. If the optimizers
> are allowed to reorder or delete memory operations, these
> intrinsics will become
2008 Nov 03
0
[LLVMdev] Optimizations and debug info
On Oct 31, 2008, at 1:29 PM, Török Edwin wrote:
> Hi Dan,
> I am actually more interested in Analysis working in presence of debug
> info, but in order to get any meaningful results, you need to run some
> transformations, at least GVN, otherwise loops aren't transformed to
> canonical form either.
Right.
> So we could:
> - teach GVN that a dependency on a debug
2010 Feb 09
0
[LLVMdev] Mapping bitcode to source code
On Feb 9, 2010, at 11:13 AM, Trevor Harmon wrote:
> Is there any information about these changes and why they were
> necessary?
I think I found it:
http://nondot.org/~sabre/LLVMNotes/EmbeddedMetadata.txt
Still looking for an API to access the metadata...
Trevor
2009 Jul 27
4
[LLVMdev] PROPOSAL : Introduce NamedMetadata
In LLVM IR metadata is used to attach auxiliary information with
various IR constructs. Currently metadata information is represented
using MDNode and MDString. The metadata can refer to LLVM values but
these references are not counted as regular "uses" of these values
because metadata is maintained 'on the side'. This ensures that the
optimizer is not influenced by auxiliary
2009 Jul 27
0
[LLVMdev] PROPOSAL : Introduce NamedMetadata
On Jul 27, 2009, at 10:10 AM, Devang Patel wrote:
> In LLVM IR metadata is used to attach auxiliary information with
> various IR constructs. Currently metadata information is represented
> using MDNode and MDString. The metadata can refer to LLVM values but
> these references are not counted as regular "uses" of these values
> because metadata is maintained 'on the
2009 Jul 27
2
[LLVMdev] PROPOSAL : Introduce NamedMetadata
On Mon, Jul 27, 2009 at 1:13 PM, Dan Gohman<gohman at apple.com> wrote:
>
> On Jul 27, 2009, at 10:10 AM, Devang Patel wrote:
>
>
>> In LLVM IR metadata is used to attach auxiliary information with
>> various IR constructs. Currently metadata information is represented
>> using MDNode and MDString. The metadata can refer to LLVM values but
>> these
2010 Feb 09
3
[LLVMdev] Mapping bitcode to source code
On Feb 8, 2010, at 8:51 PM, Duncan Sands wrote:
> this can be done using debug info. Check out
> http://llvm.org/docs/SourceLevelDebugging.html
Wow, that threw me for a loop. I'm using the 2.6 release, thinking I
was up to date, but its debug output doesn't look anything like what's
described in the above link. It appears to document the upcoming 2.7
version, which
2008 Nov 03
2
[LLVMdev] Optimizations and debug info
On 2008-11-03 12:33, Chris Lattner wrote:
> On Oct 31, 2008, at 1:29 PM, Török Edwin wrote:
>
>> Hi Dan,
>> I am actually more interested in Analysis working in presence of debug
>> info, but in order to get any meaningful results, you need to run some
>> transformations, at least GVN, otherwise loops aren't transformed to
>> canonical form either.
2018 May 29
2
Can creating new forms of debug info metadata be simplified? [formatting fixed]
[Resending due to accidental markdown rendering - sorry]
Hi list,
Let's talk about adding a new type of debug info metadata. Here are the
steps (at minimum - probably incomplete) one needs to take:
1. Create a new class in the hierarchy
2. Implement two forms of `MD_NODE_GET`
3. Specialize `MDNodeKeyImpl`
4. Modify `LLParser.cpp` and add serialization code for your
special type5. Modify
2018 May 29
0
Can creating new forms of debug info metadata be simplified? [formatting fixed]
+some of the debug info cabal (& Duncan, as an emeritus member, and person
who plumbed a lot of the current debug info syntax support in)
Visitor seems plausible though I haven't looked at the code in detail to
see if it'd work perfectly.
On Tue, May 29, 2018 at 7:56 AM Sohail Somani (Fizz Buzz Inc.) via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> [Resending due to
2018 May 29
2
Can creating new forms of debug info metadata be simplified? [formatting fixed]
> On May 29, 2018, at 12:28 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
> +some of the debug info cabal (& Duncan, as an emeritus member, and person who plumbed a lot of the current debug info syntax support in)
>
> Visitor seems plausible though I haven't looked at the code in detail to see if it'd work perfectly.
>
> On Tue, May 29, 2018 at 7:56
2011 Jun 25
0
[LLVMdev] inefficiencies in ConstantUniqueMap ?
On 25 June 2011 13:00, Duncan Sands <baldrick at free.fr> wrote:
>> 3. Clang/dragonegg need to adapt to the new API (help appreciated!)
>
> what needs to be done exactly?
Background info: http://www.nondot.org/sabre/LLVMNotes/TypeSystemRewrite.txt
As I understand it, PATypeHolder, OpaqueType and the Module's
TypeSymbolTable are gone. Instead, StructTypes can optionally be
2018 May 29
0
Can creating new forms of debug info metadata be simplified?
Hi list,
Let’s talk about adding a new type of debug info metadata. Here are the
steps (at minimum - probably incomplete) one needs to take:
1. Create a new class in the hierarchy
2. Implement two forms of MD_NODE_GET
3. Specialize MDNodeKeyImpl
4. Modify LLParser.cpp and add serialization code for your special type
5. Modify AsmWriter.cpp and add serialization code for your
special
2009 Sep 11
0
[LLVMdev] [proposal] Extensible IR metadata
On Sep 11, 2009, at 9:57 AM, Chris Lattner wrote:
> Devang's work on debug info prompted this, thoughts welcome:
> http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt
The document mentions "instructions" a lot. We'll want to be able to
apply metadata to ConstantExprs as well at least, if not also Arguments
(think noalias) and other stuff, so it seems best to just
2009 Apr 18
1
[LLVMdev] debug stoppoint nodes with -fast option
Can we help in local variable debug info work.
Dale Johannesen wrote:
> On Apr 7, 2009, at 9:52 PMPDT, vasudev wrote:
>
>
>> Thanks for the info regarding DebugLoc field. Another related
>> question
>> that I have is regarding debug info for local variables. With -fast
>> option, ISD::DECLARE nodes are created in DAG for debug info of local
>>
2008 Sep 20
1
[LLVMdev] Proposal : Function Notes
On Aug 23, 2008, at 6:58 AM, Matthijs Kooijman wrote:
> Hi Devang,
>
>> All supported notes must be documented in LLVM language reference.
> Does this also mean that undocumented / unsupported notes are
> invalid? In
> particular, when I have a custom frontend and backend, using custom
> notes
> could be a great way to communicate between those, if the LLVM IR
2009 Jul 28
0
[LLVMdev] PROPOSAL : Introduce NamedMetadata
Devang Patel wrote:
> In LLVM IR metadata is used to attach auxiliary information with
> various IR constructs. Currently metadata information is represented
> using MDNode and MDString. The metadata can refer to LLVM values but
> these references are not counted as regular "uses" of these values
> because metadata is maintained 'on the side'. This ensures that the
2008 Jul 10
0
[LLVMdev] Optimization passes and debug info
On Jul 8, 2008, at 3:33 AM, Matthijs Kooijman wrote:
> Hi all,
>
> I've been fiddling around with debug info generated by clang, with
> the goal of
> propagating line number info to our custom backend (which is not an
> llvm
> backend, but does use llvm IR as its input).
Cool.
> I've created a small pass which strips all debug info except for
> stop
2009 Jul 27
0
[LLVMdev] PROPOSAL : Introduce NamedMetadata
On Jul 27, 2009, at 3:05 PM, Devang Patel wrote:
> On Mon, Jul 27, 2009 at 1:13 PM, Dan Gohman<gohman at apple.com> wrote:
>
>>
>>
>> On Jul 27, 2009, at 10:10 AM, Devang Patel wrote:
>>
>>
>>
>>
>>
>>> In LLVM IR metadata is used to attach auxiliary information with
>>>
>>> various IR constructs. Currently
2009 Sep 12
3
[LLVMdev] [proposal] Extensible IR metadata
Dan Gohman wrote:
> On Sep 11, 2009, at 9:57 AM, Chris Lattner wrote:
>
>
>> Devang's work on debug info prompted this, thoughts welcome:
>> http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt
>
> The document mentions "instructions" a lot. We'll want to be able to
> apply metadata to ConstantExprs as well at least, if not also Arguments
>