public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michal at sawicz dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/106799] `forming offset [32, 36] is out of the bounds` error with precompiled headers
Date: Thu, 01 Sep 2022 09:57:41 +0000	[thread overview]
Message-ID: <bug-106799-4-y4DuKCITYW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106799-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106799

--- Comment #2 from michal at sawicz dot net ---
@Richard correct, if you skip the precompilation, it compiles fine:

```
$ rm cmake_pch.hxx.gch
$ /usr/bin/g++-12 -I/usr/src/googletest/googlemock/include -O2 -std=c++20
-include cmake_pch.hxx -c tmp.cpp
$
```

  parent reply	other threads:[~2022-09-01  9:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01  8:47 [Bug pch/106799] New: " michal at sawicz dot net
2022-09-01  9:27 ` [Bug pch/106799] " rguenth at gcc dot gnu.org
2022-09-01  9:57 ` michal at sawicz dot net [this message]
2022-10-22  0:24 ` [Bug middle-end/106799] " pinskia at gcc dot gnu.org
2022-10-22 12:27 ` michal at sawicz dot net

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=bug-106799-4-y4DuKCITYW@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).