public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107329] [13 Regression] ICE in gimplify_expr, at gimplify.cc:17118 since r13-2978-g43faf3e5445b5717 Date: Tue, 24 Jan 2023 23:14:30 +0000 [thread overview] Message-ID: <bug-107329-4-4CWabeBZOO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107329-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107329 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:aba6416e95ab4138a0ecab0fd51e7e9329d74a45 commit r13-5337-gaba6416e95ab4138a0ecab0fd51e7e9329d74a45 Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Jan 25 00:12:46 2023 +0100 testsuite: Fix up new51.C test on various targets [PR108533] The test fails on targets where size_t is not unsigned long due to extra diagnostics. As the testcase is tested in C++98 too, I'm not using decltype (sizeof 0) but __SIZE_TYPE__. 2023-01-25 Jakub Jelinek <jakub@redhat.com> PR c++/107329 PR testsuite/108533 * g++.dg/init/new51.C (size_t): New typedef. (RexxClass::operator new, RexxClass::operator delete): Use size_t instead of unsigned long.
prev parent reply other threads:[~2023-01-24 23:14 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-20 8:30 [Bug c++/107329] New: " marxin at gcc dot gnu.org 2022-10-20 8:30 ` [Bug c++/107329] " marxin at gcc dot gnu.org 2022-11-23 12:50 ` marxin at gcc dot gnu.org 2023-01-23 21:35 ` jason at gcc dot gnu.org 2023-01-24 3:26 ` cvs-commit at gcc dot gnu.org 2023-01-24 3:27 ` jason at gcc dot gnu.org 2023-01-24 23:14 ` cvs-commit at gcc dot gnu.org [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=bug-107329-4-4CWabeBZOO@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).