On 04/28/2016 12:35 PM, Peter Foley wrote: > On Thu, Apr 28, 2016 at 1:19 PM, Sunny Shah <ssu...@cs.wisc.edu> wrote: >> Peter, >> >> The XML files are not publicly available - they're accessible to a very >> small group of people at UW. >> >> Thanks, >> Sunny > > Ok. Maybe you should add a comment to the script to that effect? > I was planning on refactoring the script to split up buildInsnTable() > and buildDecoderTable(). > But if I don't have access to the input files, it's rather hard to test. > > See the below issues for the rationale. > > In file included from > /home/peter/dyninst/instructionAPI/src/InstructionDecoder-aarch64.C:2792:0: > /home/peter/dyninst/instructionAPI/src/aarch64_opcode_tables.C: In > static member function ‘static void > Dyninst::InstructionAPI::aarch64_insn_entry::buildInsnTable()’: > /home/peter/dyninst/instructionAPI/src/aarch64_opcode_tables.C:39:6: > note: variable tracking size limit exceeded with > -fvar-tracking-assignments, retrying without > void aarch64_insn_entry::buildInsnTable() > ^ > In file included from > /home/peter/dyninst/instructionAPI/src/InstructionDecoder-aarch64.C:2792:0: > /home/peter/dyninst/instructionAPI/src/aarch64_opcode_tables.C: In > static member function ‘static void > Dyninst::InstructionAPI::aarch64_mask_entry::buildDecoderTable()’: > /home/peter/dyninst/instructionAPI/src/aarch64_opcode_tables.C:777:6: > note: variable tracking size limit exceeded with > -fvar-tracking-assignments, retrying without > void aarch64_mask_entry::buildDecoderTable() > ^
FWIW, VTA only has an affect on the debuginfo quality for these functions. The actual code generation should be unchanged. _______________________________________________ Dyninst-api mailing list Dyninst-api@cs.wisc.edu https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api
