From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org, jwakely@redhat.com
Subject: Re: [PATCH 2/2] Avoid default-initializing auto_vec<T, N> storage, fix vec<vl_embed>
Date: Fri, 24 Feb 2023 12:52:21 +0100 [thread overview]
Message-ID: <Y/ik9apuQUt9MaOd@tucnak> (raw)
In-Reply-To: <20230224114444.7E2CE13246@imap2.suse-dmz.suse.de>
On Fri, Feb 24, 2023 at 12:44:44PM +0100, Richard Biener wrote:
> --- a/gcc/vec.h
> +++ b/gcc/vec.h
> @@ -586,8 +586,8 @@ public:
> unsigned allocated (void) const { return m_vecpfx.m_alloc; }
> unsigned length (void) const { return m_vecpfx.m_num; }
> bool is_empty (void) const { return m_vecpfx.m_num == 0; }
> - T *address (void) { return m_vecdata; }
> - const T *address (void) const { return m_vecdata; }
> + T *address (void) { return reinterpret_cast <T *> (this + 1); }
> + const T *address (void) const { return reinterpret_cast <const T *> (this + 1); }
This is now too long.
> T *begin () { return address (); }
> const T *begin () const { return address (); }
> T *end () { return address () + length (); }
> @@ -631,8 +631,7 @@ public:
>
> /* FIXME - These fields should be private, but we need to cater to
> compilers that have stricter notions of PODness for types. */
> - vec_prefix m_vecpfx;
> - T m_vecdata[1];
> + alignas (T) vec_prefix m_vecpfx;
The comment needs adjustment and down't we need
alignas (T) alignas (vec_prefix) ?
> @@ -1588,7 +1587,7 @@ public:
>
> private:
> vec<T, va_heap, vl_embed> m_auto;
> - T m_data[MAX (N - 1, 1)];
> + alignas(T) unsigned char m_data[sizeof (T) * N];
> };
I still believe you don't need alignas(T) here (and space before (T) ).
Also, I think it needs to be MAX (N, 2) instead of N, because auto_vec
ctors use MAX (N, 2). We could also change all those to MAX (N, 1)
now, but it can't be N because m_data[sizeof (T) * 0] is invalid in
standard C.
Anyway, I wonder if you get the -Werror=stringop-overflow= errors during
bootstrap that I got with my version or not.
Jakub
next prev parent reply other threads:[~2023-02-24 11:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 11:44 Richard Biener
2023-02-24 11:52 ` Jakub Jelinek [this message]
2023-02-24 11:54 ` Jonathan Wakely
2023-02-24 12:13 ` Jakub Jelinek
2023-02-24 12:15 ` Richard Biener
2023-02-24 12:26 ` Jakub Jelinek
2023-02-24 13:22 ` Jakub Jelinek
2023-02-24 13:47 Richard Biener
2023-02-24 14:08 ` Jakub Jelinek
2023-02-24 14:13 ` 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=Y/ik9apuQUt9MaOd@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=rguenther@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).