public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/21840] Linux 2.6.11.1.11: drivers/char/keyboard.c:619: internal compiler error: Segmentation fault Date: Tue, 31 May 2005 14:57:00 -0000 [thread overview] Message-ID: <20050531144704.5884.qmail@sourceware.org> (raw) In-Reply-To: <20050531135612.21840.mclinden@informed.net> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-31 14:46 ------- The backtrace: #0 0x083f1b29 in ix86_struct_value_rtx (type=0xb7c0657c, incoming=0) at /home/peshtigo/pinskia/ src/gnu/gcc/src/gcc/config/i386/i386.c:3184 #1 0x081974c9 in expand_call (exp=0xb778e9d8, target=0x0, ignore=1) at /home/peshtigo/pinskia/ src/gnu/gcc/src/gcc/calls.c:1909 #2 0x08203cf8 in expand_expr_real_1 (exp=0xb778e9d8, target=0x0, tmode=Variable "tmode" is not available. ) at /home/peshtigo/pinskia/src/gnu/gcc/src/gcc/expr.c:7344 #3 0x0820e497 in expand_expr_real (exp=0xb778e9d8, target=0xb7bf4210, tmode=VOIDmode, modifier=EXPAND_NORMAL, alt_rtl=0x0) at /home/peshtigo/pinskia/src/gnu/gcc/src/gcc/expr.c:6417 #4 0x083a3ac6 in expand_expr_stmt (exp=0xb778e9d8) at expr.h:489 #5 0x083e0bee in expand_gimple_basic_block (bb=0xb7807ca8, dump_file=Variable "dump_file" is not available. ) at /home/peshtigo/pinskia/src/gnu/gcc/src/gcc/cfgexpand.c:955 #6 0x083e1853 in tree_expand_cfg () at /home/peshtigo/pinskia/src/gnu/gcc/src/gcc/cfgexpand.c: 1307 #7 0x080d2cbd in execute_pass_list (pass=0x8574b40) at /home/peshtigo/pinskia/src/gnu/gcc/src/ gcc/tree-optimize.c:623 #8 0x080d30d3 in tree_rest_of_compilation (fndecl=0xb7767798) at /home/peshtigo/pinskia/src/ gnu/gcc/src/gcc/tree-optimize.c:793 #9 0x0805dc12 in c_expand_body (fndecl=0xb7767798) at /home/peshtigo/pinskia/src/gnu/gcc/ src/gcc/c-decl.c:6593 #10 0x08415b82 in cgraph_expand_function (node=0xb779b0d8) at /home/peshtigo/pinskia/src/ gnu/gcc/src/gcc/cgraphunit.c:949 #11 0x084179d5 in cgraph_optimize () at /home/peshtigo/pinskia/src/gnu/gcc/src/gcc/cgraphunit.c: 1013 #12 0x083aff76 in toplev_main (argc=33, argv=0xbff263b4) at /home/peshtigo/pinskia/src/gnu/gcc/ src/gcc/toplev.c:1008 #13 0x0035dad4 in __libc_start_main () from /lib/tls/libc.so.6 #14 0x08049b21 in _start () -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21840
next prev parent reply other threads:[~2005-05-31 14:47 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-05-31 13:57 [Bug c/21840] New: " mclinden at informed dot net 2005-05-31 14:05 ` [Bug middle-end/21840] " pinskia at gcc dot gnu dot org 2005-05-31 14:35 ` mclinden at informed dot net 2005-05-31 14:45 ` pluto at agmk dot net 2005-05-31 14:57 ` pinskia at gcc dot gnu dot org [this message] 2005-05-31 14:59 ` [Bug middle-end/21840] [4.1 Regression] " pinskia at gcc dot gnu dot org 2005-05-31 15:10 ` pinskia at gcc dot gnu dot org 2005-05-31 15:41 ` dberlin at gcc dot gnu dot org 2005-06-16 23:53 ` pluto at agmk dot net 2005-07-12 6:54 ` [Bug middle-end/21840] [4.1 Regression] ICE while building Linux kernel (seg fault), missing cast pinskia at gcc dot gnu dot org 2005-07-12 17:00 ` pinskia at gcc dot gnu dot org 2005-07-13 2:22 ` pinskia at gcc dot gnu dot org 2005-07-13 2:33 ` pinskia at gcc dot gnu dot org 2005-07-13 2:33 ` cvs-commit at gcc dot gnu dot 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=20050531144704.5884.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: linkBe 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).