search for: scross

...ing with interpreting instruction semantics a while back, and you shouldn't have to write a parser to get the data structure back into coherent form, you can get what you want automatically and have the structure isolated into a common schema. On Sat, Jun 20, 2015 at 9:22 AM, Stephen Cross <scross at scross.co.uk> wrote: > > reproduce the code in that language > > Is the intention to exactly reproduce the original source code? Or > some code that's functionally equivalent? > > On Sat, Jun 20, 2015 at 8:05 AM, Alec Taylor <alec.taylor6 at gmail.com> > wro...

On Wed, 1 Jul 2015 at 08:19 Stephen Cross <scross at scross.co.uk> wrote: > Hi everyone, > > I was wondering if anyone could answer the questions in my first > email. These were: > > * Why does Clang generate 8 byte alignment for 16+ byte arrays on > x86-64, even though the AMD64 ABI seems to require 16 byte alignment? &gt...

On Tue, 30 Jun 2015 at 06:02 Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- > > From: "Stephen Cross" <scross at scross.co.uk> > > To: "Reid Kleckner" <rnk at google.com> > > Cc: "Clang Developers List" <cfe-dev at cs.uiuc.edu>, "LLVM Developers > Mailing List" <llvmdev at cs.uiuc.edu> > > Sent: Monday, June 29, 2015 3:03:40 PM > &g...

Hi everyone, Currently it looks like metadata is used in LLVM IR essentially as an 'optional extra', in that any pass is allowed to remove metadata (though preserving metadata is useful) and the program should remain valid. In other words the metadata only communicates information about code quality or associated information rather than issues relevant to correctness. First question: Is

...> > That said, I wish you luck, and I hope the project eases some of the > difficulties for new frontends. It is very possible that the corner cases > that keep me up at night are not the problems that users actually face. :) > > On Sun, Jun 28, 2015 at 3:22 PM, Stephen Cross <scross at scross.co.uk> wrote: >> >> Hi everyone, >> >> (Also CC'ed cfe-dev since this seems relevant to Clang, particularly >> the questions at the end.) >> >> I've been working on a library to generate LLVM IR that complies with >> platform ABIs...

> I suspect #2 is the right design, mostly because I suspect most of the interesting and important inference cases are going to be cases where we can easily infer the stronger guarantee, and once inferred we will have much more freedom to optimize based on this stronger guarantee... Can't the stronger guarantee be represented in the existing system by either: * Adding 'readonly'

...cfe-dev since this seems relevant to Clang, particularly the questions at the end.) I've been working on a library to generate LLVM IR that complies with platform ABIs (the current focus is on C but I'm also interested in ABIs for other languages). You can find it here: https://github.com/scross99/llvm-abi To explain further (for those who are unfamiliar), LLVM frontends have to modify function argument types, attributes etc. in order to ensure the backend generates code that satisfies the ABI; this is needed because LLVM's type system can't encode all the necessary information. T...

Considering engineering my own code-generator. If I do go ahead, will open-source the end result. Needs to read [parse] one language, and output JSON (conformant to a specific JSON-schema). Then needs to read JSON, and reproduce the code in that language, and [possibly] merge the generated code with existing code. Languages I'm looking to support are all rather popular (Python, Go, Rust,

> > This seems interesting, I have a few questions: > > > Has the ISA been finalized yet or is it still a work in progress? Will > there be a fixed number of registers? > The design document has a high-level idea of the ISA, or rather of the AST we're thinking of going with: https://github.com/WebAssembly/design/blob/master/AstSemantics.md The final encoding isn't

Hi everyone, I'm the developer of the Loci programming language ( http://loci-lang.org ), for which the compiler is a front-end for LLVM. I would like to say that LLVM has been extremely useful for the development of the compiler and so thank you everyone for building this amazing system. ---- Virtual Method Calls ---- While most aspects of the language map well onto LLVM IR, it seems