public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/43995] internal compiler error: Segmentation fault on Mips64 crossbuild of ext2progs Date: Sun, 29 May 2011 18:05:00 -0000 [thread overview] Message-ID: <bug-43995-4-ND9EN9n2dl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-43995-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43995 --- Comment #12 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> 2011-05-29 17:50:57 UTC --- Author: rsandifo Date: Sun May 29 17:50:53 2011 New Revision: 174407 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=174407 Log: gcc/ PR target/43995 * config/mips/mips.c (mips_pic_call_symbol_from_set): Add a recurse_p argument. Only follow register copies if it is set, and prevent mips_find_pic_call_symbol from recursing. (mips_find_pic_call_symbol): Add a recurse_p argument. Pass it to mips_pic_call_symbol_from_set. (mips_annotate_pic_calls): Update accordingly. Modified: branches/gcc-4_5-branch/gcc/ChangeLog branches/gcc-4_5-branch/gcc/config/mips/mips.c
next prev parent reply other threads:[~2011-05-29 17:56 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-43995-4@http.gcc.gnu.org/bugzilla/> 2011-05-28 11:35 ` [Bug middle-end/43995] " rsandifo at gcc dot gnu.org 2011-05-28 12:02 ` [Bug target/43995] " rsandifo at gcc dot gnu.org 2011-05-29 17:46 ` rsandifo at gcc dot gnu.org 2011-05-29 17:48 ` rsandifo at gcc dot gnu.org 2011-05-29 18:05 ` rsandifo at gcc dot gnu.org [this message] 2011-05-29 18:11 ` rsandifo at gcc dot gnu.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=bug-43995-4-ND9EN9n2dl@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: 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).