public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110185] [14 Regression]: Tens of c++ testsuite crashes for cris-elf with r14-1624-g28db36e2cfca1b Date: Fri, 09 Jun 2023 00:50:56 +0000 [thread overview] Message-ID: <bug-110185-4-zYzaVfEUn7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110185-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110185 --- Comment #1 from Hans-Peter Nilsson <hp at gcc dot gnu.org> --- Created attachment 55290 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55290&action=edit spaceship-synth13.ii Hm, that attachment was for a test that checked for errors. Here's one for a tests that should compile without errors, /testsuite/g++.dg/cpp2a/spaceship-synth13.C. Repeat with cc1plus -fpreprocessed spaceship-synth13.ii -melf -quiet -dumpbase spaceship-synth13.C -dumpbase-ext .C -pedantic-errors -Wno-long-long -std=c++20 -version -fdiagnostics-color=never -fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers -fdiagnostics-urls=never -fdiagnostics-path-format=separate-events -fmessage-length=0 -o spaceship-synth13.s
next prev parent reply other threads:[~2023-06-09 0:50 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-09 0:36 [Bug c++/110185] New: " hp at gcc dot gnu.org 2023-06-09 0:50 ` hp at gcc dot gnu.org [this message] 2023-06-09 7:42 ` [Bug c++/110185] " rguenth at gcc dot gnu.org 2023-06-09 10:01 ` ro at gcc dot gnu.org 2023-06-09 14:25 ` jason at gcc dot gnu.org 2023-06-09 15:42 ` cvs-commit at gcc dot gnu.org 2023-06-09 15:42 ` jason 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-110185-4-zYzaVfEUn7@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).