public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/49735] [4.7 Regression] mips64-elf libgcc build fails with apparently infinite recursion. Date: Wed, 13 Jul 2011 23:12:00 -0000 [thread overview] Message-ID: <bug-49735-4-gGpIdj1Q9g@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49735-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49735 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |build, ice-on-valid-code Target| |mips64-linux Status|UNCONFIRMED |NEW Last reconfirmed| |2011.07.13 23:12:32 Target Milestone|--- |4.7.0 Summary|mips64-elf libgcc build |[4.7 Regression] mips64-elf |fails with apparently |libgcc build fails with |infinite recursion. |apparently infinite | |recursion. Ever Confirmed|0 |1 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-07-13 23:12:32 UTC --- Confirmed.
next prev parent reply other threads:[~2011-07-13 23:12 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-13 14:32 [Bug tree-optimization/49735] New: " bernds at gcc dot gnu.org 2011-07-13 23:12 ` pinskia at gcc dot gnu.org [this message] 2011-07-13 23:18 ` [Bug tree-optimization/49735] [4.7 Regression] " pinskia at gcc dot gnu.org 2011-07-13 23:22 ` pinskia at gcc dot gnu.org 2011-07-14 0:08 ` pinskia at gcc dot gnu.org 2011-07-14 9:08 ` rguenth at gcc dot gnu.org 2011-07-14 18:27 ` pinskia at gcc dot gnu.org 2011-07-19 18:10 ` rsandifo at gcc dot gnu.org 2011-08-02 14:41 ` rguenth at gcc dot gnu.org 2011-08-03 20:00 ` hubicka at gcc dot gnu.org 2011-08-03 20:01 ` hubicka at gcc dot gnu.org 2011-08-05 20:21 ` hubicka at gcc dot gnu.org 2011-08-06 18:49 ` 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-49735-4-gGpIdj1Q9g@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).