public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113706] New: c-c++-common/pr103798-2.c FAILs as C++
Date: Thu, 01 Feb 2024 15:52:58 +0000 [thread overview]
Message-ID: <bug-113706-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113706
Bug ID: 113706
Summary: c-c++-common/pr103798-2.c FAILs as C++
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: hjl.tools at gmail dot com
Target Milestone: ---
Target: i386-pc-solaris2.11, amd64-pc-solaris2.11,
sparc*-sun-solaris2.11, pru-unknown-elf
The c-c++-common/pr103798-2.c test FAILs when compiled as C++ on Solaris/SPARC
and x86, 32 and 64-bit:
FAIL: c-c++-common/pr103798-2.c -std=gnu++14 scan-assembler-not memchr
FAIL: c-c++-common/pr103798-2.c -std=gnu++17 scan-assembler-not memchr
FAIL: c-c++-common/pr103798-2.c -std=gnu++20 scan-assembler-not memchr
FAIL: c-c++-common/pr103798-2.c -std=gnu++98 scan-assembler-not memchr
Similar failures are seen on gcc-testresults posting for PRU.
next reply other threads:[~2024-02-01 15:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 15:52 ro at gcc dot gnu.org [this message]
2024-02-01 15:54 ` [Bug tree-optimization/113706] " ro at gcc dot gnu.org
2024-02-01 15:55 ` ro at gcc dot gnu.org
2024-02-01 15:55 ` ro at gcc dot gnu.org
2024-02-01 16:58 ` hjl.tools at gmail dot com
2024-02-02 9:19 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-02-02 15:24 ` ro at gcc dot gnu.org
2024-02-13 10:30 ` ro at gcc dot gnu.org
2024-02-13 18:22 ` [Bug c++/113706] " jason at gcc dot gnu.org
2024-02-14 8:25 ` cvs-commit at gcc dot gnu.org
2024-02-14 8:28 ` ro at gcc dot gnu.org
2024-02-14 13:57 ` jason at gcc dot gnu.org
2024-02-14 13:59 ` jason at gcc dot gnu.org
2024-04-18 11:15 ` cvs-commit at gcc dot gnu.org
2024-05-01 15:44 ` cvs-commit at gcc dot gnu.org
2024-05-01 15:47 ` jason at gcc dot gnu.org
2024-05-02 12:46 ` ro at CeBiTec dot Uni-Bielefeld.DE
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-113706-4@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).