This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Generate annotations for a binary translator
- From: ééä <chenwj at iis dot sinica dot edu dot tw>
- To: gcc at gcc dot gnu dot org
- Date: Fri, 17 Jun 2011 09:48:33 +0800
- Subject: Re: Generate annotations for a binary translator
- References: <20110512094304.GA60454@cs.nctu.edu.tw> <mcr7h9va1ta.fsf@coign.corp.google.com> <20110513033505.GA79308@cs.nctu.edu.tw> <mcrtycz8aaa.fsf@coign.corp.google.com> <20110516085156.GA67683@cs.nctu.edu.tw> <mcrei3y4cmh.fsf@coign.corp.google.com> <20110517053946.GA99002@cs.nctu.edu.tw> <mcrzkmlzur7.fsf@coign.corp.google.com>
> But where do you want that information to be at runtime?
>
> The hard part is not getting the information at compile time. The
> information is readily available after register allocation. Heck, you
> can see right in the dump files; e.g., use -da when you compile and look
> at the pro_and_epilogue dump file.
>
> The hard part is getting that information to be available at runtime.
Recently I have read about GCC LTO. Somehow I feel there are some
similarities between what LTO does and what I want to do. The major
difference between them is LTO dump GIMPLE bytecode into the object
file, and what I (binary translator) want is not so high-level
information.
Regards,
chenwj
--
Wei-Ren Chen (ééä)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667