This is the mail archive of the
mailing list for the GCC project.
Re: Compiler support for erasure of sensitive data
- From: Segher Boessenkool <segher at kernel dot crashing dot org>
- To: Andres Tiraboschi <andres dot tiraboschi at tallertechnologies dot com>
- Cc: Richard Biener <richard dot guenther at gmail dot com>, Marcos Diaz <marcos dot diaz at tallertechnologies dot com>, zackw at panix dot com, GCC Development <gcc at gcc dot gnu dot org>, Daniel Gutson <daniel dot gutson at tallertechnologies dot com>
- Date: Wed, 9 Mar 2016 11:09:22 -0600
- Subject: Re: Compiler support for erasure of sensitive data
- Authentication-results: sourceware.org; auth=none
- References: <55F0653C dot 9010903 at panix dot com> <1456780462-7500-1-git-send-email-marcos dot diaz at tallertechnologies dot com> <CAFiYyc3OTei5Hxt5kL85CsmZ8iVZDcXK1_+KE2LwMDWxg=_bdQ at mail dot gmail dot com> <20160304122341 dot GB20650 at gate dot crashing dot org> <CAJZwELndNYM__gh+cVt5kV2KjHtYowxtLCnL=z66O_wD0X1KOQ at mail dot gmail dot com>
[ Please don't top-post. ]
On Wed, Mar 09, 2016 at 11:23:22AM -0300, Andres Tiraboschi wrote:
> We are developing this feature for x86_64
> I want to see which registers are being used by the current function
> for returning a value or as arguments.
> I traverse the rtl looking for clobbered registers, but I don't know
> how to find which registers are arguments from the current function
> and which are used for storing the return value. How do you suggest to
> do this?
You can probably do something with diddle_return_value.