public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/25864] Enable IBM long double format in 32-bit PowerPC Linux Date: Sat, 11 Feb 2006 08:47:00 -0000 [thread overview] Message-ID: <20060211084726.23610.qmail@sourceware.org> (raw) In-Reply-To: <bug-25864-327@http.gcc.gnu.org/bugzilla/> ------- Comment #13 from jakub at gcc dot gnu dot org 2006-02-11 08:47 ------- Created an attachment (id=10821) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10821&action=view) gcc41-ldbl-default-libstdc++.patch Just for completeness, I'm attaching backport of the libstdc++-v3 changes that are on the trunk. This will be eventually on redhat/gcc-4_1-branch and if there is sufficient interest, we could try a separate branch of gcc-4_1-branch that would contain just the long double changes. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25864
next prev parent reply other threads:[~2006-02-11 8:47 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-19 20:26 [Bug target/25864] New: " dje at gcc dot gnu dot org 2006-01-19 20:27 ` [Bug target/25864] " pinskia at gcc dot gnu dot org 2006-01-19 20:28 ` dje at gcc dot gnu dot org 2006-01-19 20:44 ` mmitchel at gcc dot gnu dot org 2006-01-19 23:19 ` uweigand at gcc dot gnu dot org 2006-01-24 16:42 ` jakub at gcc dot gnu dot org 2006-01-25 6:27 ` mmitchel at gcc dot gnu dot org 2006-01-27 20:00 ` jakub at gcc dot gnu dot org 2006-02-03 7:44 ` krebbel at gcc dot gnu dot org 2006-02-03 7:53 ` krebbel at gcc dot gnu dot org 2006-02-10 20:58 ` jakub at gcc dot gnu dot org 2006-02-11 8:39 ` jakub at gcc dot gnu dot org 2006-02-11 8:45 ` jakub at gcc dot gnu dot org 2006-02-11 8:47 ` jakub at gcc dot gnu dot org [this message] 2006-02-11 8:49 ` jakub at gcc dot gnu dot org 2006-02-14 14:18 ` jakub at gcc dot gnu dot org 2006-02-14 14:23 ` jakub at gcc dot gnu dot org 2006-06-29 18:58 ` pluto at agmk dot net 2006-10-21 21:19 ` pinskia at gcc dot gnu dot org 2006-10-21 21:24 ` pinskia 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=20060211084726.23610.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).