public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/52639] New: ice in supportable_widening_operation
Date: Tue, 20 Mar 2012 18:20:00 -0000	[thread overview]
Message-ID: <bug-52639-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 52639
           Summary: ice in supportable_widening_operation
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: dcb314@hotmail.com


Created attachment 26934
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26934
C source code

I just tried to compile the package mpfr-3.1.0
on gcc-4.8 trunk dated 20120319 on an AMD x86_64 box.

The compiler said

set_f.c: In function 'mpfr_set_f':
set_f.c:27:1: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

Here is a valgrind dump

==19223== Invalid read of size 8
==19223==    at 0xCC7B08: supportable_widening_operation(tree_code,
gimple_statement_d*, tree_node*, tree_node*, tree_node**, tree_node**,
tree_code*, tree_code*, int*, VEC_tree_heap**) (tree-vect-stmts.c:6096)
==19223==    by 0x1082547: vect_recog_widen_mult_pattern(VEC_gimple_heap**,
tree_node**, tree_node**) (tree-vect-patterns.c:664)
==19223==    by 0x1087A57: vect_pattern_recog(_loop_vec_info*, _bb_vec_info*)
(tree-vect-patterns.c:2553)
==19223==    by 0xCEBA85: vect_slp_analyze_bb(basic_block_def*)
(tree-vect-slp.c:2020)
==19223==    by 0xCECA55: execute_vect_slp() (tree-vectorizer.c:265)
==19223==    by 0xA52D6C: execute_one_pass(opt_pass*) (passes.c:2084)
==19223==    by 0xA532E6: execute_pass_list(opt_pass*) (passes.c:2139)
==19223==    by 0xB91E4D: tree_rest_of_compilation(tree_node*)
(tree-optimize.c:422)
==19223==    by 0x7EBD7D: cgraph_expand_function(cgraph_node*)
(cgraphunit.c:1837)
==19223==    by 0x7EFB4B: cgraph_optimize() (cgraphunit.c:1904)
==19223==    by 0x7F01F9: cgraph_finalize_compilation_unit()
(cgraphunit.c:1344)
==19223==    by 0x5F3B1A: cp_write_global_declarations() (decl2.c:4074)
==19223==  Address 0x10 is not stack'd, malloc'd or (recently) free'd

Preprocessed source code attached. Flag -O3 required.


             reply	other threads:[~2012-03-20 18:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 18:20 dcb314 at hotmail dot com [this message]
2012-03-20 19:01 ` [Bug c++/52639] " dcb314 at hotmail dot com
2012-03-31 23:29 ` paolo.carlini at oracle dot com
2012-04-03 19:29 ` dcb314 at hotmail dot com
2012-04-03 19:32 ` dcb314 at hotmail dot com
2012-04-24 13:23 ` vincent-gcc at vinc17 dot net
2012-04-24 14:05 ` rguenth at gcc dot gnu.org
2012-04-24 18:09 ` dcb314 at hotmail dot com
2012-04-24 23:58 ` vincent-gcc at vinc17 dot net
2012-04-25  0:18 ` paolo.carlini at oracle dot com
2014-02-16 10:02 ` jackie.rosen at hushmail 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-52639-4@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).