public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/108973] New: Sufficiently narrow terminal window causes selftest failure
Date: Tue, 28 Feb 2023 17:12:42 +0000	[thread overview]
Message-ID: <bug-108973-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 108973
           Summary: Sufficiently narrow terminal window causes selftest
                    failure
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
          Assignee: unassigned at gcc dot gnu.org
          Reporter: acoplan at gcc dot gnu.org
  Target Milestone: ---

Running the selftests in a sufficiently-narrow terminal window (in my case
$COLUMNS < 42) causes the following selftest failure:

$ echo $COLUMNS
41
$ ./xgcc -B . -c -xc /dev/null
-fself-test=$HOME/toolchain/src/gcc/gcc/testsuite/selftests
/home/alecop01/toolchain/src/gcc/gcc/diagnostic-show-locus.cc:4452:
test_add_location_if_nearby: FAIL: ASSERT_STREQ (" struct same_line { double x;
double y; ;\n" "                  ~                    ^\n", pp_formatted_text
(dc.printer))
 val1=" struct same_line { double x; double y; ;
                  ~                    ^
"
 val2=" truct same_line { double x; double y; ;
                 ~                    ^

"

cc1: internal compiler error: in fail_formatted, at selftest.cc:63
0x2b02675 selftest::fail_formatted(selftest::location const&, char const*, ...)
        /home/alecop01/toolchain/src/gcc/gcc/selftest.cc:63
0x2b02764 selftest::assert_streq(selftest::location const&, char const*, char
const*, char const*, char const*)
        /home/alecop01/toolchain/src/gcc/gcc/selftest.cc:92
0x2b24547 test_add_location_if_nearby
        /home/alecop01/toolchain/src/gcc/gcc/diagnostic-show-locus.cc:4450
0x2b51737 selftest::for_each_line_table_case(void (*)(selftest::line_table_case
const&))
        /home/alecop01/toolchain/src/gcc/gcc/input.cc:3899
0x2b2bf52 selftest::diagnostic_show_locus_cc_tests()
        /home/alecop01/toolchain/src/gcc/gcc/diagnostic-show-locus.cc:5706
0x29c8f24 selftest::run_tests()
        /home/alecop01/toolchain/src/gcc/gcc/selftest-run-tests.cc:96
0x15d19c4 toplev::run_self_tests()
        /home/alecop01/toolchain/src/gcc/gcc/toplev.cc:2184
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

             reply	other threads:[~2023-02-28 17:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 17:12 acoplan at gcc dot gnu.org [this message]
2023-03-01 21:21 ` [Bug testsuite/108973] " pinskia at gcc dot gnu.org
2023-03-01 21:22 ` [Bug testsuite/108973] [13 Regression] " pinskia at gcc dot gnu.org
2023-03-02  8:47 ` jakub at gcc dot gnu.org
2023-03-02  9:10 ` jakub at gcc dot gnu.org
2023-03-02 15:23 ` marxin at gcc dot gnu.org
2023-03-04  8:49 ` cvs-commit at gcc dot gnu.org
2023-03-04  9:29 ` [Bug testsuite/108973] [10/11/12 " jakub at gcc dot gnu.org
2023-03-19  5:30 ` cvs-commit at gcc dot gnu.org
2023-03-20 10:29 ` [Bug testsuite/108973] [10/11 " jakub at gcc dot gnu.org
2023-05-02 20:15 ` cvs-commit at gcc dot gnu.org
2023-05-03 10:42 ` [Bug testsuite/108973] [10 " jakub at gcc dot gnu.org
2023-05-03 15:22 ` cvs-commit at gcc dot gnu.org
2023-05-04  7:25 ` jakub 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-108973-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).