public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rask at sygehus dot dk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/32761] [4.3 Regression] build broke: var_tracking loses track of register elimination, crashes in find_src_set_src on parallel set Date: Thu, 19 Jul 2007 13:31:00 -0000 [thread overview] Message-ID: <20070719133136.28144.qmail@sourceware.org> (raw) In-Reply-To: <bug-32761-507@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from rask at sygehus dot dk 2007-07-19 13:31 ------- Created an attachment (id=13939) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13939&action=view) Test case for frv-unknown-elf with -O2 -g -mcpu=fr400 It breaks on frv-unknown-elf as well: Program received signal SIGSEGV, Segmentation fault. find_src_set_src (set=0xdf05a0, loc=0x2b2c3b921760, insn=<value optimized out>) at /n/12/rask/src/all/gcc/var-tracking.c:1865 1865 if (REG_P (src)) (gdb) call debug_rtx(src) (nil) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32761
next prev parent reply other threads:[~2007-07-19 13:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-14 2:05 [Bug middle-end/32761] New: build broke: var_tracking loses track of fp-elimination, " hp at gcc dot gnu dot org 2007-07-14 2:07 ` [Bug middle-end/32761] " hp at gcc dot gnu dot org 2007-07-14 2:16 ` hp at gcc dot gnu dot org 2007-07-14 5:15 ` [Bug middle-end/32761] [4,3 Regression] build broke: var_tracking loses track of register elimination, " pinskia at gcc dot gnu dot org 2007-07-15 0:52 ` danglin at gcc dot gnu dot org 2007-07-19 13:31 ` rask at sygehus dot dk [this message] 2007-07-24 0:59 ` [Bug middle-end/32761] [4.3 " hp 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=20070719133136.28144.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).