public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/45983] ICE: tree code 'template_parm_index' is not supported in gimple streams with -lto Date: Tue, 12 Oct 2010 14:24:00 -0000 [thread overview] Message-ID: <20101012142400.28rAualXLTlaEWzvSuXXrd3qUMlCMAvgTPQyD54JLmo@z> (raw) In-Reply-To: <bug-45983-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45983 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2010.10.12 14:24:28 CC| |rguenth at gcc dot gnu.org Ever Confirmed|0 |1 --- Comment #7 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-10-12 14:24:28 UTC --- Reduced testcase for the LTO problem: typedef long unsigned int size_t; enum { chunk_size = 16, max_channels = 16 }; struct float4_t { }; template<size_t NumChans> class chunk_array_t { typedef float4_t value_type_t; typedef float scalar_type_t; typedef value_type_t value_array_t[chunk_size/4]; typedef scalar_type_t scalar_array_t[chunk_size]; value_array_t m[NumChans]; const scalar_array_t &decay(size_t c) const; }; template<size_t capacity> struct bitboard_t { struct scanner_t { scanner_t(const bitboard_t &b); size_t index() const; }; }; enum params_enum_t { PRM_VOL = 0, PRM_PAN, PRM_BND, PRM_MOD }; class midi_channels_params_t { float vals[4][max_channels]; public: template<params_enum_t p> float get_value(size_t cha) const { return vals[p][cha]; } }; class synth_t { typedef bitboard_t<max_channels> bb_channels_t; struct states_t { bb_channels_t mask_active_channels; }; midi_channels_params_t &channel_params; states_t &states; void output_audio(void); }; void synth_t::output_audio(void) { const bb_channels_t m(states.mask_active_channels); bb_channels_t::scanner_t cscan(m); const size_t chan = cscan.index(); float chan_vol = channel_params.get_value<PRM_VOL>(chan); }
next prev parent reply other threads:[~2010-10-12 14:24 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-12 12:14 [Bug c++/45983] New: " tbptbp at gmail dot com 2010-10-12 13:10 ` [Bug c++/45983] " rguenth at gcc dot gnu.org 2010-10-12 13:22 ` rguenth at gcc dot gnu.org 2010-10-12 13:27 ` tbptbp at gmail dot com 2010-10-12 13:31 ` tbptbp at gmail dot com 2010-10-12 13:49 ` rguenth at gcc dot gnu.org 2010-10-12 13:56 ` tbptbp at gmail dot com 2010-10-12 14:24 ` rguenth at gcc dot gnu.org [this message] 2010-10-12 14:55 ` rguenth at gcc dot gnu.org 2010-10-15 15:05 ` rguenth at gcc dot gnu.org 2010-10-15 15:22 ` rguenth at gcc dot gnu.org 2010-10-15 15:27 ` rguenth at gcc dot gnu.org 2010-10-15 15:29 ` [Bug c++/45983] [4.5/4.6 Regression] " rguenth at gcc dot gnu.org 2010-10-15 21:15 ` jason at gcc dot gnu.org 2010-10-15 21:49 ` tbptbp at gmail dot com 2010-10-18 15:45 ` [Bug c++/45983] [4.5 " rguenth at gcc dot gnu.org 2010-10-20 15:05 ` jason at gcc dot gnu.org 2010-11-12 14:34 ` 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=20101012142400.28rAualXLTlaEWzvSuXXrd3qUMlCMAvgTPQyD54JLmo@z \ --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: linkBe 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).