This is the mail archive of the
mailing list for the GCC project.
Re: Compiler support for erasure of sensitive data
- From: Marcos DÃaz <marcos dot diaz at tallertechnologies dot com>
- To: Segher Boessenkool <segher at kernel dot crashing dot org>
- Cc: Andres Tiraboschi <andres dot tiraboschi at tallertechnologies dot com>, Richard Biener <richard dot guenther at gmail dot com>, Zack Weinberg <zackw at panix dot com>, GCC Development <gcc at gcc dot gnu dot org>, Daniel Gutson <daniel dot gutson at tallertechnologies dot com>
- Date: Tue, 15 Mar 2016 12:21:39 -0300
- 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> <20160309170921 dot GA1344 at gate dot crashing dot org>
On Wed, Mar 9, 2016 at 2:09 PM, Segher Boessenkool
> [ 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.
Hi, we attached a patch in:
Please take a look!