From: Jason Merrill <jason@redhat.com>
To: Ben Boeckel <ben.boeckel@kitware.com>
Cc: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
nathan@acm.org, fortran@gcc.gnu.org, gcc@gcc.gnu.org,
brad.king@kitware.com
Subject: Re: [PATCH v6 0/4] P1689R5 support
Date: Fri, 16 Jun 2023 23:55:53 -0400 [thread overview]
Message-ID: <CADzB+2=ELt05EO=MV5hRFuf=fvEaCyo-cq4_o2kjsZCRGOwVUQ@mail.gmail.com> (raw)
In-Reply-To: <20230616194856.GA24524@farprobe>
On Fri, Jun 16, 2023 at 3:49 PM Ben Boeckel <ben.boeckel@kitware.com> wrote:
>
> On Thu, Jun 08, 2023 at 21:59:13 +0400, Maxim Kuvyrkov wrote:
> > This patch series causes ICEs on arm-linux-gnueabihf. Would you
> > please investigate? Please let me know if you need any in reproducing
> > these.
>
> Finally back at it. I tried on aarch64, but wasn't able to reproduce the
> errors (alas, it is probably a 32bit thing…let me try with `-m32`). Is
> there hardware I can access to try this out on the same target triple?
>
> Alternatively, a backtrace may be able to help pinpoint it enough if you
> have the cycles.
I see the same thing with patch 4 on x86_64-pc-linux-gnu, e.g.
FAIL: g++.dg/modules/ben-1_a.C -std=c++17 (test for excess errors)
Excess errors:
/home/jason/gt/gcc/testsuite/g++.dg/modules/ben-1_a.C:9:1: internal
compiler error: Segmentation fault
0x19e2f3c crash_signal
/home/jason/gt/gcc/toplev.cc:314
0x340f3f8 mkdeps::vec<mkdeps::velt>::size() const
/home/jason/gt/libcpp/mkdeps.cc:57
0x340dc1f apply_vpath
/home/jason/gt/libcpp/mkdeps.cc:194
0x340e08e deps_add_dep(mkdeps*, char const*)
/home/jason/gt/libcpp/mkdeps.cc:318
0xea7b51 module_client::open_module_client(unsigned int, char const*,
mkdeps*, void (*)(char const*), char const*)
/home/jason/gt/gcc/cp/mapper-client.cc:291
0xef2ba8 make_mapper
/home/jason/gt/gcc/cp/module.cc:14042
0xf0896c get_mapper(unsigned int, mkdeps*)
/home/jason/gt/gcc/cp/module.cc:3977
0xf032ac name_pending_imports
/home/jason/gt/gcc/cp/module.cc:19623
0xf03a7d preprocessed_module(cpp_reader*)
/home/jason/gt/gcc/cp/module.cc:19817
0xe85104 module_token_cdtor(cpp_reader*, unsigned long)
/home/jason/gt/gcc/cp/lex.cc:548
0xf467b2 cp_lexer_new_main
/home/jason/gt/gcc/cp/parser.cc:756
0xfc1e3a c_parse_file()
/home/jason/gt/gcc/cp/parser.cc:49725
0x11c5bf5 c_common_parse_file()
/home/jason/gt/gcc/c-family/c-opts.cc:1268
next prev parent reply other threads:[~2023-06-17 3:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 20:50 Ben Boeckel
2023-06-06 20:50 ` [PATCH v6 1/4] libcpp: reject codepoints above 0x10FFFF Ben Boeckel
2023-06-19 21:34 ` Jason Merrill
2023-06-20 19:16 ` Damien Guibouret
2023-06-20 19:49 ` Ben Boeckel
2023-06-06 20:50 ` [PATCH v6 2/4] p1689r5: initial support Ben Boeckel
2023-06-06 20:50 ` [PATCH v6 3/4] c++modules: report imported CMI files as dependencies Ben Boeckel
2023-06-06 20:50 ` [PATCH v6 4/4] c++modules: report module mapper files as a dependency Ben Boeckel
2023-06-08 17:59 ` [PATCH v6 0/4] P1689R5 support Maxim Kuvyrkov
2023-06-16 19:48 ` Ben Boeckel
2023-06-16 23:15 ` Ben Boeckel
2023-06-17 3:55 ` Jason Merrill [this message]
2023-06-17 14:43 ` Ben Boeckel
2023-06-20 0:54 ` Jason Merrill
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='CADzB+2=ELt05EO=MV5hRFuf=fvEaCyo-cq4_o2kjsZCRGOwVUQ@mail.gmail.com' \
--to=jason@redhat.com \
--cc=ben.boeckel@kitware.com \
--cc=brad.king@kitware.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=nathan@acm.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).