This is the mail archive of the
mailing list for the GCC project.
Re: how to tweak x86 code generation to instrument certain opcodes with CC trap?
- From: Stefan Ring <stefanrin at gmail dot com>
- To: Yasser Shalabi <yassershalabi at gmail dot com>
- Cc: William Cohen <wcohen at redhat dot com>, gcc at gcc dot gnu dot org
- Date: Tue, 27 Oct 2015 11:12:17 +0100
- Subject: Re: how to tweak x86 code generation to instrument certain opcodes with CC trap?
- Authentication-results: sourceware.org; auth=none
- References: <CACkfA5s-k4kP7hM6FarVMEc-eREn2pGwQr+=sVsf3LRaxjG_ug at mail dot gmail dot com> <562A5309 dot 8060302 at redhat dot com> <CACkfA5tS=+YNRi1fk6UoJe_zeGoDOEJ7FttZBLEektTUL2HC0w at mail dot gmail dot com> <562A55BE dot 7080700 at redhat dot com> <CACkfA5tb60+HaRo6Y3us3aFs46LFSMODwr_vWpxUgss1PVfZjQ at mail dot gmail dot com>
On Mon, Oct 26, 2015 at 8:47 PM, Yasser Shalabi <email@example.com> wrote:
> So back to square one. Any tips on what code/config-files I need to
> modify with to get GCC to emit additional opcodes for certain
Maybe you should try cross-compiling. It looks like you have already
succeeded with the instrumentation, it was just that the generated
code is not in good enough shape to run during the build process. This
should not be an issue with a cross-compilation.