public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "baraclese at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/35354] ICE in libgcc2.c/__popcountsi2 Date: Mon, 25 Feb 2008 17:37:00 -0000 [thread overview] Message-ID: <20080225173509.1628.qmail@sourceware.org> (raw) In-Reply-To: <bug-35354-11901@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from baraclese at googlemail dot com 2008-02-25 17:35 ------- I'm changing the resolution to invalid, but maybe you want to up the requirements on the mpfr version number and bail out if it's too low. -- baraclese at googlemail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35354
prev parent reply other threads:[~2008-02-25 17:37 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-24 17:19 [Bug bootstrap/35354] New: " baraclese at googlemail dot com 2008-02-24 18:08 ` [Bug bootstrap/35354] " pinskia at gcc dot gnu dot org 2008-02-24 19:41 ` baraclese at googlemail dot com 2008-02-24 21:23 ` baraclese at googlemail dot com 2008-02-25 17:37 ` baraclese at googlemail dot com [this message]
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=20080225173509.1628.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).