public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/51527] ICE: Segmentation fault: 'convert_to_integer' enters infinite recursion Date: Fri, 27 Apr 2012 10:52:00 -0000 [thread overview] Message-ID: <bug-51527-4-EnDOscpjtN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51527-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51527 --- Comment #4 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2012-04-27 10:52:03 UTC --- Author: gjl Date: Fri Apr 27 10:51:58 2012 New Revision: 186899 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=186899 Log: PR c/51527 * convert.c (convert_to_integer): Avoid infinte recursion for target-defined built-in types. Modified: branches/gcc-4_7-branch/gcc/ChangeLog branches/gcc-4_7-branch/gcc/convert.c
next prev parent reply other threads:[~2012-04-27 10:52 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-13 12:30 [Bug c/51527] New: " gjl at gcc dot gnu.org 2011-12-13 12:31 ` [Bug c/51527] " gjl at gcc dot gnu.org 2011-12-13 12:50 ` gjl at gcc dot gnu.org 2012-03-05 17:32 ` gjl at gcc dot gnu.org 2012-03-22 9:31 ` rguenth at gcc dot gnu.org 2012-04-27 10:52 ` gjl at gcc dot gnu.org [this message] 2012-04-27 11:04 ` gjl 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-51527-4-EnDOscpjtN@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).