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 c++/98531] New: g++.dg/modules/xtreme-header-2_a.H etc. FAIL
Date: Tue, 05 Jan 2021 13:00:32 +0000	[thread overview]
Message-ID: <bug-98531-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 98531
           Summary: g++.dg/modules/xtreme-header-2_a.H etc. FAIL
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ro at gcc dot gnu.org
                CC: nathan at gcc dot gnu.org
  Target Milestone: ---
            Target: i386-pc-solaris2.11, sparc-sun-solaris2.11,
                    i586-unknown-freebsd11.4, x86_64-unknown-freebsd11.4

Created attachment 49887
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49887&action=edit
i386-pc-solaris2.11 32-bit xtreme-header-2_a.ii

Several of the new modules tests FAIL on Solaris/x86, Solaris/SPARC, and
FreeBSD,
e.g.

+FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2a (internal compiler error)
+FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2a (test for excess errors)

Excess errors:
/vol/gcc/src/hg/master/local/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H:
internal compiler error: in tree_node, at cp/module.cc:9125
0x8cdfc7f trees_out::tree_node(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:9125
0x8cc9fbe trees_out::core_vals(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:6007
0x8ccd34f trees_out::tree_node_vals(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:7141
0x8ccd34f trees_out::tree_value(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:8956
0x8cc93ce trees_out::tree_node(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:9154
0x8cc9fbe trees_out::core_vals(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:6007
0x8ccd34f trees_out::tree_node_vals(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:7141
0x8ccd34f trees_out::tree_value(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:8956
0x8cc93ce trees_out::tree_node(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:9154
0x8cc9fbe trees_out::core_vals(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:6007
0x8ccd34f trees_out::tree_node_vals(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:7141
0x8ccd34f trees_out::tree_value(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:8956
0x8cc93ce trees_out::tree_node(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:9154
0x8cc9fbe trees_out::core_vals(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:6007
0x8ccd34f trees_out::tree_node_vals(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:7141
0x8ccd34f trees_out::tree_value(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:8956
0x8cc93ce trees_out::tree_node(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:9154
0x8cc9fbe trees_out::core_vals(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:6007
0x8ccd34f trees_out::tree_node_vals(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:7141
0x8ccd34f trees_out::tree_value(tree_node*)
        /vol/gcc/src/hg/master/local/gcc/cp/module.cc:8956

+FAIL: g++.dg/modules/xtreme-header-2_a.H module-cmi 
(gcm.cache/vol/gcc/src/hg/master/local/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H.gcm)

  must not use absolute filename here

+FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++2a (test for excess errors)

Excess errors:
/vol/gcc/src/hg/master/local/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H:
error: failed to read compiled module: No such file or directory
/vol/gcc/src/hg/master/local/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H:
fatal error: returning to the gate for a mechanical issue
compilation terminated.

+FAIL: g++.dg/modules/xtreme-header-2_c.C -std=c++2a (test for excess errors)

The same failure happens for 

+FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++2a (internal compiler error)
+FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++2a (test for excess errors)
+FAIL: g++.dg/modules/xtreme-header-5_a.H module-cmi 
(gcm.cache/vol/gcc/src/hg/master/local/gcc/testsuite/g++.dg/modules/xtreme-header-5_a.H.gcm)
+FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++2a (test for excess errors)
+FAIL: g++.dg/modules/xtreme-header-5_c.C -std=c++2a (test for excess errors)

+FAIL: g++.dg/modules/xtreme-header-6_a.H -std=c++2a (internal compiler error)
+FAIL: g++.dg/modules/xtreme-header-6_a.H -std=c++2a (test for excess errors)
+FAIL: g++.dg/modules/xtreme-header-6_a.H module-cmi 
(gcm.cache/vol/gcc/src/hg/master/local/gcc/testsuite/g++.dg/modules/xtreme-header-6_a.H.gcm)
+FAIL: g++.dg/modules/xtreme-header-6_b.C -std=c++2a (test for excess errors)
+FAIL: g++.dg/modules/xtreme-header-6_c.C -std=c++2a (test for excess errors)

+FAIL: g++.dg/modules/xtreme-header_a.H -std=c++2a (internal compiler error)
+FAIL: g++.dg/modules/xtreme-header_a.H -std=c++2a (test for excess errors)
+FAIL: g++.dg/modules/xtreme-header_a.H module-cmi 
(gcm.cache/vol/gcc/src/hg/master/local/gcc/testsuite/g++.dg/modules/xtreme-header_a.H.gcm)

+FAIL: g++.dg/modules/xtreme-header_b.C -std=c++2a (test for excess errors)
+FAIL: g++.dg/modules/xtreme-tr1_a.H -std=c++2a (internal compiler error)
+FAIL: g++.dg/modules/xtreme-tr1_a.H -std=c++2a (test for excess errors)
+FAIL: g++.dg/modules/xtreme-tr1_a.H module-cmi 
(gcm.cache/vol/gcc/src/hg/master/local/gcc/testsuite/g++.dg/modules/xtreme-tr1_a.H.gcm)
+FAIL: g++.dg/modules/xtreme-tr1_b.C -std=c++2a (test for excess errors)

However, with -std=c++17 the tests PASS.

The failure can be reproduced for the first test with

$ cc1plus -fpreprocessed xtreme-header-2_a.ii -quiet -std=c++20 -fmodule-header
-o xtreme-header-2_a.s

and the attached .ii file.

             reply	other threads:[~2021-01-05 13:00 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 13:00 ro at gcc dot gnu.org [this message]
2021-01-05 13:00 ` [Bug c++/98531] " ro at gcc dot gnu.org
2021-01-05 13:57 ` nathan at gcc dot gnu.org
2021-01-05 14:00 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-01-05 14:08 ` nathan at gcc dot gnu.org
2021-01-19 15:13 ` [Bug c++/98531] [11 Regression] " iains at gcc dot gnu.org
2021-01-21 16:52 ` nathan at gcc dot gnu.org
2021-01-22 13:22 ` nathan at gcc dot gnu.org
2021-01-27 13:30 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-01-27 13:36 ` nathan at acm dot org
2021-02-01 12:36 ` ro at gcc dot gnu.org
2021-02-02 20:55 ` nathan at gcc dot gnu.org
2021-02-08 17:24 ` cvs-commit at gcc dot gnu.org
2021-02-08 17:36 ` nathan at gcc dot gnu.org
2021-02-16  8:41 ` iains at gcc dot gnu.org
2021-04-27 11:40 ` [Bug c++/98531] [modules] " jakub at gcc dot gnu.org
2021-07-28  7:05 ` rguenth at gcc dot gnu.org
2022-04-21  7:48 ` rguenth at gcc dot gnu.org
2023-04-02 15:01 ` danglin at gcc dot gnu.org
2023-04-02 15:23 ` danglin at gcc dot gnu.org
2023-05-29 10:03 ` jakub at gcc dot gnu.org
2023-12-06 16:09 ` danglin at gcc dot gnu.org
2024-02-11 18:27 ` danglin at gcc dot gnu.org
2024-02-11 18:34 ` pinskia at gcc dot gnu.org
2024-02-11 18:35 ` pinskia at gcc dot gnu.org
2024-02-11 18:51 ` danglin 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-98531-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).