public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/59789] [4.9 Regression] ICE in in convert_move, at expr.c:333
Date: Mon, 20 Jan 2014 21:09:00 -0000	[thread overview]
Message-ID: <bug-59789-4-mG4ZznCIQO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59789-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59789

--- Comment #8 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> ---
Author: hjl
Date: Mon Jan 20 21:08:26 2014
New Revision: 206858

URL: http://gcc.gnu.org/viewcvs?rev=206858&root=gcc&view=rev
Log:
Add type to DEFCIFCODE to describe the inline failure

Report inline error during early inlining if the inline failure is
CIF_FINAL_ERROR.

gcc/

    PR middle-end/59789
    * cgraph.c (cgraph_inline_failed_string): Add type to DEFCIFCODE.
    (cgraph_inline_failed_type): New function.
    * cgraph.h (DEFCIFCODE): Add type.
    (cgraph_inline_failed_type_t): New enum.
    (cgraph_inline_failed_type): New prototype.
    * cif-code.def: Add CIF_FINAL_NORMAL to OK, FUNCTION_NOT_CONSIDERED,
    FUNCTION_NOT_OPTIMIZED, REDEFINED_EXTERN_INLINE,
    FUNCTION_NOT_INLINE_CANDIDATE, LARGE_FUNCTION_GROWTH_LIMIT,
    LARGE_STACK_FRAME_GROWTH_LIMIT, MAX_INLINE_INSNS_SINGLE_LIMIT,
    MAX_INLINE_INSNS_AUTO_LIMIT, INLINE_UNIT_GROWTH_LIMIT,
    RECURSIVE_INLINING, UNLIKELY_CALL, NOT_DECLARED_INLINED,
    OPTIMIZING_FOR_SIZE, ORIGINALLY_INDIRECT_CALL,
    INDIRECT_UNKNOWN_CALL, USES_COMDAT_LOCAL. 
    Add CIF_FINAL_ERROR to UNSPECIFIED, BODY_NOT_AVAILABLE,
    FUNCTION_NOT_INLINABLE, OVERWRITABLE, MISMATCHED_ARGUMENTS,
    EH_PERSONALITY, NON_CALL_EXCEPTIONS, TARGET_OPTION_MISMATCH,
    OPTIMIZATION_MISMATCH.
    * tree-inline.c (expand_call_inline): Emit errors during
    early_inlining if cgraph_inline_failed_type returns
    CIF_FINAL_ERROR.

gcc/testsuite/

    PR middle-end/59789
    * gcc.target/i386/pr59789.c: New testcase.

Added:
    trunk/gcc/testsuite/gcc.target/i386/pr59789.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/cgraph.c
    trunk/gcc/cgraph.h
    trunk/gcc/cif-code.def
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree-inline.c


  parent reply	other threads:[~2014-01-20 21:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 14:49 [Bug target/59789] New: " aivchenk at gmail dot com
2014-01-13 15:25 ` [Bug target/59789] " hjl.tools at gmail dot com
2014-01-13 15:40 ` hjl.tools at gmail dot com
2014-01-13 15:40 ` hjl.tools at gmail dot com
2014-01-13 15:56 ` aivchenk at gmail dot com
2014-01-13 16:27 ` hjl.tools at gmail dot com
2014-01-13 17:53 ` hjl.tools at gmail dot com
2014-01-20 21:09 ` hjl at gcc dot gnu.org [this message]
2014-01-20 21:10 ` [Bug tree-optimization/59789] " hjl.tools 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-59789-4-mG4ZznCIQO@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).