search for: tartan

Hi all, I'd like to introduce you to the Tartan project (http://tartan.folklogic.net) and get your feedback. It's a Ruby based wiki text parser with the following goals: 1. handle more then one wiki markup but start with Markdown 2. allow mixing-in of markup rules (eg. Markdown + smartypants + tables + wiki links; each as a sep...

Of course it's *possible*, in a fundamental sense. It's even pretty easy to get right in a compiler back end (in a conceptual sense). You have to touch a LOT of code, but all the changes are trivial. We did this at Tartan Labs back in the 90s. Done with only a bit of care, it makes debugging possible at any optimization level. The idea is to make the debug information reflect what the optimizer and code generator actually did, rather than restricting them to the linear mapping supported by most debuggers. If anyon...

...ssible to compile a C file or LLVM assembler bitcode file and save off the DAGS ascii file. Believe it or not, they had this over 30 years ago with the PQCC (Production Quality Compiler Compiler ) project at Carnegie Mellon. Intermetrics where I worked had a commercial version of this and later Tartan Laboratories. http://en.wikipedia.org/wiki/PQCC Any phase of the compiler had an ascii representation that could be parsed into binary stuctures and then submitted to that phase and optionally propagated to later phases. You could also save off the state of any phase in ascii too. So you could...

On 9 Aug 2013, at 00:18, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote: > I am hoping that this proposal will generate a lot of feedback, and there are many different topics to discuss. When replying to this email, please change the subject header to something more specific, but keep the [global-isel] tag. Subject changed, but I'm not sure if helps... Overall, I really like this

It's kind of troubling that you can't create test cases that start with DAG as opposed to bitcode .ll. It's very tedious sometimes to go through and make sure that you have really tested all your patterns and sometimes the compiler changes and it stops generating those patterns but may resume generating them later. So if you make a change at a time when it's not generating

Do you have any suggestions about how to address this? -- Sean Silva

On 7 June 2013 13:53, Dallman, John <john.dallman at siemens.com> wrote: > It needs to be possible to debug code at any optimisation level. > Yes, I agree. But after O1, sequential execution is a big impediment for optimizations, and keeping the debug information valid after so many transformations might pose a big penalty on the passes (time & memory). That was the whole idea

I'm not a LLVM or Clang developer, but I do spend a lot of time teasing software into working with the highest possible optimisation levels where it still works correctly. These guidelines are pretty good, but there are a few details worth considering. It needs to be possible to debug code at any optimisation level. It's acceptable for that to be harder at high optimisation levels, but

I am hoping that this proposal will generate a lot of feedback, and there are many different topics to discuss. When replying to this email, please change the subject header to something more specific, but keep the [global-isel] tag. Thanks, /jakob Proposal for a Global Instruction Selector It is becoming evident that we need a replacement for the SelectionDAG-based instruction selector. This