similar to: [LLVMdev] Emitting an extra section with meta-information

Hi, I think it's an awesome idea to make sure all names are logical. It is an essential feature of a good API to have logical naming :) > I really dislike that all the files and classes in the MC library > start with MC. This is c++, not c :( On a similar note, all the classes in clang/CodeGen are prefixed with CG or even CodeGen, could those be renamed as well? And speaking of the

On Nov 24, 2012, at 1:02 AM, Tinco Andringa <mail at tinco.nl> wrote: > Hi, > > I think it's an awesome idea to make sure all names are logical. It is > an essential feature of a good API to have logical naming :) > >> I really dislike that all the files and classes in the MC library >> start with MC. This is c++, not c :( > > On a similar note, all

Dear llvm-dev-list, I have created my own custom section to be added at the end into a binary upon compilation which contains address of all basic blocks. As the final address of the basic block is not known until link time, I collect the MCSymbol* Symbol Values per BB in a temp array and at the in the custom section and emit it (emitSymbolValue) into my section within EmitEndOfAsmFile() I have

> I really dislike that all the files and classes in the MC library > start with MC. This is c++, not c :( Same here. > > - Michael Spencer Cheers, Rafael

I have managed to produce correct relocation records for my jump table with the below code, but am baffled to how to emit the text addresses to the data section. I'm sure it is just a few lines of code. Any suggestions? Jack void MCObjectStreamer::EmitGPRel32Value(const MCExpr *Value) { MCDataFragment *DF = getOrCreateDataFragment(); int Size = 4; // Assumption is that this is alway

On 10/31/2018 03:02 PM, Justin Bogner wrote: > Tom Stellard <tstellar at redhat.com> writes: >>> On 10/31/2018 10:39 AM, Justin Bogner wrote: >>>> Tom Stellard <tstellar at redhat.com> writes: >>>>> On 10/31/2018 09:22 AM, Justin Bogner via llvm-dev wrote: >>>>>> Hi all, >>>>>> >>>>>> I've

Hi all, In an effort to improve compatibility on the CodeView debug info side, we need to output a few new record types on the backend that don't seem to have the necessary info tracked by the debug info metadata. Specifically: 1) For each compile unit, we need to emit a record containing the output file name (e.g. foo.obj) 2) For each compile unit, we need to emit a record containing the

Hallo, Does Rsync support XATTR sync between nodes? Using setfattr -n user.line -v 100 <File Name> setfattr -n user.creator -v ?Rakesh Kumar Bhatia? <File Name> will create extended attribute for different files. I used rsync -av <source> <destination> to copy the files. extended attributes are missing in the destination path. Can use the command

Hi again. I've though more about the full standard being too ambitious, and now I fully agree with that. So I had a go at choosing the useful subset of Fortran on which I would like to work on - my update proposal can be viewed at https://gist.github.com/hyp/5434845 . Focusing on less should also improve my productivity and lead to a better summer of code project by drastically reducing the

Hi Alex, You may want to check the later versions of the standard also to check if some of your proposal is not deprecated there. The most important thing in the Fortran standard is the array support and it is a big task by itself. In my opinion, the I/O part is not the most important thing yet it is an enormous task. Usually, the Fortran routines are used externally in other computation and I/O

Hi! I am the author of Maruku (http://maruku.rubyforge.org/), a Markdown-superset interpreter. At the moment I am 1) learning webgen 2) integrating Maruku+webgen 3) converting my website to webgen, so I have many questions (one question, one message). First one: I wrote the straightforward maruku.rb converter (see attachment). In a content converter, how can I access the meta-information of

Greetings, Using latest svn. I've noticed the following error when performing index merging: postlist: baseB blocksize=8K items=33962 lastblock=534 revision=1 levels=2 root=459 B-tree checked okay Tag containing meta information is corrupt. postlist table errors found: 1 I can still search on this index (I've only checked very small indexes), but merging is now a problem since I check

We are intending to include a lot more pre-computed information with an installed package in 2.0.0, and to force all packages to be reinstalled under 2.0.0. This causes a problem with R-devel pre-2.0.0, which stamps packages as having been installed under the future 2.0.0. As of today we have changed the format of the meta-information file 'Meta/package.rds', and you should either

Thanks for the responses! > I might be wrong (I'd love to be wrong here!) but I think this is a bit > too ambitious > You might be right about it being too ambitious, it would certainly be wise to aim for less. A more polished, but less broad product is definitely better than a buggy standard compliant one, and I think that it would go better with the general philosophy of GSoC. I

Hello all, I've began writing the parsing section of the spec, and I though I'd let you know about where I'm heading with all this. Basically, parsing is defined as three consecutive passes: parsing document elements, parsing block elements and parsing span elements. Each pass is going to contain a set of rules the parser should attempt to match while parsing the input. Rules

Some more information about the relaxation pass whose effectiveness and convergence guarantees were listed as a concern: TLDR; Our relaxation pass is similar to what LLVM’s MCAssembler does but with a caveat for efficiency. Our experimental results show it is efficient and convergence is guaranteed. Our relaxation pass is very similar to what MCAssembler does as it needs to solve the same

[adding various lists and the two other nouveau maintainers to the list of recipients] For the rest of this mail: [TLDR: I'm adding this report to the list of tracked Linux kernel regressions; the text you find below is based on a few templates paragraphs you might have encountered already in similar form. See link in footer if these mails annoy you.] On 18.01.23 21:59, Chris Clayton wrote:

On 2007-01-15, at 11:48, Chris Lattner wrote: > On Mon, 15 Jan 2007, Nick Lewycky wrote: > >> The structure contents are defined right afterwards, but I assume >> that the typedefs are used when emitting the structure contents? >> We may have to put fully defined structures first and typedefs >> second. > > Looks like it. It sounds like the CBE should

Hello, I wanted to consolidate all the discussions and our final thoughts on the concerns raised. I have attached a document consolidating it. BOLT’s performance gains inspired this work and we believe BOLT is a great piece of engineering. However, there are build environments where scalability is critical and memory limits per process are tight : * Debug Fission,

----- Original Message ----- > From: "Dmitri Gribenko" <gribozavr at gmail.com> > To: "Alex L" <arphaman at gmail.com> > Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Sent: Monday, April 22, 2013 9:00:51 AM > Subject: Re: [LLVMdev] GSoC project questions. > > On Mon, Apr 22, 2013 at 4:30 PM, Alex L <arphaman