public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gavin Ray <ray.gavin97@gmail.com>
To: gcc@gcc.gnu.org
Subject: Bug with GCC's handling of lifetimes of implicit-lifetime types
Date: Sat, 10 Dec 2022 12:41:13 -0500	[thread overview]
Message-ID: <CAFtvWZPMecnFV3gWDU654Gmt+0ssFfxx88p_cuGhLEE+pKB-gQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

This came up when I was asking around about what the proper way was to:

- Allocate aligned storage for a buffer pool/page cache
- Then create pointers to "Page" structs inside of the storage memory area

I thought something like this might do:

struct buffer_pool
{
  alignas(PAGE_SIZE) std::byte storage[NUM_PAGES * PAGE_SIZE];
  page* pages = new (storage) page[NUM_PAGES];
}

Someone told me that this was a valid solution but not to do it, because it
wouldn't function properly on GCC
They gave this as a reproduction:

https://godbolt.org/z/EhzM37Gzh

I'm not experienced enough with C++ to grok the connection between this
repro and my code, but I figured
I'd post it on the mailing list in case it was useful for others/might get
fixed in the future =)

They said it had to do with "handling of lifetimes of implicit-lifetime
types"

             reply	other threads:[~2022-12-10 17:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10 17:41 Gavin Ray [this message]
2022-12-10 18:35 ` Jonathan Wakely
2022-12-10 18:43   ` Andrew Pinski
2022-12-10 21:48     ` Gavin Ray
2022-12-11  9:11     ` Richard Biener
2022-12-11 12:02       ` Jonathan Wakely
2022-12-11 13:31         ` Richard Biener
2022-12-11 13:38           ` Gavin Ray
2022-12-11 13:44             ` Gavin Ray
2022-12-12 11:56               ` Jonathan Wakely

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=CAFtvWZPMecnFV3gWDU654Gmt+0ssFfxx88p_cuGhLEE+pKB-gQ@mail.gmail.com \
    --to=ray.gavin97@gmail.com \
    --cc=gcc@gcc.gnu.org \
    /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).