public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manuel.lauss at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108071] [13 regression] Build failure in Libreoffice Date: Mon, 12 Dec 2022 12:21:23 +0000 [thread overview] Message-ID: <bug-108071-4-4TZNBN5meL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108071-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108071 --- Comment #2 from Manuel Lauss <manuel.lauss at googlemail dot com> --- (In reply to Richard Biener from comment #1) I get the same errors, but the whole file can be compiled without errors with gcc-12 (it needs to be preprocessed with gcc-12 as well), and with a gcc-13 checkout from 9 days ago. So in the last 9 days, something was introduced which caused these errors to appear.
next prev parent reply other threads:[~2022-12-12 12:21 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-12 10:30 [Bug c++/108071] New: 13 regression: " manuel.lauss at googlemail dot com 2022-12-12 12:07 ` [Bug c++/108071] [13 regression] " rguenth at gcc dot gnu.org 2022-12-12 12:21 ` manuel.lauss at googlemail dot com [this message] 2022-12-12 12:40 ` [Bug c++/108071] [13 Regression] Build failure in Libreoffice since r13-4565 jakub at gcc dot gnu.org 2022-12-12 12:54 ` jakub at gcc dot gnu.org 2022-12-12 13:02 ` redi at gcc dot gnu.org 2022-12-12 13:05 ` redi at gcc dot gnu.org 2022-12-12 13:53 ` slyfox at gcc dot gnu.org 2022-12-12 13:54 ` slyfox at gcc dot gnu.org 2022-12-12 16:10 ` jason at gcc dot gnu.org 2022-12-12 22:47 ` jason at gcc dot gnu.org 2022-12-15 5:26 ` cvs-commit at gcc dot gnu.org
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-108071-4-4TZNBN5meL@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: linkBe 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).