public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nick.tomlinson at arm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/59053] cilkplus branch compiler loops Date: Wed, 30 Jul 2014 11:07:00 -0000 [thread overview] Message-ID: <bug-59053-4-5LqJ21YaBd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59053-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59053 Nick Tomlinson <nick.tomlinson at arm dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nick.tomlinson at arm dot com --- Comment #5 from Nick Tomlinson <nick.tomlinson at arm dot com> --- Possibly related to: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61962 The reproducer attached to that bug (see below) also enters an infinite loop (build with g++ -fcilkplus -c arrayinf.cpp): struct FloatStruct { float *f; }; /* Either SRC or DST must be a struct, otherwise the bug does not occur. */ void f (FloatStruct *dst, float *src, unsigned int length) { dst->f[0:length] = src[0:length]; }
next prev parent reply other threads:[~2014-07-30 11:07 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-59053-4@http.gcc.gnu.org/bugzilla/> 2013-11-08 19:10 ` hjl.tools at gmail dot com 2013-11-08 21:59 ` john.forrest at fastercoin dot com 2014-04-22 11:36 ` jakub at gcc dot gnu.org 2014-07-16 13:30 ` jakub at gcc dot gnu.org 2014-07-30 11:07 ` nick.tomlinson at arm dot com [this message] 2014-10-30 10:40 ` jakub at gcc dot gnu.org 2015-06-26 20:17 ` jakub at gcc dot gnu.org 2015-06-26 20:38 ` jakub at gcc dot gnu.org 2015-06-26 21:19 ` pinskia 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-59053-4-5LqJ21YaBd@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).