similar to: Metadata on StructType

Displaying 20 results from an estimated 100000 matches similar to: "Metadata on StructType"

2015 Aug 14
2
[LLVM RFC] Add llvm.typeid.for intrinsic
This is for BPF output. BPF program output bytes to perf through a tracepoint. For decoding such data, we need a way to describe the format of the buffer. This patch is a try which gives each variable a unique number by introducing a new intrinsic 'llvm.typeid.for'. At the bottom is an example of using that intrinsic and the result of $ clang -target bpf -O2 -c -S ./test_typeid.c
2019 Sep 27
3
Question on target-features
Ugh, that would be a “yes” then… -- Krzysztof Parzyszek kparzysz at quicinc.com<mailto:kparzysz at quicinc.com> AI tools development From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of Krzysztof Parzyszek via llvm-dev Sent: Friday, September 27, 2019 10:05 AM To: Dangeti Tharun kumar <cs15mtech11002 at iith.ac.in>; llvm-dev at lists.llvm.org Subject: [EXT] Re:
2016 Aug 25
2
Questions on LLVM vectorization diagnostics
Hi, Gerolf. We've been a bit quiet for some time. After listening to feedback on the project internally and externally, we decided to take a more generally accepted community development model ---- building up through a collection of small incremental changes ---- than trying to make a big step forward. That change of course took a bit of time, but we are getting close to the first NFC patch
2013 Feb 11
1
[LLVMdev] Parallel Loop Metadata
----- Original Message ----- > From: "Tobias Grosser" <tobias at grosser.es> > To: "Nadav Rotem" <nrotem at apple.com> > Cc: "llvmdev at cs.uiuc.edu Dev" <llvmdev at cs.uiuc.edu> > Sent: Monday, February 11, 2013 4:58:50 PM > Subject: Re: [LLVMdev] Parallel Loop Metadata > > On 02/11/2013 10:31 PM, Nadav Rotem wrote: > >
2012 Mar 27
0
[LLVMdev] llvm::Type as llvm::Value in metadata
On Mon, Mar 26, 2012 at 11:48 PM, Marcus Frenkel <marcus.frenkel at fernuni-hagen.de> wrote: > On Tue, Mar 27, 2012 at 01:55 AM, Eli Friedman <eli.friedman at gmail.com> > wrote: >> >> On Mon, Mar 26, 2012 at 3:08 PM, Marcus Frenkel >> <marcus.frenkel at fernuni-hagen.de> wrote: >>> >>> Hi all, >>> >>> I've a
2016 Jun 24
2
Questions on LLVM vectorization diagnostics
Hi Dangeti, Ramakrishna, Adam, and Gerolf, >Yes this is an area that needs further improvement. We have some immediate plans to make these more useful. See the recent llvm-dev threads [1], [2]. It takes a lot of dedicated effort to make vectorization report easier to understand by ordinary programmers (i.e., those who are not compiler writers). Having done that for ICC ourselves, we truly
2016 Jun 23
4
Questions on LLVM vectorization diagnostics
Dear LLVM Community, I am D Tharun Kumar, masters student at Indian Institute of Technology Hyderabad, working in a team to improve current vectorizer in LLVM. As an initial study, we are studying various benchmarks to analyze and compare vectorizing capabilities of LLVM, GCC and ICC. We found that vectorization remarks given by LLVM are vague and brief, comparatively GCC and ICC are giving
2019 Sep 27
2
Question on target-features
Hi, In "target-features" list in LLVM-IR, there are "+feature", "-feature". My question is, does "-feature" is equivalent to not specifying a feature at all? For example: *attributes #0 = { "target-cpu"="znver2" "target-features"="+avx -avx2" }* Wheather it is equalent to omitting the avx2 from list? *attributes #0
2013 Feb 11
0
[LLVMdev] Parallel Loop Metadata
On 02/11/2013 10:31 PM, Nadav Rotem wrote: > Now that we have a better understanding of the proposal for using per-instruction metadata, I think that we need to revisit the "single metedata" approach (Pekka's original suggestion). Following Andrew's comments we understood that Sebastian's proposal causes issues with inlining and unrolling. It seems we all agree that his
2019 Jan 07
2
[Xray] Help with Xray
On Mon, Jan 7, 2019 at 3:21 PM Dean Michael Berris <dean.berris at gmail.com> wrote: > On Mon, Jan 7, 2019 at 8:43 PM Dangeti Tharun kumar > <cs15mtech11002 at iith.ac.in> wrote: > > > > Hi Dean, > > > > I have tried with -instr-map-1 and -instr-map-2, it didn't work. > > > > Yeah, I'm looking through the code and it looks like
2013 Sep 12
2
[LLVMdev] llvm.meta (was Rotated loop identification)
----- Original Message ----- > > > > On Sep 7, 2013, at 7:41 AM, Hal Finkel < hfinkel at anl.gov > wrote: > > > > > On Feb 7, 2013, at 10:58 PM, Hal Finkel < hfinkel at anl.gov > wrote: > > > > > As long as this is brainstorming time, I actually like the idea of > an > llvm.invariant intrinsic that the optimizers know to
2004 Aug 06
0
ices, alsa, dsnoop plugin a metadata update
Hello, I found a bug by metadata updating in ices-2.0.0. I use icecast2 server for streaming stations of Czech Radio. Czech Radio prefers streaming in both formats mp3 and ogg. So - I'm using DarkIce as a live audio streamer, which does encoding to mp3 and ogg streams together. I would like to insert textual information about actual streaming program, but DarkIce does not support it. So -
2016 Oct 10
2
On Loop Distribution pass
> On Oct 10, 2016, at 2:50 PM, Hal Finkel <hfinkel at anl.gov> wrote: > > > From: "Dangeti Tharun kumar via llvm-dev" <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> > To: llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org> > Cc: "Santanu Das" <cs15mtech11018 at iith.ac.in <mailto:cs15mtech11018 at
2013 Sep 09
0
[LLVMdev] llvm.meta (was Rotated loop identification)
On Sep 7, 2013, at 7:41 AM, Hal Finkel <hfinkel at anl.gov> wrote: >> On Feb 7, 2013, at 10:58 PM, Hal Finkel < hfinkel at anl.gov > wrote: >> >> >> >> >> As long as this is brainstorming time, I actually like the idea of >> an >> llvm.invariant intrinsic that the optimizers know to ignore. I >> like >> it for other
2019 Jan 07
2
[Xray] Help with Xray
Hi Dean, I have tried with -instr-map-1 and -instr-map-2, it didn't work. Is there a way to find the function name from the identifier? -DTharun On Mon, Jan 7, 2019 at 2:29 PM Dean Michael Berris <dean.berris at gmail.com> wrote: > Hi Dangeti, > > That's interesting -- can you try providing both `-instr-map-1=` and > `-instr-map-2=` even though they're the same
2013 Feb 07
0
[LLVMdev] Parallel Loop Metadata
On 02/07/2013 11:49 PM, Nadav Rotem wrote: > > On Feb 7, 2013, at 10:55 AM, Pekka Jääskeläinen <pekka.jaaskelainen at tut.fi> wrote: > >> Hi Nadav, >> >> On 02/07/2013 07:46 PM, Nadav Rotem wrote: >>> Pekka suggested that we add two kind of metadata: llvm.loop.parallel >>> (attached to each loop latch) and llvm.mem.parallel (attached to each
2012 Feb 27
0
[LLVMdev] mapping types from a bitcode module
Hi Michael, since noone of the experts answered, let me share our experiences. We recently had exactly the same problem, I posted on this list on January 31st. I didn't follow Duncans advice to "just use the linker", since for several reasons we wanted to have unique struct types even in the separate modules. > 1) duplicate the LinkModule internal code and copy the module we
2018 Jul 24
2
StructType --> DICompositeType?
Is there a more convenient way to obtain a DIType given a Type than matching up the strings for the names? For example, given: struct S { int x, y; } s; void foo(S *a) { a->x = 0; a->y = 1; } There are DIType nodes for the struct Type: !6 = distinct !DICompositeType(tag: DW_TAG_structure_type, name: "S", file: !3, line: 1, size: 64, flags: DIFlagTypePassByValue,
2012 Feb 24
2
[LLVMdev] mapping types from a bitcode module
Hi all, We've run into a tricky situation in our work on the Crack compiler and I'm hoping that someone on this list can help us find the best solution. We're currently trying to implement "module caching" for Crack, similar to the feature in Python where module bitcode is persisted at compile time. When we import a module, before compiling the module we check for a
2019 Aug 13
0
MetaData Update for FLAC and OPUS
Good afternoon, On Tue, 2019-08-13 at 14:26 +0200, bn at radio42.com wrote: > I am using the standard Xiph.org FLAC encoder, but I couldn't find any option to update the meta-data mid-stream. > Also the FLAC spec says, that it defines VORBIS_COMMENT as the only way to transmit meta-data information. > This is the only officially supported tagging mechanism in FLAC. There may be only