similar to: [LLVMdev] IMPORTANT: Test Your Changes Before Committing Them!!

Hey all, I just found Bryan Helmkamp''s (of webrat fame) slides on a presentation he did at GoRuCo 2008: http://www.brynary.com/2008/4/26/story-driven-development-slides-posted On slides 21-24 he talks about writing good stories and shows gives two examples.. the way not to do it and the way to do it. You can also see the video of the presentation at confreaks

The coding guidelines say: > Function names should be verb phrases (as they represent actions), and command-like function should be imperative. The name should be camel case, and start with a lower case letter (e.g. openFile() or isFoo()). This means that functions that just compute or access a value (no side-effects) should be named e.g. `getParent()`, rather than `parent()` as they are in

On Thu, 2018-02-08 at 23:48 +0000, Chandler Carruth wrote: > Bringing everything back to this thread -- we now have %V support > landed in top-of-tree, so wanted to get confirmation that top-of-tree > is healthy for the kernel, or see what else we need to do. For 64-bit it's fine. For 32-bit we *think* the retpoline bits are OK but it doesn't build for other reasons on 32-bit.

On Fri, 4 Oct 2019 at 18:11, Japheth Cleaver <cleaver at terabithia.org> wrote: > > On 10/4/2019 8:17 AM, Lamar Owen wrote: > > On 10/4/19 10:40 AM, Valeri Galtsev wrote: > >> My impression is younger generation doesn't value rules that > >> programmers were following 2-3 decades ago. One of which is: > >> > >> Do not make any changes [in

> On 24 May 2018, at 20:19, Sam McCall via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > The coding guidelines say: > > Function names should be verb phrases (as they represent actions), and command-like function should be imperative. The name should be camel case, and start with a lower case letter (e.g. openFile() or isFoo()). > > This means that functions that

On 24.05.2018 13:11, Dean Michael Berris via llvm-dev wrote: > >> On 24 May 2018, at 20:19, Sam McCall via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> The coding guidelines say: >>> Function names should be verb phrases (as they represent actions), and command-like function should be imperative. The name should be camel case, and start with a lower case

On Thursday 07 July 2016 17:30:03 Richard W.M. Jones wrote: > This adds imperative list manipulation functions inspired by Perl. > The functions are passed list refs which get updated in place. > > This allows us to replace some awkward pure functional code like: > > let xs = ys in > let xs = if foo then xs @ zs else xs in > > with: > > let xs = ref ys in

Basic support for Small bss and data. The rest is implemented with target specific logic and will be commited as soon as it's ok to commit this patch. -- Bruno Cardoso Lopes http://www.brunocardoso.cc "When faced with untenable alternatives, you should consider your imperative." -------------- next part -------------- A non-text attachment was scrubbed... Name: smallsections.patch

Hi all, I am trying to compile a high-level imperative OOP-like language to the LLVM IR. Do we have any "generic" way of translating a non-SSA form to the LLVM IR's SSA? There are lots of LLVM front-ends now. Do they do such translation individually? or there is some common non-SSA IR that we can translate to, and can be converted to the LLVM IR automatically? I did not find such

So the right way to do it -- it seemed to work when I tried it, at least -- is metaflac --remove-all --dont-use-padding filename.flac ? I guess that these features make it more imperative than ever to watch the timestamps and not to validate a FLAC with an MD5 that is older than the FLAC is.

On Thu, Jul 07, 2016 at 06:08:43PM +0100, Richard W.M. Jones wrote: > On Thu, Jul 07, 2016 at 07:00:46PM +0200, Pino Toscano wrote: > > On Thursday 07 July 2016 17:30:03 Richard W.M. Jones wrote: > > > This adds imperative list manipulation functions inspired by Perl. > > > The functions are passed list refs which get updated in place. > > > > > > This

Am Freitag, den 04.04.2008, 15:19 -0400 schrieb Jonathan S. Shapiro: > In general, the C++ compiler does NOT know the type of the leaf class > when performing a virtual method invocation. In particular, a parameter > (including "this") alleging to be a Foo* (Foo being some class) may > actually be any subclass of Foo, so unless the compiler can trace the > value flow all

Hi, I'm trying to emit FP_ROUND f64 -> f32 considering a mips target that only supports single float point operations. The problem is that f32 is considered legal on this target but f64 doesn't and the only way I can codegen this instruction is using setConvertAction(MVT::f64, MVT::f32, Expand), which issues a EmitStackConvert. What if I want a libcall instead? What should I do? The

Hi Lists, I currently have the issue of wanting to use emu-system-x86_64 on a ppc64le platform. It is imperative to pass the "-accel tcg,thread=multi” parameter to qemu when starting an instance, as without that, it will only use one thread and hence of limited/no use. The problem is, that libvirt itself, passes “-machine q35,accel=tcg” to qemu, which is a different parameter, that

On Tue, Feb 6, 2018 at 2:56 PM David Woodhouse <dwmw2 at infradead.org> wrote: > On Tue, 2018-02-06 at 22:08 +0000, Chandler Carruth wrote: > > So, I was waiting to hear a definitive response on whether using aliases > is hard, and didn't see one here, which is why I haven't responded further. > > However, a colleauge pointed me at an LKML thread where it seems

Hi all, I am trying to compile my toy language to LLVM back end. (I am new to LLVM, so my questions may sound naive) I am looking at some tutorials about LLVM, most are about how to use LLVM IRBuilder, however, I find the API provided by IRBuilder is quite imperative and verbose, and the API changes so fast that most of the tutorials are out of dated. So I am wondering what's

> On Jan 9, 2017, at 10:29 AM, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 9 January 2017 at 18:20, Reid Kleckner <rnk at google.com> wrote: >> I object to the first. If you need a new type name, use a typedef. It's time >> honored and everyone, including C programmers, will know what you're doing. >> I don't understand

Please check out this ticket (which would explain almost everything): http://dev.rubyonrails.org/ticket/8762 So basically, Rails to_json methods produces invalid JSON out of the box as it doesn''t quote all hash keys. This is valid JSON: { "id": 6589, "code": "SIN", "name": "Singapore" } This is not (Rails'' JSON encoders

On Apr 4, 2008, at 3:59 PM, Joachim Durchholz wrote: > > I'm not sure how hard (a) really is. It's being done in other > imperative > OO languages, and quite successful there (the SmartEiffel folks have > reported they can eliminate the vtable lookup in about 90% of call > sites, Are those the folks that don't do separate compilation or dynamic libraries? :-)

Hi Eduardo, > I'm a little new to LLVM. > I know that the backends are still in experimental stage. MSIL and MIPS > would be very useful for a project that I'm working on. Do you have any > plans to have it completed in the next few months? I could generate the > MSIL assembly but when compiled it, which compiles sucessfully, it > generates invalid opcode errors. As