public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/96591] [8/9/10/11 Regression] ICE with -flto=auto and -O1: tree code ‘typename_type’ is not supported in LTO streams
Date: Sat, 06 Feb 2021 06:20:11 +0000 [thread overview]
Message-ID: <bug-96591-4-Uz8WGRJPYB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96591-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96591
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|c++ |lto
Assignee|jason at gcc dot gnu.org |unassigned at gcc dot gnu.org
Status|ASSIGNED |NEW
--- Comment #5 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Arseny Solokha from comment #4)
> Is it somehow related to PR83997? Maybe even a duplicate?
No, not a duplicate.
Reduced a bit more:
struct builtin_simd
{
using type [[gnu::vector_size(sizeof(scalar_t) * length)]] = scalar_t;
};
struct simd_traits
{
using scalar_type = int;
template <typename X>
using rebind = typename X::type;
};
template <typename simd_t>
constexpr simd_t fill(typename simd_traits::scalar_type const scalar)
{
return simd_t{scalar};
}
using score_type = typename builtin_simd<int, 1>::type;
// Uncommenting this makes it work:
// const simd_traits::scalar_type n = 8;
score_type data[1]{fill<score_type>(8)};
The difference from uncommenting that line seems to be that then
free_lang_data_in_type is called for simd_traits::scalar_type. So the problem
seems to be that find_decls_types isn't finding scalar_type in the vector in
the array. So changing component to LTO and unassigning myself. Feel free to
change it back if it seems appropriate.
next prev parent reply other threads:[~2021-02-06 6:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 15:58 [Bug lto/96591] New: " gcc-bugs at marehr dot dialup.fu-berlin.de
2020-08-12 17:05 ` [Bug lto/96591] " marxin at gcc dot gnu.org
2020-08-25 9:27 ` [Bug c++/96591] [8/9/10/11 Regression] " rguenth at gcc dot gnu.org
2020-08-25 12:12 ` jakub at gcc dot gnu.org
2020-08-26 5:20 ` asolokha at gmx dot com
2020-10-12 12:34 ` rguenth at gcc dot gnu.org
2021-02-04 21:03 ` jason at gcc dot gnu.org
2021-02-06 6:20 ` jason at gcc dot gnu.org [this message]
2021-02-08 7:47 ` [Bug lto/96591] " rguenth at gcc dot gnu.org
2021-02-08 8:45 ` rguenth at gcc dot gnu.org
2021-02-08 12:05 ` cvs-commit at gcc dot gnu.org
2021-02-08 12:06 ` [Bug lto/96591] [8/9/10 " rguenth at gcc dot gnu.org
2021-03-24 14:26 ` cvs-commit at gcc dot gnu.org
2021-04-12 11:23 ` [Bug lto/96591] [8/9 " cvs-commit at gcc dot gnu.org
2021-04-26 10:46 ` [Bug lto/96591] [8 " cvs-commit at gcc dot gnu.org
2021-04-26 10:48 ` rguenth 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-96591-4-Uz8WGRJPYB@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).