public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dorit at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/21335] bootstrap fails with CFLAGS="-O3 -ftree-vectorize"
Date: Mon, 02 May 2005 14:51:00 -0000	[thread overview]
Message-ID: <20050502145140.32109.qmail@sourceware.org> (raw)
In-Reply-To: <20050502115108.21335.micis@gmx.de>


------- Additional Comments From dorit at il dot ibm dot com  2005-05-02 14:51 -------
I get the following bootstrap failure on powerpc-apple-darwin, with "-O2 -ftree-
vectorize":

../../gcc/gcc/builtins.c: In function 'fold_builtin_1':
../../gcc/gcc/builtins.c:8451: internal compiler error: Bus error

which seems to happen during tree-if-conversion:

(gdb)
Program received signal EXC_BAD_ACCESS, Could not access memory.
0x000cbe00 in clean_predicate_lists (loop=0x4144fda0) at ../../gcc/gcc/tree-if-
conv.c:654
654         bb[i]->aux = NULL;
(gdb) backtrace
#0  0x000cbe00 in clean_predicate_lists (loop=0x4144fda0) at ../../gcc/gcc/tree-
if-conv.c:654
#1  0x000caf0c in tree_if_conversion (loop=0x4d78b8, for_vectorizer=16 '\020') 
at ../../gcc/gcc/tree-if-conv.c:205
#2  0x000ccbf0 in main_tree_if_conversion () at ../../gcc/gcc/tree-if-
conv.c:1116
#3  0x00065874 in execute_one_pass (pass=0x17311d0) at ../../gcc/gcc/tree-
optimize.c:578
#4  0x00065958 in execute_pass_list (pass=0x4b7f2c) at ../../gcc/gcc/tree-
optimize.c:615
#5  0x00065970 in execute_pass_list (pass=0x4b7cb0) at ../../gcc/gcc/tree-
optimize.c:616
#6  0x00065970 in execute_pass_list (pass=0x4b74f0) at ../../gcc/gcc/tree-
optimize.c:616
#7  0x00065c34 in tree_rest_of_compilation (fndecl=0xb7915c) 
at ../../gcc/gcc/tree-optimize.c:728
#8  0x0000e60c in c_expand_body (fndecl=0xde0bc8) at ../../gcc/gcc/c-decl.c:6411
#9  0x002f7998 in cgraph_expand_function (node=0xde0bc8) 
at ../../gcc/gcc/cgraphunit.c:924
#10 0x002f7ac4 in cgraph_expand_all_functions () 
at ../../gcc/gcc/cgraphunit.c:988
#11 0x002f7e0c in cgraph_optimize () at ../../gcc/gcc/cgraphunit.c:1090
#12 0x002a6ad4 in compile_file () at ../../gcc/gcc/toplev.c:1013
#13 0x002a8a80 in do_compile () at ../../gcc/gcc/toplev.c:2123
#14 0x002a8b04 in toplev_main (argc=43, argv=0xbffff868) 
at ../../gcc/gcc/toplev.c:2155
#15 0x00001df0 in _start (argc=43, argv=0xbffff868, envp=0xbffff918) 
at /SourceCache/Csu/Csu-47/crt.c:267
#16 0x8fe1a558 in __dyld__dyld_start ()
(gdb) 


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dpatel at apple dot com


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


  reply	other threads:[~2005-05-02 14:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02 11:51 [Bug bootstrap/21335] New: " micis at gmx dot de
2005-05-02 14:51 ` dorit at il dot ibm dot com [this message]
2005-09-25 23:31 ` [Bug bootstrap/21335] [meta-bug] " pinskia at gcc dot gnu dot org
2005-09-28 21:31 ` [Bug bootstrap/21335] [meta-bug] bootstrap fails with -ftree-vectorize rguenth at gcc dot gnu dot org
2005-09-29  6:22 ` uros at kss-loka dot si

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=20050502145140.32109.qmail@sourceware.org \
    --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).