From: Qing Zhao <qing.zhao@oracle.com>
To: Richard Sandiford <richard.sandiford@arm.com>,
Kees cook <keescook@chromium.org>,
Richard Biener <rguenther@suse.de>
Cc: gcc-patches Qing Zhao via <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][version 3]add -ftrivial-auto-var-init and variable attribute "uninitialized" to gcc
Date: Tue, 22 Jun 2021 21:31:58 +0000 [thread overview]
Message-ID: <863F3F50-F44A-466D-8CE8-8CB8B3FBF33E@oracle.com> (raw)
In-Reply-To: <mptv965bw6a.fsf@arm.com>
Okay.
Now, I believe that we agreed on the following:
For this current patch:
1. Use byte-repeatable pattern for pattern-initialization;
2. Use one pattern for all types;
3. Use “0xFE” for the byte pattern value.
Possible future improvement:
1. Type specific patterns if needed;
2. User-specified pattern if needed; (add a new option for user to change the patterns).
3. Make the code generation part a target hook if needed.
Let me know if I miss anything.
Thanks.
Qing
> On Jun 22, 2021, at 1:18 PM, Richard Sandiford <richard.sandiford@arm.com> wrote:
>
> Kees Cook <keescook@chromium.org> writes:
>> On Tue, Jun 22, 2021 at 09:25:57AM +0100, Richard Sandiford wrote:
>>> Kees Cook <keescook@chromium.org> writes:
>>>> On Mon, Jun 21, 2021 at 03:39:45PM +0000, Qing Zhao wrote:
>>>>> So, if “pattern value” is “0xFFFFFFFFFFFFFFFF”, then it’s a valid canonical virtual memory address. However, for most OS, “0xFFFFFFFFFFFFFFFF” should be not in user space.
>>>>>
>>>>> My question is, is “0xFFFFFFFFFFFFFFFFF” good for pointer? Or “0xAAAAAAAAAAAAAAAA” better?
>>>>
>>>> I think 0xFF repeating is fine for this version. Everything else is a
>>>> "nice to have" for the pattern-init, IMO. :)
>>>
>>> Sorry to be awkward, but 0xFF seems worse than 0xAA to me.
>>>
>>> For integer types, all values are valid representations, and we're
>>> relying on the pattern being “obviously” wrong in context. 0xAAAA…
>>> is unlikely to be a correct integer but 0xFFFF… would instead be a
>>> “nice” -1. It would be difficult to tell in a debugger that a -1
>>> came from pattern init rather than a deliberate choice.
>>
>> I can live with 0xAA. On x86_64, this puts it nicely in the middle of
>> the middle of the non-canonical space:
>>
>> 0x800000000000 - 0xffff7fffffffffff
>>
>> The only trouble is with 32-bit, where the value 0xAAAAAAAA is a
>> legitimate allocatable userspace address. If we want some kind-of middle
>> ground, how about 0xFE? That'll be non-canonical on x86_64, and at the
>> high end of the i386 kernel address space.
>
> Sounds good to me FWIW. That'd give float -1.694739530317379e+38
> (suspiciously big even for astrophysics, I hope!) and would still
> look unusual in an integer context.
>
>>> I agree that, all other things being equal, it would be nice to use NaNs
>>> for floats. But relying on wrong numerical values for floats doesn't
>>> seem worse than doing that for integers.
>>>
>>> 0xAA… for float is (if I've got this right) -3.0316488252093987e-13,
>>> which admittedly doesn't stand out as wrong. But I'm not sure we
>>> should sacrifice integer debugging for float debugging here.
>>
>> In some future version type-specific patterns would be a nice improvement,
>> but I don't want that to block getting the zero-init portion landed. :)
>
> Yeah.
>
> Thanks,
> Richard
next prev parent reply other threads:[~2021-06-22 21:32 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 17:16 Qing Zhao
2021-05-25 19:26 ` Qing Zhao
2021-05-26 11:18 ` Richard Biener
2021-05-27 19:44 ` Qing Zhao
2021-06-07 7:48 ` Richard Biener
2021-06-07 16:13 ` Qing Zhao
2021-06-08 7:37 ` Richard Biener
2021-06-08 16:56 ` Kees Cook
2021-06-08 17:32 ` Qing Zhao
2021-06-08 17:36 ` Kees Cook
2021-06-07 23:45 ` Kees Cook
2021-06-08 8:27 ` Richard Biener
2021-05-27 21:42 ` Qing Zhao
2021-06-03 20:14 ` Qing Zhao
2021-06-07 7:50 ` Richard Biener
2021-06-03 20:18 ` Qing Zhao
2021-06-07 7:53 ` Richard Biener
2021-06-07 16:18 ` Qing Zhao
2021-06-07 23:48 ` Kees Cook
2021-06-08 7:41 ` Richard Biener
2021-06-08 15:27 ` Qing Zhao
2021-06-08 16:59 ` Kees Cook
2021-06-08 18:05 ` Qing Zhao
2021-06-11 11:04 ` Richard Biener
2021-06-11 17:14 ` Kees Cook
2021-06-10 21:11 ` Qing Zhao
2021-06-11 11:12 ` Richard Biener
2021-06-11 15:49 ` Qing Zhao
2021-06-11 16:24 ` Kees Cook
2021-06-11 17:00 ` Qing Zhao
2021-06-14 16:10 ` Qing Zhao
2021-06-15 13:21 ` Richard Biener
2021-06-15 21:49 ` Qing Zhao
2021-06-16 6:19 ` Richard Biener
2021-06-16 15:04 ` Qing Zhao
2021-06-16 19:39 ` Qing Zhao
2021-06-18 23:47 ` Kees Cook
2021-06-21 15:39 ` Qing Zhao
2021-06-21 16:18 ` Kees Cook
2021-06-21 17:11 ` Qing Zhao
2021-06-22 8:25 ` Richard Sandiford
2021-06-22 8:59 ` Richard Biener
2021-06-22 13:54 ` Qing Zhao
2021-06-22 14:00 ` Richard Biener
2021-06-22 14:10 ` Qing Zhao
2021-06-22 14:15 ` Richard Biener
2021-06-22 14:33 ` Qing Zhao
2021-06-22 19:04 ` Richard Biener
2021-06-22 17:55 ` Kees Cook
2021-06-22 18:18 ` Richard Sandiford
2021-06-22 21:31 ` Qing Zhao [this message]
2021-06-23 6:05 ` Richard Biener
2021-06-21 7:53 ` Richard Biener
2021-06-21 15:11 ` Qing Zhao
2021-06-21 15:35 ` Richard Biener
2021-06-21 16:13 ` Qing Zhao
2021-06-22 6:24 ` Richard Biener
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=863F3F50-F44A-466D-8CE8-8CB8B3FBF33E@oracle.com \
--to=qing.zhao@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=keescook@chromium.org \
--cc=rguenther@suse.de \
--cc=richard.sandiford@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).