public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bviyer at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/60198] ICE with _Cilk_spawn in expression within template function Date: Tue, 18 Feb 2014 14:20:00 -0000 [thread overview] Message-ID: <bug-60198-4-pRnRgPQPyw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60198-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60198 Balaji V. Iyer <bviyer at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bviyer at gmail dot com --- Comment #3 from Balaji V. Iyer <bviyer at gmail dot com> --- (In reply to Sylwester Arabas from comment #2) > Hi, > > I've just got the same error with current Debian's gcc-snapshot (20140212) > when trying to compile a code that uses the Blitz++ library, and after > replacing all "#pragma ivdep" with "#pragma GCC ivdep" in that library... > > /usr/include/blitz/globeval.cc:466:12: internal compiler error: in > tsubst_copy, at cp/pt.c:12887 > for (; i < uneven_start; ++i) > ^ > Please submit a full bug report, > with preprocessed source if appropriate. > > I can provide more details if needed. Hi Sylwester, The issue with #pragma ivdep is not relevant for this bug. Can you please open another bug report for that and discuss it there? Thanks, Balaji V. Iyer. > > HTH, > Sylwester
next prev parent reply other threads:[~2014-02-18 14:20 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-14 15:35 [Bug c++/60198] New: " reichelt at gcc dot gnu.org 2014-02-14 15:36 ` [Bug c++/60198] " reichelt at gcc dot gnu.org 2014-02-18 10:14 ` slayoo at staszic dot waw.pl 2014-02-18 14:20 ` bviyer at gmail dot com [this message] 2014-02-18 23:00 ` slayoo at staszic dot waw.pl 2015-02-10 6:22 ` pinskia at gcc dot gnu.org 2015-02-10 6:38 ` pinskia at gcc dot gnu.org 2015-05-01 8:37 ` hvdieren at elis dot ugent.be
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-60198-4-pRnRgPQPyw@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: 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).