public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/57032] [4.9/5 Regression]: internal compiler error: Max. number of generated reload insns per insn is achieved (90)
Date: Thu, 09 Apr 2015 19:53:00 -0000	[thread overview]
Message-ID: <bug-57032-4-dKwd6eOd9E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57032-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from Uroš Bizjak <ubizjak at gmail dot com> ---
Created attachment 35282
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35282&action=edit
Preprocessed source for QImode subreg reload problem

$ /space/uros/gcc-build-nobwx/gcc/cc1 -O2 -quiet team.i
/space/homedirs/uros/gcc-svn/trunk/libgomp/team.c: In function
‘gomp_team_start’:
/space/homedirs/uros/gcc-svn/trunk/libgomp/team.c:836:1: internal compiler
error: Max. number of generated reload insns per insn is achieved (90)

 }
 ^
0x1209d580b lra_constraints(bool)
        /space/homedirs/uros/gcc-svn/trunk/gcc/lra-constraints.c:4366
0x1209b5f0b lra(_IO_FILE*)
        /space/homedirs/uros/gcc-svn/trunk/gcc/lra.c:2315
0x12093b4e7 do_reload
        /space/homedirs/uros/gcc-svn/trunk/gcc/ira.c:5418
0x12093bc1f execute
        /space/homedirs/uros/gcc-svn/trunk/gcc/ira.c:5589
Please submit a full bug report,

this problem can also be triggered by a cross from x86_64-linux-gnu.
>From gcc-bugs-return-483206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 09 19:55:26 2015
Return-Path: <gcc-bugs-return-483206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94580 invoked by alias); 9 Apr 2015 19:55:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94506 invoked by uid 55); 9 Apr 2015 19:55:21 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/65691] libgccjit documentation typo in gcc_jit_context_one
Date: Thu, 09 Apr 2015 19:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: jit
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65691-4-wD89ctmkqN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65691-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65691-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-04/txt/msg00758.txt.bz2
Content-length: 816

https://gcc.gnu.org/bugzilla/show_bug.cgi?ide691

--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Author: dmalcolm
Date: Thu Apr  9 19:54:49 2015
New Revision: 221959

URL: https://gcc.gnu.org/viewcvs?rev"1959&root=gcc&view=rev
Log:
PR jit/65691: Fix copy&paste error in docs

gcc/jit/ChangeLog:
    PR jit/65691
    * docs/cp/topics/expressions.rst (Simple expressions): Fix copy
    and paste error in description of gccjit::context::one.
    * docs/topics/expressions.rst (Simple expressions): Likewise in
    description of gcc_jit_context_one.
    * docs/_build/texinfo/libgccjit.texi: Regenerate.


Modified:
    trunk/gcc/jit/ChangeLog
    trunk/gcc/jit/docs/_build/texinfo/libgccjit.texi
    trunk/gcc/jit/docs/cp/topics/expressions.rst
    trunk/gcc/jit/docs/topics/expressions.rst


  parent reply	other threads:[~2015-04-09 19:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 14:35 [Bug rtl-optimization/57032] New: [4.9 " ubizjak at gmail dot com
2013-04-22 15:20 ` [Bug rtl-optimization/57032] " ubizjak at gmail dot com
2013-04-22 17:22 ` ubizjak at gmail dot com
2013-04-22 21:00 ` ubizjak at gmail dot com
2013-11-22 10:46 ` rguenth at gcc dot gnu.org
2014-04-22 11:38 ` [Bug rtl-optimization/57032] [4.9/4.10 " jakub at gcc dot gnu.org
2014-07-16 13:31 ` jakub at gcc dot gnu.org
2014-09-13 23:20 ` [Bug rtl-optimization/57032] [4.9/5 " olegendo at gcc dot gnu.org
2014-10-30 10:43 ` jakub at gcc dot gnu.org
2015-04-08  8:28 ` ubizjak at gmail dot com
2015-04-09 17:31 ` rth at gcc dot gnu.org
2015-04-09 19:46 ` ubizjak at gmail dot com
2015-04-09 19:48 ` ubizjak at gmail dot com
2015-04-09 19:53 ` ubizjak at gmail dot com [this message]
2015-04-09 19:56 ` ubizjak at gmail dot com
2015-04-14 16:48 ` [Bug rtl-optimization/57032] [4.9/5/6 " ubizjak at gmail dot com
2015-05-18 16:35 ` uros at gcc dot gnu.org
2015-05-18 17:40 ` ubizjak at gmail dot com

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-57032-4-dKwd6eOd9E@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).