From: Florian Weimer <fweimer@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] libgcc: Mostly vectorize CIE encoding extraction for FDEs
Date: Mon, 17 Oct 2022 15:07:11 +0200 [thread overview]
Message-ID: <87a65umwe8.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <mvmv8oibo0s.fsf@suse.de> (Andreas Schwab's message of "Mon, 17 Oct 2022 15:03:31 +0200")
* Andreas Schwab:
> On Okt 17 2022, Florian Weimer via Libc-alpha wrote:
>
>> + unsigned long long value = *(const unsigned long long *) &cie->version;
>
> Is that strict-aliasing safe?
Should be, the data is never written to during the program's life-time.
libgcc doesn't use memcpy consistently for reading this constant data.
Instead it uses non-char types to read things.
> I guess you wanted to send that to gcc-patches@.
Right.
Thanks,
Florian
prev parent reply other threads:[~2022-10-17 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 12:36 Florian Weimer
2022-10-17 13:00 ` Florian Weimer
2022-10-17 13:03 ` Andreas Schwab
2022-10-17 13:07 ` Florian Weimer [this message]
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=87a65umwe8.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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).