search for: _jt

Hi there, I've created a bug on llvm: http://www.llvm.org/bugs/show_bug.cgi?id=9582 Basically, ARM, Thumb and data mapping symbols should have been exported in the ELF file, so the linker can work correctly. I can do the change and create some test cases, but I haven't been paying much attention to recent MC developments. Is ArmAsmPrinter the place to change for that, or is there an MC

...MC based printer anymore, so you'll only have to change one place. In particular, have a look at ARMAsmPrinter::EmitInstruction(). There's a big switch statement there for instructions that need any sorts of special handling. From the sounds of things, you'll be interested in the ARM::*_JT (jump table branch) instructions and ARM::CONSTPOOL_ENTRY. These mapping symbols sound very similar to special-purpose assembler directives. Off the cuff, it makes sense to me to do something similar to the MCStreamer::EmitAssemblerFlag() routine. -Jim

Hi I Have a very large dataset that I would like to conduct ANOVA tests on. Im not a very strong programmer so any help would be appreciated. the format is Identifier             A1       A2        B1      B2       C1   C2      Norm1         Norm2 1234                  1        1            NA     NA      4       3        NA               NA 4567                  2        2              4     

...ind of jump table than the one I want. One direction that looks promising to me is to add an intrinsic, something like: declare void @llvm.jump.instr.table.entry(i8*, i8*) The first argument would be the original function (the one that gets jumped to in the table), and the second argument is the _JT function declared but not defined by the pass. Then I can add a custom lowering in each supported architecture that would turn this into a labeled jump instruction something like .globl func_JT func_JT: jmp func at PLT The CFI pass would add a special function that would consist only of the...

On Sat, Feb 15, 2014 at 7:08 PM, Eric Christopher <echristo at gmail.com> wrote: > On Tue, Feb 11, 2014 at 9:46 AM, Tom Roeder <tmroeder at google.com> wrote: >> On Tue, Feb 11, 2014 at 9:12 AM, Reid Kleckner <rnk at google.com> wrote: >>> On Tue, Feb 11, 2014 at 12:28 AM, Richard Osborne <richard at xmos.com> wrote: >>>> >>>>

...looks promising to me is to add an intrinsic, something > > like: > > > > declare void @llvm.jump.instr.table.entry(i8*, i8*) > > > > The first argument would be the original function (the one that gets jumped > > to in the table), and the second argument is the _JT function declared but > > not defined by the pass. > > > > Then I can add a custom lowering in each supported architecture that would > > turn this into a labeled jump instruction something like > > > > .globl func_JT > > func_JT: > > jmp func at...