search for: lemahieu

Hi everyone. We're interested in contributing a Hexagon assembler to MC and we're looking for comments on a good way to integrate the grammar in to the infrastructure. We rely on having a robust assembler because we have a large base of developers that write in assembly due to low power requirements for mobile devices. We put in some C-like concepts to make the syntax easier and this

...urns getAnyRelocationAddress so I’ll have to also find its containing section and add this in just so llvm-objdump can later subtract it. Can you detail why this is a better plan? From: Rafael Espíndola [mailto:rafael.espindola at gmail.com] Sent: Thursday, March 24, 2016 3:13 PM To: Colin LeMahieu <colinl at codeaurora.org> Cc: llvm-commits <llvm-commits at lists.llvm.org>; Shankar Easwaran <shankare at codeaurora.org>; Hemant Kulkarni <khemant at codeaurora.org>; reviews+D15965+public+319b19c852e3c4e3 at reviews.llvm.org Subject: RE: [PATCH] D15965: Add support for d...

On Wed, Feb 18, 2015 at 6:58 AM, Colin LeMahieu <colinl at codeaurora.org> wrote: > It might help after adding explicit types where needed and before adding > the opaque pointer type, to change all pointers to a single type in the > existing type system, i8* could work or maybe a weird type that would shake > out any issues li...

...need reasonable behaviors for each platform. Does this seem like a good approach and does anyone have input on how this function should behave on COFF/MachO? -----Original Message----- From: Rafael Espíndola [mailto:rafael.espindola at gmail.com] Sent: Tuesday, March 22, 2016 10:42 AM To: Colin LeMahieu <colinl at codeaurora.org> Cc: llvm-commits <llvm-commits at lists.llvm.org> Subject: Re: [llvm] r263971 - [llvm-objdump] Printing relocations in executable and shared object files. This partially reverts r215844 by removing test objdump-reloc-shared.test which stated GNU objdump doesn&...

Hi everyone, we've been prototyping an optimizing assembler for Hexagon for the purpose of updating legacy assembly for new architectures, packet rules, and instruction latencies. It seems like others would be interested in using this and we're looking for any related feedback: has it been attempted before, who's interested, or any general suggestions. We're using the

Dear list, I noticed that the Hexagon disassembler has issues with disassembling some firmwares I have. When tracing one of these problems, the handling of some new-value instructions in HexagonDisassembler::getSingleInstruction() turned out to be the cause, specifically this statement: [lines 384-386 in HexagonDisassembler.cpp in HEAD] else if (SubregBit) // Subreg bit should not be

On Mon, Feb 16, 2015 at 3:53 PM, Chris Lattner <clattner at apple.com> wrote: > > On Feb 6, 2015, at 3:38 PM, David Blaikie <dblaikie at gmail.com> wrote: > > It's an idea been thrown around in a few different threads (including > Rafael's recent > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20141201/247285.html > and Chandler's

I don't want to get into the debate w.r.t. which IR style is better - ask me over beer if you care about my opinions - but as an FYI, there are serious proposals being worked on to introduce some notion of memory def-use edges to help in analysing memory operations. I don't think we've settled on a concrete proposal yet, but I wouldn't be surprised to see something in the

On Tue, Feb 17, 2015 at 10:47 PM, David Blaikie <dblaikie at gmail.com> wrote: > > > On Tue, Feb 17, 2015 at 10:27 PM, Chris Lattner <clattner at apple.com> > wrote: > >> On Feb 17, 2015, at 1:58 PM, Chandler Carruth <chandlerc at gmail.com> >> wrote: >> > I'm not actually worried about this change though Chris, at least >> w.r.t.

One of the things that may taint my prior analysis... At the time I was last evaluating Windows git GUIs, I was looking for something that would make handling .patch and .diff files easier. In particular, if a patch didn't apply, I really wanted to get some visual indication of which hunk failed, and some interface to resolve the conflict. I didn't find any tools that handled that