public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/66820] [5/6 Regression] internal compiler error: in get_expr_operands, at tree-ssa-operands.c:910
Date: Fri, 10 Jul 2015 10:26:00 -0000	[thread overview]
Message-ID: <bug-66820-4-7Jrmq0l5oS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66820-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66820

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Jul 10 10:26:19 2015
New Revision: 225661

URL: https://gcc.gnu.org/viewcvs?rev=225661&root=gcc&view=rev
Log:
        PR middle-end/66820
        * gimplify.c (maybe_fold_stmt): Don't fold in ORT_PARALLEL
        or ORT_TASK contexts.
        * omp-low.c (lower_omp): Call fold_stmt even if taskreg_nesting_level
        is non-zero.

        * gcc.dg/gomp/pr66820.c: New test.

Added:
    trunk/gcc/testsuite/gcc.dg/gomp/pr66820.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/gimplify.c
    trunk/gcc/omp-low.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2015-07-10 10:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09  9:47 [Bug libgomp/66820] New: " simon at sconseil dot fr
2015-07-09  9:48 ` [Bug libgomp/66820] " simon at sconseil dot fr
2015-07-09 10:04 ` [Bug libgomp/66820] [5/6 Regression] " mpolacek at gcc dot gnu.org
2015-07-09 10:16 ` [Bug middle-end/66820] " jakub at gcc dot gnu.org
2015-07-09 10:21 ` [Bug middle-end/66820] [5/6 Regression] " mpolacek at gcc dot gnu.org
2015-07-09 14:34 ` jakub at gcc dot gnu.org
2015-07-09 15:14 ` jakub at gcc dot gnu.org
2015-07-10 10:26 ` jakub at gcc dot gnu.org [this message]
2015-07-10 14:14 ` jakub at gcc dot gnu.org
2015-07-10 14:15 ` jakub 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-66820-4-7Jrmq0l5oS@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).